MCP Servers

Install an MCP server and its tools, resources, and prompts join the catalog chat can use. Chat can then reach your metrics stack, ticketing system, or anything else you expose through MCP.

Two directions, one acronym

Note

This page is about servers chat calls out to. The platform is also an MCP server itself. External agents like the architect plugin reach your boards with a scoped token. That direction lives on MCP Access.

Getting to the screen

One caveat: this feature is built and working, but its navigation entry is not enabled. There is no MCP Servers item in the settings sidebar yet.

Reach the management screen at /{your-org}/mcp-servers. The list, install flow, and capability console work, but the entry point may change at launch.

Installing a server

The screen has installed servers on one side and the selected server on the other. Install New MCP Server opens the sheet.

A server connects over stdio or SSE. stdio runs a local process for development, filesystem tools, and local services. SSE reaches a hosted server with headers for authentication. Streamable HTTP is not supported yet.

Provide a name, description, connection details, enabled capability types, and categories or tags. Saving validates the config and tests the connection.

Tip

Names and descriptions are worth writing carefully. Chat picks tools from the catalog by what they say they do, so a well-described tool gets chosen and a vaguely named one gets skipped.

What a server exposes

Once connected, we discover three capability kinds:

KindWhat it gives chat
ToolsFunctions chat can call — query a database, fetch metrics, run a job
ResourcesData chat can read — files, API responses, live system state
PromptsTemplated instructions for a specific task

The detail view includes a capability-testing console. Use it to verify the connection and test discovered capabilities against the live server.

Individual tools can be toggled off without removing the server. Use that when one tool from an otherwise useful server keeps being chosen for the wrong jobs.

Editing and uninstalling

Reopen a server to edit config, transport settings, and enabled capabilities. Re-run discovery after the server changes.

Uninstall MCP Server removes the installation and its discovered capabilities from the catalog.

Warning

Uninstalling takes those tools away from every conversation that was using them. Chat will still work, but answers that used to reach that server no longer can.

Not the same as Connectors

Connectors authorize third-party services so the platform can pull content or use a model provider. An MCP server exposes tools chat can call during a turn.

One brings material in. The other extends what chat can do. Neither replaces the other.

What's next