Mcp Api
Manage users, apps, and FusionAuth configuration from your agent during auth integration work on a self-hosted or cloud instance.
Overview
io.fusionauth/mcp-api is a MCP server for the Build phase that lets agents call your FusionAuth instance API for identity and app configuration via generated tools.
What is this MCP server?
- Preview MCP server (@fusionauth/mcp-api) over stdio npm package
- Configurable tool surface via USE_TOOLS prefixes (e.g. retrieve, search)
- Requires API_KEY_APIKEYAUTH and API_BASE_URL for your FusionAuth host
- Maps FusionAuth OpenAPI operations into agent-callable tools
- Preview release; package version 0.1.14
- Required env: API_KEY_APIKEYAUTH, API_BASE_URL
- Optional USE_TOOLS prefix filter for generated MCP tools
Community signal: 1 GitHub stars.
What problem does it solve?
Builders integrating FusionAuth keep bouncing between API docs and curl while their agent cannot safely inspect or update auth configuration on the running instance.
Who is it for?
Developers actively integrating FusionAuth into a SaaS or API who want agent-driven API operations against a known instance URL.
Skip if: Teams who only need conceptual auth guidance without API access, or who should use the FusionAuth docs MCP instead of mutating instance data.
What do I get? / Deliverables
After configuring API key and base URL, your agent can use FusionAuth MCP tools to retrieve and manage instance resources aligned with your USE_TOOLS filter.
- Agent-callable FusionAuth API tools scoped by optional USE_TOOLS
- Faster auth integration debugging without manual REST repetition
- Preview release alignment with FusionAuth OpenAPI (v0.1.14 package)
Recommended MCP Servers
Journey fit
FusionAuth API access is used while wiring authentication and identity into the product—core Build work, especially backend integrations. Auth platform APIs are integration tasks: provisioning apps, keys, and users against a running FusionAuth instance fits build → integrations.
How it compares
Live FusionAuth API MCP (preview), not the read-only FusionAuth documentation MCP server.
Common Questions / FAQ
Who is io.fusionauth/mcp-api for?
It is for developers building with FusionAuth who want MCP-enabled agents to interact with their instance API using an API key and base URL.
When should I use io.fusionauth/mcp-api?
Use it during build-phase auth integration when you need programmatic retrieve, search, or other API actions against FusionAuth from your agent.
How do I add io.fusionauth/mcp-api to my agent?
Install @fusionauth/mcp-api, set API_KEY_APIKEYAUTH and API_BASE_URL in the MCP env block, optionally set USE_TOOLS, and register the stdio server in your MCP client.