Primary navigation

Model Context Protocol

Connect ZeroTwo to third-party tools and context

MCP connects models to outside tools and context, such as library docs, a browser, or Figma. ZeroTwo builds on it throughout: every entry under Customize > Connectors is a remote MCP server that ZeroTwo signs in to for you, and plugins can bundle MCP servers of their own. You manage all of it in the app. There is no configuration file and no command-line tool for MCP.

Supported MCP features

ZeroTwo talks to remote servers over Streamable HTTP and, in the desktop app only, to local servers started as STDIO processes. Remote servers can use no authentication, an API key sent as a bearer token, custom headers, or OAuth 2.0, which ZeroTwo handles on the server side, including registering a client where the provider supports it. Each connection has one approval mode for all its tools, and the desktop app also supports MCP elicitation prompts and MCP app widgets.

Add an MCP server

  1. Open the form

    Go to Settings > Plugins, select Add, and choose Add MCP server.

  2. Describe it

    Give it a Name and a Type of STDIO or Streamable HTTP, then fill in the command or the URL.

  3. Authenticate if needed

    For a remote server pick No authentication, API key or OAuth 2.0 (a client ID and secret are optional), and add any Headers.

  4. Test and save

    Use Test connection to check a remote server, then Save.

Where the server ends up depends on its address. A public URL is saved to your ZeroTwo account, works on every device, and appears under Connectors. A private or localhost URL, and any STDIO server, runs on your computer only, so it needs the desktop app and appears under MCPs. OAuth is limited to public URLs. Type /mcp in a desktop Work or Code composer to open the same manager.

STDIO servers

The STDIO form has Command to launch, Arguments, Environment variables, Environment variable passthrough and Working directory. The desktop app stores secret values with the operating system's secure storage.

Streamable HTTP servers

The remote form has URL, Authentication, Headers, an optional Description and an Icon. API keys and other secret values stay hidden when you edit the server; leave the field blank to keep the current one.

Use MCP-backed tools

Connected servers supply their tools to your chats and tasks, on the web as well as in the desktop app. Installing a plugin brings in the connectors and MCP servers it bundles. Servers that run locally exist only on the desktop, and a cloud run cannot reach them.

Tool permissions

Permissions are set once per connected account or local server, not tool by tool. Open the app's page, choose Permissions, and pick Always ask, Allow read-only tools, Allow low-risk tools or Allow all tools; the last one carries an Elevated risk badge. An account with no choice of its own follows the Default permission on the plugin Permissions page, which starts at Allow low-risk tools. Connector tools ask for approval on every device, even when the desktop app runs with full access, and each one follows the mode you picked for it.

Plugin-provided and imported servers

A plugin can ship its own local server, which the desktop app launches for you; these appear as read-only rows because the plugin's own on and off switch controls them. Settings > Import can bring in MCP servers from other agents' configurations. Imported servers arrive disabled, so review each one before enabling it.

Examples of useful MCP servers

  • Context7: current library documentation, available as a connector.
  • Figma: designs, available as a connector.
  • GitHub: pull requests and issues, available as a connector.
  • Sentry: errors and logs, available as a connector.
  • Chrome DevTools: Chrome inspection, started by turning on Developer mode in the Chrome settings (desktop app only).

Not everything that drives a browser is an MCP server. The Playwright plugin, for example, is a set of skills that run a local Playwright command-line tool, so it does not appear under MCPs.