MCPServer Credentials

MCP Server Credentials

These are the credentials Archestra uses to call the MCP servers behind a gateway, such as Jira or GitHub. Each MCP server signs in its own way. Set it once per server, and Archestra signs in on every call, as the right account. Ask for your open Jira tickets, and the call uses your Jira account. A status-page bot posts as the bot. Nobody pastes a key into a client.

Sign-In Methods

Pick the method the server's own docs name. You set it when you add the server.

MethodWho signs inPick it when
OAuth 2.1Each person, in the browser, onceThe server offers OAuth. Most hosted servers do.
Token headerEach person or team, with an API key at installThe server takes an API key or a personal access token
OAuth 2.0 client credentialsOne app account, with no personThe server serves machines, not people
IdP token exchangeNobody. Archestra uses the person's company identity.You want per-person accounts without installs. See IdP Token Exchange.
IdP signed JWTNobody. Archestra sends the person's company JWT.The server checks your identity provider's tokens itself
AWS IAM (SigV4)Nobody. Each agent assumes an IAM role.The server sits behind AWS, such as a Bedrock AgentCore Gateway. See AWS IAM.

OAuth tokens refresh by themselves when the provider allows it. A stdio server gets its credentials once, at start, so per-call methods need streamable-http.

Whose Account a Call Uses

Decide per tool: should it act as the person who asks, or always as one shared account? A Jira tool should file tickets as you, so Jira shows who asked. A deploy tool can run as a bot, so nobody needs their own deploy key.

You wantSet on the toolSet on the server's Credentials
Each person acts as themselvesResolve at call timeAgents connect with: Each caller's own account
Their own account, or the team's when they have noneResolve at call timeEach caller's own account, plus a team install
Everyone acts as one botThe bot's shared installNothing

Set the tool's account where you choose its tools, on the gateway or the agent. A tool pinned to a shared install always uses it, whatever the server's default says.

  • Nobody's account fits? The call fails with a link to install one. Follow it, and try again.
  • A personal install serves only its owner. A team install works only in agents and gateways the team can use.
  • To check which account a call used, see Identity in the MCP Gateway logs.

Company Identity

Give every person their own account in every server, with no installs: on each call, Archestra trades the person's single sign-on token for a token the server accepts. Pick IdP token exchange, or IdP signed JWT when the server checks your provider's tokens itself. See IdP Token Exchange.

What to Know

  • Sign-in expired? Your client asks you to sign in again, then the tool call finishes. Claude Code opens the page from a prompt. Cursor is the exception: its agent shows the link in its reply. You can also click Re-authenticate on the install.
  • Changed the OAuth scopes? Reconnect to get tokens with the new scopes.
  • Every call records its account. See Identity in the MCP Gateway logs.