@mentionflow/mcp

Ask Claude about your AI-visibility data. One line, no code.

MentionFlow runs an MCP server at https://app.mentionflow.ai/api/mcp (Streamable HTTP, bearer-key auth). Clients that speak HTTP, like Cursor and Claude Code, connect to it directly. Claude Desktop can only launch local stdio servers, and that is what this package fixes: it connects to the remote server with your API key and re-serves it on stdio, forwarding everything verbatim in both directions. It hardcodes nothing, so new MentionFlow tools show up in Claude the moment the server ships them. No package update needed.

Claude Desktop setup

1. Create an API key in MentionFlow → Settings → API keys (mf_…).
2. In Claude Desktop: Settings → Developer → Edit Config. Add this:

{
  "mcpServers": {
    "mentionflow": {
      "command": "npx",
      "args": ["-y", "@mentionflow/mcp"],
      "env": { "MENTIONFLOW_KEY": "mf_your_key_here" }
    }
  }
}

3. Restart Claude Desktop and ask: "Which prompts mention my brand the most this week?"

You need Node.js 18 or newer on the machine.

Other stdio-only clients

Same shape everywhere: run npx -y @mentionflow/mcp as the server command with MENTIONFLOW_KEY in its environment.

npx -y @mentionflow/mcp --help

Usage: mentionflow-mcp [endpoint] [--key mf_…] [--endpoint url]

Environment:
  MENTIONFLOW_KEY       API key (mf_…), from MentionFlow → Settings → API keys
  MENTIONFLOW_ENDPOINT  MCP endpoint (self-hosted only; default https://app.mentionflow.ai/api/mcp)

Self-hosted MentionFlow

Point the bridge at your own origin:

"env": {
  "MENTIONFLOW_KEY": "mf_your_key_here",
  "MENTIONFLOW_ENDPOINT": "https://mf.example.com/api/mcp"
}

The bridge refuses http:// endpoints outside localhost. Your key must never travel as cleartext.

Security notes

• Use a dedicated API key for this integration so you can revoke it independently (Settings → API keys).
• The key stays in your MCP client's config on your machine. The bridge sends it only as the Authorization header to the endpoint you configured, nowhere else.
• The MCP surface is read-only. It serves the same data as the v1 REST API and cannot modify your workspace.