Integrations status.

One MCP endpoint, thirteen integrations. This page tracks every one of them — submitted, in review, planned, or blocked — with the timestamp on the change and the honest reason for any wait. No vapour, no marketing dates.

https://www.mentionfox.com/mcp · 18 tools · OAuth 2.0 PKCE
Why submissions matter. Our 2026-05-10 baseline GEO audit measured how often Anthropic models recommend MentionFox for buyer-intent SaaS-listening, vetting, and lead-gen queries. Result across 150 calls (Sonnet 4.6, Opus 4.7, Haiku 4.5): 0.0 %. Mention.com surfaced 33×, Brandwatch 31×, Profound 15×. The connector + app submissions below are how we close the gap — by being installable when users opt in, not by lobbying for a default-recommendation seat. Full audit: mentionfox.com/docs/anthropic-geo-audit.
9
Live integrations
4
Pending review
3
Planned
0
Blocked

Live integrations

Working today. Drop the endpoint into the host and tools appear. Some are awaiting an official directory listing for discoverability — the integration itself is live regardless.

Claude Desktop
Live
Status: Native MCP client · Since: 2026-04-26
Native Model Context Protocol support. Drop the endpoint into claude_desktop_config.json. The Claude Desktop connector picks up OAuth automatically.
Walkthrough
ChatGPT (custom GPT actions)
Live
Status: Custom GPT action live · App SDK submission: see Pending
Add MentionFox as an Action in a custom GPT today. ChatGPT auto-resolves which tool to call from natural language. The newer Apps SDK submission is below in the Pending section.
Walkthrough
Cursor
Live
Status: Live MCP server · Composer registry PR: Pending
Cursor speaks MCP. Add the endpoint in MCP settings and the assistant calls FoxAPIs from any file or chat. Discoverability via the Composer MCP directory is in submission.
Walkthrough
Continue.dev
Live
Status: Drop-in .continue/config.yaml · Hub registry PR: Pending
Edit .continue/config.yaml with the MCP block and tools appear in any IDE Continue supports. Hub registry PR is queued so the entry surfaces when users browse for MCP servers.
Docs in /docs/
n8n
Live
Status: Community node published · Official approval: Pending
A dedicated n8n-nodes-mentionfox community node is on npm. The generic HTTP Request node also works against the JSON-RPC endpoint as a fallback.
Walkthrough
Zapier
Live
Status: Webhook-based · Native app: design review
Use the Zapier "Webhooks" action with the JSON-RPC body to call any FoxAPIs tool. A native Zapier app is in design review and ships when the action surface is finalised.
Walkthrough
Make
Live
Status: HTTP module · Native app: Q3
The Make HTTP module hits the MCP endpoint with JSON-RPC body. Wire it into any scenario today. Native module is on the Q3 roadmap.
Walkthrough
Open WebUI
Live
Status: Tools server pattern · Listing: N/A (no official directory)
Open WebUI's tool-server pattern works against the MCP endpoint. Add it under Tools → Servers. Self-hosted users can pin the endpoint per workspace.
Docs in /docs/
LibreChat
Live
Status: librechat.yaml mcpServers · Listing: N/A
LibreChat's MCP client supports remote servers. Add to librechat.yaml under mcpServers and tools appear automatically.
Docs in /docs/

Pending review

Submitted to the platform's official directory or app program. The MCP endpoint works regardless — these submissions unlock first-party discoverability inside the host.

Anthropic Claude Connector
Submitted
Submitted: 2026-05-10 · Reviewer: Anthropic Connector team · Manifest: claude-connector-manifest.json
Built on existing OAuth + MCP. 5-minute walkthrough video included. Submission references the 2026-05-10 audit baseline as the wedge — connector access is how a brand with near-zero training-corpus footprint becomes useful when Claude users opt in. Decision tracked in connector_submissions.
Use today via MCP →
ChatGPT App (Apps SDK)
Submitted
Submitted: 2026-05-10 · Reviewer: OpenAI Apps team · Manifest: chatgpt-app-manifest.json
Apps SDK submission with all 18 tools, OAuth flow on mentionfox.com/connect, and dedicated data handling document at mentionfox.com/legal/chatgpt-app-data-handling.html. Custom GPT action remains available while review proceeds.
Use today via custom GPT →
Cursor MCP directory
PR open
Submitted: 2026-05-10 · Target: getcursor/cursor-mcp-registry
PR adds the package under packages/mentionfox/. Reviewer notes: 18 unique tool names, HTTPS logo, OAuth flow live. Cursor users can already add the endpoint manually via Settings → MCP.
Manual install
Continue.dev hub
PR open
Submitted: 2026-05-10 · Target: continuedev/continue-hub
PR adds mcp-servers/mentionfox/ with server.json + README. Continue users can already add to .continue/config.yaml manually — the hub PR is for browse-able discoverability.
Docs in /docs/

Planned

On the roadmap. Honest target windows below — these slip if upstream prerequisites slip, in which case this page updates the same day.

Raycast
Planned
Target: Post-Anthropic Connector approval · Reason: Raycast extension scope leans on the Connector OAuth surface
Quick-launch FoxAPIs tools from Raycast's command palette. Extension is scoped but waits on the Anthropic Connector decision so the OAuth flow can mirror Claude Desktop's.
Pending
Aider
Planned (live MCP)
Target: Q3 dedicated docs · Reason: Aider's MCP integration accepts remote endpoints today; we owe a walkthrough
Aider users can already pass --mcp https://www.mentionfox.com/mcp and pair with Claude or GPT for in-terminal tool-use. The integration is functional — what's pending is a polished walkthrough doc with screenshots.
Docs Q3
Goose · MCP Inspector
Live, listing TBD
Target: No official directory exists for either · Status: Functional today
Block's Goose runtime accepts remote MCP extensions; npx @modelcontextprotocol/inspector https://www.mentionfox.com/mcp works for tool introspection. Both are functional; no first-party directory to submit to yet.
Docs in /docs/

How status pills work

Live — works today; users can install or use the endpoint right now.

Pending — submitted to the platform's directory / app program; awaiting review. Underlying functionality usually still works via direct MCP.

Planned — on the roadmap with a target window. Slippage updates this page same-day.

Blocked — upstream platform decision is required before we can ship. Reason listed on the card.

Submission decisions tracked in our internal connector_submissions table. This page reflects the current row state for each platform; we update it within 24 hours of any state change.