Add Rankhog to your AI client

Every client connects to the same server address and signs in to Rankhog with OAuth. You pick your organization and what the app may do on Rankhog's consent page: every box starts ticked, sending included, and you can untick any before you allow it.

https://api.rankhog.com/mcp

For a page per client with prompts to try, see Reddit MCP for your AI. For scopes, API keys and the tools themselves, see the MCP overview.

Claude

Works on claude.ai, Claude Desktop and the Claude phone apps. Connectors belong to your Claude account.

1. Open the prefilled Add custom connector form. It fills in Rankhog's name and address.
2. Check the address and click Add.
3. Sign in to Rankhog and allow it.
4. Start a new chat. Rankhog shows up in the chat's tools menu.

Team and Enterprise: an owner adds Rankhog once with the team form. Then each member clicks Connect under Customize, Connectors.

Limits: the free Claude plan allows one custom connector. Custom connectors sign in with your Rankhog account and don't take an API key.

Claude Duet has no install of its own. Anthropic says it uses your Claude account's connectors, but not yet whether connectors you add yourself work in its background checks.

If something goes wrong:

• The sign-in window doesn't open: allow pop-ups for claude.ai and click Connect again.
• Claude can't reach the server: the address must be exactly https://api.rankhog.com/mcp.
• No Rankhog tools in the chat: turn Rankhog on in the chat's tools menu, or start a new chat.

Claude Code

Add Rankhog for every project:

claude mcp add --transport http --scope user rankhog https://api.rankhog.com/mcp

Then start Claude Code and sign in:

/mcp

Pick rankhog, sign in to Rankhog in your browser and allow it. Leave out --scope user to add Rankhog to the current project only. Your settings live in ~/.claude.json; a project's .mcp.json is shared through git.

If you already added Rankhog on claude.ai, it shows up in Claude Code too when you sign in with a Claude plan.

API key, for scripts and CI. Put the key in RANKHOG_API_KEY first:

claude mcp add --transport http rankhog https://api.rankhog.com/mcp --header "Authorization: Bearer $RANKHOG_API_KEY"

If something goes wrong:

• /mcp says rankhog needs you to sign in: pick it and choose to sign in. If no browser opens, copy the link Claude Code prints.
• The server fails to connect: run claude mcp list and check the address ends in /mcp.
• Wrong organization: disconnect the app in Rankhog under Connected apps and sign in again.

ChatGPT

Custom servers with full use, drafts included, are for ChatGPT Business, Enterprise and Edu, on the web. On Business, only an admin or owner adds the plugin. Pro can connect a custom server to read only, and Plus isn't offered. On Plus or Pro, use Codex, which comes with those plans.

1. Open Plugins in ChatGPT on the web.
2. Click the plus button, then Add custom MCP server.
3. Name it Rankhog and paste the address as the server URL:

https://api.rankhog.com/mcp

4. Choose OAuth, tick that you understand the warning, create it as a plugin and check the tools it found.
5. Sign in to Rankhog and allow it.
6. In a new chat, type @ and pick Rankhog.

ChatGPT asks you to confirm every action that writes. ChatGPT has no field for an API key.

If something goes wrong:

• No Add custom MCP server option: your plan or role doesn't allow it. Ask your workspace admin, or use Codex.
• A new Rankhog tool doesn't show up: workspaces freeze a plugin's tools when an admin approves them. Ask the admin to refresh it.

Codex

Works in the Codex CLI, the Codex IDE extension and the ChatGPT desktop app, on Plus and Pro too.

codex mcp add rankhog --url https://api.rankhog.com/mcp

codex mcp login rankhog

Type /mcp in Codex to check that rankhog is listed. The CLI, the IDE extension and the desktop app share ~/.codex/config.toml:

[mcp_servers.rankhog]
url = "https://api.rankhog.com/mcp"

In the ChatGPT desktop app you can also add it under Settings, MCP servers, then restart the app. Codex Cloud tasks can't use custom servers.

API key, for scripts and CI. Put the key in RANKHOG_API_KEY first:

codex mcp add rankhog --url https://api.rankhog.com/mcp --bearer-token-env-var RANKHOG_API_KEY

If something goes wrong:

• The login opens nothing: run codex mcp login rankhog --no-browser, open the link it prints, then paste back the address your browser lands on.
• rankhog is missing from /mcp: restart Codex. It loads servers when it starts.

Cursor

Use the one-click install link, click Install in Cursor, then click Needs login next to rankhog under Cursor Settings, MCP.

