FusionAuth Documentation MCP server
Productivityv1.0.0streamable-httpai.fusionauth.dev
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 423ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo fusionauth-docs-mcp@1.0.0 |
| tooling | 35 / 35 | tools/list OK: 2 tools e.g. "ask_fusionauth_question"; 2/2 described, 2/2 fully-typed schemas, median description 41 chars |
| latency | 10 / 10 | initialize round-trip 423ms |
| provenance | 5 / 15 | description present; no repository URL; version 1.0.0; namespace io.fusionauth does NOT match remote host (expected *.fusionauth.io) |
Score 90/100 · latency 423ms · 2 tools · auth: open
Claude Code:
claude mcp add --transport http mcp-docs https://ai.fusionauth.dev/mcp/docs
Generic MCP client config:
{ "mcpServers": { "mcp-docs": { "type": "http", "url": "https://ai.fusionauth.dev/mcp/docs" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/io.fusionauth/mcp-docs · referral link https://mcpqueen.com/go/io.fusionauth/mcp-docs (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.fusionauth/mcp-docs)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 12:30 | A | 90 | 423ms |