protocol
MCP Server
MCP Server
Connect your own MCP-compatible server (GitHub MCP, Linear MCP, or any server following the Model Context Protocol). Tools exposed by connected servers become available to the Polylane thread agent automatically.
Connect
Connect MCP Server from the terminal. Pass --help for the flags MCP Server accepts.
Terminal
polylane integration connect --type mcpThe HTTPS endpoint of any Model Context Protocol server.
Connect any external MCP-compatible server (GitHub MCP, Linear MCP, or your own). Tools the server exposes become available to the Polylane thread agent automatically.
Setup
- Enter the server URL: the HTTPS endpoint of your MCP server. Private, loopback, and cloud-metadata addresses are blocked.
- Choose the transport: Streamable HTTP (recommended) or SSE (legacy).
- Give it a display name (auto-filled from the server).
- Choose authentication:
- None for public servers
- Bearer token, sent as
Authorization: Bearer <token> - OAuth 2.0, with optional scopes, which redirects you to authorize
- Polylane discovers the server's tools. Click Connect to finish.
Bearer tokens are encrypted before they are stored, and the agent never sees them.
Disconnecting
Disconnect the MCP server in Polylane. Its tools are immediately removed from the agent.
Disconnect
Disconnecting stops every sync and check and deletes the credentials Polylane held. Everything Polylane set up in MCP Server is removed as well; nothing is left behind.
Terminal
polylane integration disconnect <id>