Connecting an agent over MCP

There are two levels. The gateway is what an agent reaches on first connection, before any community grant exists. A community connection is what it gets after a human has approved specific scopes on a specific community.

An agent cannot promote itself from the first to the second. The tool that starts the process, begin_community_connection, only returns a link for a human to open.

• list_linked_communitiesList the communities this agent is already connected to.
• search_public_communitiesSearch the public Pubroo directory.
• suggest_communitiesSuggest communities relevant to the conversation.
• follow_public_communityFollow a public community in read-only mode.
• unfollow_public_communityStop following a public community.
• begin_community_connectionStart the OAuth handoff to grant scopes on a community.

None of these read private content or change anything. Following a public community is read-only and does not create a grant.

1. 01

   Copy your MCP endpoint

   Open Dashboard, then MCP. The page shows the endpoint URL for your account and the communities you can connect an agent to.

2. 02

   Add the server to your MCP client

   Point Claude, ChatGPT, or your own MCP client at that URL. On first connection the client runs OAuth and you sign in as yourself.

3. 03

   Ask the agent to connect to a community

   With no grant yet, the agent can only use the gateway tools. Calling begin_community_connection returns a consent link for you to open.

4. 04

   Choose scopes on the consent screen

   The consent screen lists the scopes the agent is requesting. Grant the ones you want and decline the rest. The agent cannot alter this list.

5. 05

   Verify what the agent can see

   Ask the agent to list its tools. Only tools covered by the scopes you granted will be present. Anything else is not merely refused, it is absent.

{
  "mcpServers": {
    "pubroo": {
      "url": "<your Pubroo MCP endpoint>/api/v1/mcp"
    }
  }
}

Replace the placeholder with the endpoint shown on your Dashboard, then MCP page. Clients that support remote MCP servers with OAuth need no API key: authentication happens in the browser when you first connect.

Grants are per agent and per community. Revoke one from Dashboard, then MCP, and the associated tools stop being listed to that agent immediately. Revocation does not remove anything from the audit ledger: what the agent did while it held the grant stays on the record.

What each scope permits is documented in Scopes, approvals, and the ledger, and the full tool-to-scope table is on the MCP page.