agent-auth-mcp
Use the Agent Auth MCP tools to discover providers, connect agents, manage capabilities, and execute operations through the MCP protocol. Use when working inside an MCP-enabled environment (Cursor, Claude Code, etc.) and need to authenticate agents, execute capabilities, or interact with Agent Auth providers.
- Installs
- 109
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/better-auth/agent-auth --skill agent-auth-mcp- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads agent-auth-mcp automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Agent Auth MCP Tools
You have access to Agent Auth MCP tools for interacting with Agent Auth providers. Always prefer using these MCP tools for any agent authentication operations rather than making raw HTTP requests or writing custom code.
Starting the MCP Server
The MCP server is part of the CLI:
auth-agent mcp
Or with pre-configured providers:
auth-agent mcp --url https://api.example.com
Cursor / Claude Desktop configuration
{
"mcpServers": {
"auth-agent": {
"command": "npx",
"args": ["@auth/agent-cli", "mcp", "--url", "https://api.example.com"]
}
}
}
Available Tools
The MCP server exposes 17 tools. Follow the numbered workflow below.
Step 1: Discovery — Find a Provider
| Tool | Parameters | When to use |
|---|---|---|
list_providers | (none) | Call this first. Lists all discovered/configured providers. |
search_providers | intent (required) | Search the directory by name or intent (e.g. "deploy web apps", "vercel"). |
discover_provider | url (required) | Look up a specific provider by URL. Only use if list/search didn't help. |
Always start with list_providers. If empty, use search_providers or discover_provider.
Step 2: Capabilities — Understand What's Available
| Tool | Parameters | When to use |
|---|---|---|
list_capabilities | provider (required), query, agent_id, limit, cursor | List capabilities for a provider. |
describe_capability | provider, name (required), agent_id | Get full definition including input schema. Always call before executing. |
Step 3: Connect — Authenticate an Agent
| Tool | Parameters | When to use |
|---|---|---|
connect_agent | provider (required), capabilities, mode, name, reason, preferred_method, login_hint, binding_message, force_new | Connect an agent to a provider. Returns agent_id. |
Key parameters:
capabilities— Array of capability names to request.mode—"delegated"(acts for a user, default) or"autonomous"(independent).preferred_method—"device_authorization"(default, opens browser) or"ciba"(backchannel notification).login_hint— User email for CIBA flow.force_new— Create a new connection even if one exists.
Step 4: Use the Agent
| Tool | Parameters | When to use |
|---|---|---|
execute_capability | agent_id, capability (required), arguments | Execute a granted capability. |
agent_status | agent_id (required) | Check agent status, grants, and constraints. |
sign_jwt | agent_id (required), capabilities, audience | Sign an agent JWT for manual use. |
request_capability | agent_id, capabilities (required), reason, preferred_method, login_hint, binding_message | Request additional capabilities. |
disconnect_agent | agent_id (required) | Revoke an agent. |
reactivate_agent | agent_id (required) | Reactivate an expired agent. |
Host Management
| Tool | Parameters | When to use |
|---|---|---|
enroll_host | provider, enrollment_token (required), name | Enroll a host with a one-time token. |
rotate_agent_key | agent_id (required) | Rotate an agent's keypair. |
rotate_host_key | issuer (required) | Rotate the host keypair for a provider. |
Workflow Example
Here is the standard workflow for connecting to a provider and executing a capability:
1. list_providers
→ See what providers are already known
2. search_providers({ intent: "deploy web apps" })
→ Find a provider if none are known (or discover_provider with a URL)
3. list_capabilities({ provider: "https://api.example.com" })
→ See what the provider offers
4. describe_capability({ name: "deploy_app", provider: "https://api.example.com" })
→ Understand the input schema before executing
5. connect_agent({ provider: "https://api.example.com", capabilities: ["deploy_app"], name: "deploy-bot" })
→ Authenticate and get an agent_id
→ If approval is required, the user will be prompted
6. agent_status({ agent_id: "..." })
→ Confirm the agent is active and capabilities are granted
7. execute_capability({ agent_id: "...", capability: "deploy_app", arguments: { app: "my-app", env: "production" } })
→ Run the capability with the correct arguments
Important Rules
- Never make raw HTTP requests to Agent Auth endpoints. Always use MCP tools.
- Always call
list_providersfirst. This tells you what's already configured. - Always call
describe_capabilitybeforeexecute_capability. You need the input schema. - Always call
agent_statusafterconnect_agent. The agent may be pending approval. - Save the
agent_idreturned byconnect_agent— every subsequent tool needs it. - Use constraints when connecting to limit agent permissions — pass them in the
capabilitiesparameter as objects withnameandconstraintsfields. - Handle approval flows. When
connect_agentreturns approval info (device code URL or CIBA), the user must approve before the agent becomes active. Pollagent_statusto check. - Errors return structured objects like
{ error: "message", code: "error_code" }— check these and retry or adjust accordingly.
Capability Constraints
When connecting, you can restrict what an agent can do with its capabilities:
{
"provider": "https://api.example.com",
"capabilities": [
"read_data",
{
"name": "transfer_money",
"constraints": {
"amount": { "max": 1000, "min": 1 },
"currency": { "in": ["USD", "EUR"] }
}
}
]
}
Constraint types: eq (exact match), min/max (numeric bounds), in/not_in (allowed/blocked values).
When to Use CLI vs MCP
- Use MCP tools when operating inside an MCP-enabled environment (Cursor, Claude Code, Claude Desktop) — the tools are already available and integrated.
- Use the CLI when running from a terminal directly, scripting, or when MCP is not available.
- Both expose the same operations and share the same storage (
~/.agent-auth/).
FAQ
What does the agent-auth-mcp skill do?
Use the Agent Auth MCP tools to discover providers, connect agents, manage capabilities, and execute operations through the MCP protocol. Use when working inside an MCP-enabled environment (Cursor, Claude Code, etc.) and need to authenticate agents, execute capabilities, or interact with Agent Auth providers.
How do I install agent-auth-mcp?
Run npx skills add https://github.com/better-auth/agent-auth --skill agent-auth-mcp in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/agent-auth-mcp/ (personal) or .claude/skills/agent-auth-mcp/ (project).
Which AI agents can use agent-auth-mcp?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is agent-auth-mcp safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains agent-auth-mcp?
It is published by better-auth in better-auth/agent-auth, and it is an official skill from the maker of the technology it covers. It has 109 recorded installs.
More from better-auth/agent-auth
agent-auth-cli
better-auth/agent-auth
Use the Agent Auth CLI (auth-agent) to discover providers, connect agents, manage capabilities, and execute operations. Use when the user wants to interact with an Agent Auth provider from the terminal, authenticate an agent, execute capabilities, or manage agent connections.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.