MCP Server integration: connect MCP Server to Polylane
Connect external MCP servers to Polylane through Streamable HTTP or SSE. Give investigations access to your own tools with server-specific authentication.
Get started for freeWhat Polylane does with MCP Server.
Your tools in the agent's hands
Connect any MCP-compatible server and its tools show up mid-investigation, next to the built-in observability, graph, and code tools.
Anything that speaks the protocol
GitHub MCP, Linear MCP, an internal server you wrote last week: if it follows the Model Context Protocol, agents can use it.
On the record like everything else
Calls to your MCP tools land in the thread transcript with their results, cited like every other piece of evidence.
How to set up MCP Server
- Enter an HTTPS MCP server endpoint in Polylane. Private, loopback and cloud-metadata addresses are blocked.
- Select Streamable HTTP (recommended) or legacy SSE, and give the server a display name.
- Choose no authentication, a bearer token or OAuth 2.0. For OAuth, authorize the server’s requested scopes. Validate, review discovered tools and connect.
Permissions and access
Permissions come from your server and its authentication, not a universal Polylane MCP scope list. Bearer mode sends Authorization: Bearer <token>; OAuth supports server-specific scopes. Custom headers can be configured, but an Authorization header must not conflict with managed OAuth or bearer authentication. Bearer credentials are encrypted before storage.
Discovery, refresh and the connected view
The external server’s discovered tools become available to the Polylane thread agent. This connection imports callable tool definitions, not a promised set of cloud resources or application tables. The objects read and any write-back depend on the particular tools exposed by that server. Review its tool list and credentials before enabling it for investigations.
Example workflow
Expose a company-specific diagnostic endpoint through your own MCP server, then connect it so an investigation can call that tool alongside Polylane’s native cloud tools. For example, a server you operate could return internal release metadata unavailable from a cloud provider. This works only if your server actually implements that tool; connecting MCP does not create that capability for you.
Disconnect and revoke access
Disconnect the server in Polylane to remove its tools from the agent. Revoke the bearer credential or OAuth authorization at the server separately if it should no longer be usable elsewhere. A public server connected without credentials has no token to revoke.
MCP Server setup and troubleshooting
Common questions.
Can I connect an MCP server running on localhost?
No. The connection requires an HTTPS endpoint and blocks private, loopback and cloud-metadata addresses.
Does every MCP connection have write access?
No universal write permission exists. The server’s tools and the credentials you authorize determine what can be read or changed.