MCP Server
Connect Reaudit to Meta Muse
Add Reaudit as a Meta Muse custom connector via OpenAPI — OAuth or API key auth for AI visibility, audits, prompts, and analytics.
Meta Muse is Meta's personal AI agent. Muse does not support MCP — add Reaudit as a custom connector using our OpenAPI spec and OAuth or API key auth. Once connected, Muse can run all Reaudit capabilities: AI visibility scores, audits, prompts, citations, social, and analytics.
MCP vs OpenAPI
Cursor, Claude, and ChatGPT use the Reaudit MCP server at
mcp.reaudit.io. Muse uses the REST OpenAPI spec at reaudit.io/openapi/reaudit-v1.json — same tools, different transport.Setup (custom connector)
- 1Ensure you have an active Reaudit subscription with MCP access (Professional+ or MCP Pack)
- 2Create an API key in Dashboard → Settings → MCP API Keys (optional if using OAuth)
- 3Send the connector prompt below to Muse
- 4When Muse asks for credentials, use OAuth (recommended) or paste your
rau_*API key as a Bearer token — do not paste the key in the initial message
Muse connector prompt
Connect Reaudit as a custom connector. OpenAPI: https://reaudit.io/openapi/reaudit-v1.json
Auth docs: https://reaudit.io/auth.md
Use OAuth if available; otherwise use my Reaudit API key as a Bearer token when I provide it.Example prompts
- "What's my AI visibility score?"
- "Run an SEO audit on my homepage"
- "Which prompts mention my brand in ChatGPT?"
- "Show citation analytics for the last 30 days"
- "Compare my visibility vs competitors"
Resources
- OpenAPI spec — machine-readable API for Muse
- Authentication guide — OAuth PKCE + API keys
- Connect page — MCP setup for Codex, Cursor, Claude
- Muse Connector Platform — official directory submission (partner program)
Troubleshooting
Muse tries OAuth but fails
Use a Bearer API key instead. Create one in the dashboard and give it to Muse when prompted.
Long-running jobs time out
Audits and content generation can take 1–3 minutes. Ask Muse to poll the read endpoint (e.g.
list_audits after run_audit) — never retry the same POST (duplicate credit charges). OpenAPI marks these with x-long-running and x-poll-operationId.403 Forbidden
Your plan may not include MCP access, or the API key is read-only for that operation.
The OpenAPI spec exposes 235+ user tools under
/api/mcp/v1/*. Almost every call requires projectId — start with list_projects.