Skip to main content
A backend server is any MCP server mcp1 aggregates behind your workspace’s single endpoint. The Backend Servers page lists everything currently connected, its status, and a toggle to enable or disable it.

​
Registering a server

You can add a backend two ways:
  • From the Store — browse pre-built integrations (GitHub, and other zero-config connectors) and connect with one click.
  • Manually — provide a name, namespace, and URL for any http or sse MCP server. mcp1 connects and discovers its tools automatically.
Each server’s tools are prefixed with its namespace, so github registered as the namespace gh exposes tools like gh.create_issue.

​
Transport types

​
Enable and disable

Toggling a server off stops it from being discoverable or callable through the aggregated endpoint without deleting its configuration or history.

​
Auth headers

A server that requires an Authorization header (for example, one behind OAuth) registers successfully but won’t discover tools until you connect it in the UI — headers aren’t inferred automatically during import or manual registration.