On this page
MCP Servers
Connect built-in or custom MCP servers, understand visible states, and review actions that can change data.
MCP Servers are optional connections to tools that can contribute information or an action during a task. Open Settings → MCP Servers to browse the built-in catalog, connect a server, or add a custom server. Connect only what the task needs and review any action that can change data before allowing it.
Open Settings → MCP Servers
Choose a built-in connector from the catalog or select Add MCP server for a custom connection.
Choose the visible connection method
Built-in connectors expose the sign-in or connection input they need. Custom servers use Local (stdio) or Remote (HTTP/SSE) fields.
Confirm the connection state
Wait for Connecting to become Connected, or follow the visible Reconnect action when a connection needs attention.
Review task actions
When a connected server contributes an action, check its scope and requested permission before allowing an effectful operation.
Built-in connector catalog
The catalog has 14 built-in connectors. Their visible prerequisite groups are:
No credentials
Filesystem, DuckDuckGo, and Browser (Playwright) can be browsed without an additional credential or connection input.
API key, token, or connection input
Figma, Azure DevOps, Context7, and PostgreSQL ask for the connection input shown by the product.
Browser sign-in
Linear, Notion, Sentry, GitLab, Slack, and Jira (Atlassian) use the browser sign-in flow shown by the product.
Device-code sign-in
GitHub uses the device-code flow shown during connection.
Built-in server states
| State | What you see | Useful action |
|---|---|---|
| Connect | The connector is available but not connected. | Start the visible connection flow. |
| Connecting | The connection is being established. | Wait for the result and keep the task scope clear. |
| Connected | The server is available and Manage is visible. | Use it in a task after reviewing requested actions. |
| Reconnect | The saved connection needs attention. | Reconnect and confirm the visible state changes. |
| Turned off | The connector is disabled. | Turn it on again only when the task needs it. |
| Remove | The Manage menu offers removal of the saved setup. | Remove only when the saved configuration is no longer wanted. |
Disconnecting preserves the saved sign-in configuration so the connector can be connected again later. Remove deletes the saved configuration and sign-in information. Turning off all servers requires a confirmation because it changes the availability of every configured connector.
Add a custom MCP server
Choose Add MCP server and enter only the fields shown in the current form.
| Method | Fields | Review point |
|---|---|---|
| Local (stdio) | Command, space-separated arguments, optional KEY=VALUE environment lines | Confirm the local command is trusted before enabling it. |
| Remote (HTTP/SSE) | URL | Confirm the destination and the access it can provide. |
The custom form also provides an enable toggle and Remove action. The current form does not expose separate working-directory, custom-header, or tool- allowlist controls; do not assume those settings exist.
How should a connected server be used in a task?
Keep the project and attachments focused, then review the server's visible contribution alongside the task activity. For an action that changes data, read the request and approve it only when it matches your intent.
If a server is unavailable, check its visible state and retry when appropriate, or continue from project context when the external tool is not needed. Then read troubleshooting for recovery steps.