Skip to content

Put a hosted MCP server behind AtmanID (GitHub, Slack, Stripe)

Many MCP servers are hosted by the vendor: GitHub, Slack and Stripe each run one. They speak the standard MCP protocol and accept only their own vendor’s credential. AtmanID governs them like any other server: your agents call the AtmanID gateway, and the gateway calls the vendor’s server on their behalf with a credential it holds for you. The agents never hold the vendor credential.

1. Register the server and point it at the vendor

In MCP Gateway → Settings, for the server:

  1. Set the upstream URL to the vendor’s MCP endpoint, for example https://api.githubcopilot.com/mcp/, https://mcp.slack.com/mcp or https://mcp.stripe.com.
  2. Set the protocol under it to Standard MCP.

The gateway now speaks the MCP protocol to that server. Once it has the credential (step 2), it records the server’s tools, checks the list every hour, and holds any tool whose definition changes until you approve the change.

2. Give AtmanID the vendor credential

Open Upstream Identity for the server, choose Stored credential and paste the credential:

Server Credential to create Narrow it with
GitHub A fine-grained personal access token, or a GitHub App token Only the repositories and permissions the agents need. Read-only if they only read
Slack A user token issued through a Slack app your workspace admin approved The fewest scopes that cover the agents’ tasks. Leave out search of private channels and DMs unless it’s needed
Stripe An agent API key (restricted) Only the resources the agents need, in test mode until you’re ready

Use a credential made for this purpose only, never a person’s own token.

How AtmanID holds it:

  • Encrypted with your tenant’s key, and bound to this one server.
  • Write-only. Once saved, AtmanID shows only its last four characters, and you can replace or remove it.
  • Audited. Every save and removal is recorded, without the value.
  • Sent only after the gateway allows the call. It goes as Authorization: Bearer to this server’s URL. If AtmanID can’t use it, the call is refused rather than sent without it.

The vendor sees one identity for every agent that uses the server, so the narrowing above is what limits them at the vendor’s end. Per-agent limits are AtmanID’s job: the grant, intent policies, holds and inspection.

3. Review the tools, then decide who may call them

When the first tool list arrives, review it in the server’s tool inventory. Then:

  • Grant agents only the tools they need. A GitHub agent that triages issues needs the issue tools, not delete_file or merge_pull_request.
  • Hold the high-impact tools for a person. Use intent policies to hold calls such as a merge, a payment action, or a message to a channel for approval, or deny them outright.
  • Start in Shadow. Leave the server in Shadow until the events show what would be refused, then switch it to Enforce.

4. Connect the agents

Agents use the server’s AtmanID endpoint, never the vendor’s URL (connect any MCP client).

What to know

  • Content from these servers can carry instructions. Issue text, chat messages and record fields are written by other people, and some are written to steer an agent. Grants, holds and inspection limit what a steered agent can do. Keep the high-impact tools held.
  • Close the side door. An agent that also has the vendor credential can go around the gateway. Keep vendor credentials out of agents’ configuration, and revoke any it had before.
  • Resources and prompts aren’t served. The gateway governs a server’s tools. Its resources and prompts answer “Method not found” through the gateway.
  • A server you host yourself works the same way. Set it to Standard MCP, and use token exchange instead of a stored credential if it can verify AtmanID’s signed agent token.

© AtmanID · Privacy