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.
接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
npx -y @aauth/[email protected]Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
claude mcp add aauth-mcp-server -- npx -y @aauth/mcp-server@1.0.0在終端機中執行。
{ "mcpServers": { "aauth-mcp-server": { "command": "npx", "args": [ "-y", "@aauth/[email protected]" ] } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
來自發布者
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]" ] } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
@aauth/ 透過 stdio 在本機執行。
上次檢查時間:2026-11-16。 AAuth server-side building blocks: challenge headers, interaction management, resource tokens