AAuth for MCP
TypeScript packages for adding AAuth to MCP servers and agents.
AAuth is an agent-aware authentication protocol that lets AI agents prove their identity and obtain authorization using HTTP Message Signatures and JWTs.
Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y @aauth/[email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add aauth-mcp-server -- npx -y @aauth/mcp-server@1.0.0Execute em um terminal.
{ "mcpServers": { "aauth-mcp-server": { "command": "npx", "args": [ "-y", "@aauth/[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
TypeScript packages for adding AAuth to MCP servers and agents.
AAuth is an agent-aware authentication protocol that lets AI agents prove their identity and obtain authorization using HTTP Message Signatures and JWTs.
AAuth server-side building blocks: challenge headers, interaction management, resource tokens
Agent Resource Server Auth Server
| | |
|--- signed request ------------>| |
| | |
|<-- 401 + resource_token -------| |
| + auth-server URL | |
| | |
|--- signed POST (resource_token) ------------------------->|
| |
|<-- auth_token --------------------------------------------|
| | |
|--- signed request ------------>| |
| + auth_token | |
| |-- verify signature |
| |-- verify auth_token |
| |-- check key binding |
|<-- 200 OK ---------------------| |
resource_token and auth server URLresource_token at the auth server (signed request)auth_token (or 202 for interactive flows)auth_token — resource verifies signature, token, and key bindingAll requests are signed with HTTP Message Signatures (RFC 9421) using Ed25519. Tokens are JWTs with aa-agent+jwt, aa-auth+jwt, and aa-resource+jwt types.
import { createAAuthFetch } from '@aauth/mcp-agent'
const fetch = createAAuthFetch({
getKeyMaterial: async () => ({
signingKey: privateKeyJwk,
signatureKey: { type: 'jwt', jwt: agentToken }
})
})
const response = await fetch('https://resource.example/api')
// Handles 401 challenges, token exchange, and retry automatically
import { verifyToken, buildAAuthHeader, createResourceToken } from '@aauth/mcp-server'
// Verify an incoming signed request's token
const result = await verifyToken({ jwt, httpSignatureThumbprint })
// Build a 401 challenge
const header = buildAAuthHeader('auth-token', { resourceToken, authServer })
// Create a resource token for the challenge
const token = await createResourceToken({ resource, authServer, agent, agentJkt }, sign)
# Register an agent provider: generate a key, bind it, and bind the default
# person server (person.hello.coop)
npx @aauth/bootstrap create <your-agent-provider-url>
See @aauth/bootstrap for the full setup flow.
This implementation covers the core AAuth protocol flows. The following spec features are not yet supported:
upstream_tokenrequirement=claims for identity claim exchangeThe AAuth protocol specification: github.com/dickhardt/AAuth
MIT
AAuth server-side building blocks: challenge headers, interaction management, resource tokens
{ "mcpServers": { "aauth-mcp-server": { "command": "npx", "args": [ "-y", "@aauth/[email protected]" ] } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
@aauth/ roda localmente via stdio.
Última verificação: 2026-11-16. AAuth server-side building blocks: challenge headers, interaction management, resource tokens