To add it by hand, put this in ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one project:

{
  "mcpServers": {
    "rankhog": {
      "url": "https://api.rankhog.com/mcp"
    }
  }
}

API key: Cursor fills in environment values in headers. Put the key in RANKHOG_API_KEY first:

{
  "mcpServers": {
    "rankhog": {
      "url": "https://api.rankhog.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:RANKHOG_API_KEY}"
      }
    }
  }
}

If something goes wrong:

• The link opens a web page but not Cursor: install Cursor, then click the link again, or add the JSON by hand.
• rankhog shows a red dot: click Needs login under Cursor Settings, MCP, and check the address ends in /mcp.

Grok

Grok on the web:

1. Open grok.com/connectors.
2. Click New Connector, then Custom.
3. Paste the address and sign in to Rankhog:

https://api.rankhog.com/mcp

On Grok Business and Enterprise, an admin adds Rankhog in the xAI console first. Grok's docs don't say whether the free plan can add a custom connector. The @grok replies on X can't use connectors.

Grok Bot adds a server when you ask in chat. It needs an X Premium, Super or Ultra plan. Paste this to your Bot and approve the sign-in card it shows:

Add a custom MCP server called rankhog at https://api.rankhog.com/mcp.
When it asks me to sign in, wait while I approve it.
Then tell me which Rankhog products you can see. Don't send anything to Reddit.

Apps you add to Grok Bot work for every Bot on your account, and team admins can block them.

Grok Build, xAI's terminal agent. Sign-in starts the first time it uses Rankhog, or type /mcps and press i:

grok mcp add --transport http rankhog https://api.rankhog.com/mcp

With an API key in RANKHOG_API_KEY:

grok mcp add --transport http rankhog https://api.rankhog.com/mcp --header "Authorization: Bearer $RANKHOG_API_KEY"

If something goes wrong:

• Custom is greyed out: your team admin has to add Rankhog in the xAI console first.
• Grok Bot can't finish the sign-in: open the Connect card it shows, sign in there, then tell the Bot you're done.

Hermes Agent

Hermes Agent is Nous Research's open-source agent.

hermes mcp add rankhog --url https://api.rankhog.com/mcp --auth oauth

Sign in from a fresh terminal, not inside a running Hermes Agent session, which waits only 30 seconds:

hermes mcp login rankhog

In a chat that was already running, type /reload-mcp. The command writes this to ~/.hermes/config.yaml:

mcp_servers:
  rankhog:
    url: "https://api.rankhog.com/mcp"
    auth: oauth

API key, for a server with no browser. Put the key in RANKHOG_API_KEY and use headers instead of auth:

mcp_servers:
  rankhog:
    url: "https://api.rankhog.com/mcp"
    headers:
      Authorization: "Bearer ${RANKHOG_API_KEY}"

If something goes wrong:

• Sign-in times out: run the login command from a fresh terminal.
• Hermes Agent says rankhog has no tools: type /reload-mcp, or restart Hermes Agent.

OpenClaw

OpenClaw's mcp commands need the local Gateway stopped. Keep --transport streamable-http: without it, OpenClaw falls back to an older transport.

openclaw mcp add rankhog --url https://api.rankhog.com/mcp --transport streamable-http --auth oauth

openclaw mcp login rankhog

openclaw mcp doctor rankhog --probe

Then start the Gateway again. Without a terminal, use the Control UI: Settings, MCP, Add server, pick Streamable HTTP and paste the address. The server lands in ~/.openclaw/openclaw.json under mcp.servers.

Install OpenClaw only from openclaw.ai or npm, and add Rankhog only with OpenClaw's own command or settings, never an install link someone sends you.

API key: leave out --auth oauth, because OpenClaw ignores a key header while sign-in is on:

openclaw mcp add rankhog --url https://api.rankhog.com/mcp --transport streamable-http --header "Authorization: Bearer $RANKHOG_API_KEY"

If something goes wrong:

• The login command fails: stop the Gateway and run it again.
• Rankhog connects but its tools fail: check the transport is streamable-http.

Other clients

Any client that takes a remote MCP server with OAuth works the same way: add the address, then sign in to Rankhog when it asks.

• VS Code: add an http server with the address in .vscode/mcp.json or your user profile, under servers.
• Gemini CLI: gemini mcp add --transport http rankhog https://api.rankhog.com/mcp.
• Le Chat: Connectors, Add Connector, Custom MCP Connector, then the address.