# MCP Authentication

> How clients sign in to a gateway, and how Archestra signs in to each MCP server

Sign in to Archestra once, and every tool call runs as you, in every app. Ask Claude Code to file a Jira ticket and comment on a GitHub pull request. With your own accounts installed, Jira and GitHub both show your name. You never pasted a token into Claude Code.

Every MCP server signs in its own way, and most clients cannot do it for a whole team. Archestra does it for them:

- One way in for each client. Coding agents authenticate through the browser. Scripts, apps, and your identity provider have their own methods. See [MCP Gateway Authentication](https://archestra.ai/docs/mcp/authentication/gateway).
- The right account for each call. The person's own, a shared bot account, or their company identity, exchanged at call time. See [MCP Server Credentials](https://archestra.ai/docs/mcp/authentication/servers).
- Credentials stay in Archestra. It stores them, and refreshes OAuth tokens when the provider allows it. Clients never see them.
- Every call is traceable. The [MCP Gateway logs](https://archestra.ai/docs/admin/logs) show which account each call used.

```mermaid
graph LR
    Client["MCP client"] -->|"1. Gateway authentication<br/>OAuth, token, or IdP JWT"| Gateway["MCP Gateway"]
    Gateway -->|"2. Server credential<br/>the caller's or a shared one"| Server["MCP server"]

    class Gateway accent
```

<span id="gateway-authentication"></span><span id="upstream-mcp-server-authentication"></span><span id="id-jag-vs-jwks"></span>

## Explore

- [MCP Gateway Authentication](https://archestra.ai/docs/mcp/authentication/gateway.md): Authenticate a client to an MCP Gateway with OAuth, a platform token, your identity provider's JWT, or a GitHub Actions token
- [Gateway Access for Apps](https://archestra.ai/docs/mcp/authentication/applications.md): Let your own app or service call an MCP Gateway with an OAuth client
- [MCP Server Credentials](https://archestra.ai/docs/mcp/authentication/servers.md): Set how Archestra signs in to each MCP server, and whose account each call uses
- [IdP Token Exchange](https://archestra.ai/docs/mcp/authentication/idp-token-exchange.md): Give every person their own account in an MCP server, from their company sign-in, with no installs
- [AWS IAM (SigV4)](https://archestra.ai/docs/mcp/authentication/aws-iam.md): Let each agent call MCP servers behind AWS as its own IAM role session, with no AWS keys stored
