Connect an MCP server

The MCP Server connector brings in any server that speaks the Model Context Protocol, such as Linear, Sentry or an internal MCP service. Each tool on the server becomes a method the agent can call.

Connecting

On the Gatekeepers page choose MCP Server, or ask the agent in a workspace to connect one.
Enter the server’s URL (for example https://mcp.linear.app/mcp). It must be HTTPS and can’t be a private or local address.
If the server requires sign-in, Gosper discovers how it authorizes and sends you to its sign-in page. Public servers connect straight away.

The URL is fixed at first connect; reconnecting can’t point the account at a different server.

Choosing which tools to allow

When you grant it to a workspace, choose the scope:

All tools: every tool the server offers, including ones it adds later;
Choose tools: only the tools you tick. Anything else is refused, including tools added later.

Each tool in the list is marked read-only (returns data right away) or needs approval.

How the agent calls tools

Read-only tools return data immediately and are recorded as observations.
Other tools go to the approval queue, run once you approve, and the agent collects the result afterwards.

The binding is named after the server’s host, so mcp.linear.app suggests MCP_LINEAR, which makes it easy to spot in activity history.

Troubleshooting

Registration was refused while connecting? Some servers don’t support dynamic client registration. Use a server that does, or ask an administrator to provide access through your organization’s MCP portal.

Asked to reconnect? The server rejected the current token (it may have been revoked). Reconnect.

Does your organization manage MCP centrally? If an administrator has set up an MCP server portal, members pick from the servers approved there without typing a URL. Each grant still covers one server behind the portal.