Inside ChatGPT, Claude and Grok

Inside Grok

On grok.com, one connector URL. In Cursor or Grok Bot, the URL and an x-api-key header.

Custom connectors are on Grok's paid plans. On Grok Business and Enterprise a team admin may have to add the connector first.

Grok's custom connectors take the server URL, so the key rides at the end of it, exactly as for claude.ai. The app shows this URL next to every new key.

  1. In the app, Settings → API & MCP → Create a key. Copy the connector URL shown for Claude and Grok.
  2. On grok.com, open Connectors (grok.com/connectors) → New Connector → Custom.
  3. Name it AutomateSocials and paste the URL. It needs no other sign-in.
  4. In a chat, turn the connector on and say what you want.
https://automatesocials.net/mcp/sk_live_...
That URL is your key. Keep it as you would a password, and revoke the key under Settings → API & MCP if it leaks: the URL stops working at once.

Inside Cursor / Grok Bot

  1. In AutomateSocials: Settings → API & MCP → Create a key. Copy only the sk_live_… key (or the connector URL shown).
  2. Ask the Grok Bot or Cursor agent: “Add AutomateSocials MCP”, and give it the key through its secure secret field. Do not paste sk_live_ keys into the normal chat.
  3. The agent adds a remote MCP server with the URL https://automatesocials.net/mcp and the header x-api-key: sk_live_…. In Cursor, use the header rather than putting the key at the end of the URL.
  4. Check that it connected: the AutomateSocials tools load. A safe first request is “List my connected social accounts”.
  5. One key is one project. If you run several brands or clients, add a separate connector for each, with its own name and key, so posts never cross between them.
  6. If a key was ever pasted into a normal chat, revoke it under Settings → API & MCP and create a new one.
URL     https://automatesocials.net/mcp
Header  x-api-key: sk_live_...

Questions

Does one key work for all my brands? No. A key belongs to one project. Use one connector per brand, each with that project's key.

grok.com or Cursor? grok.com takes the full connector URL with the key at the end. Cursor and Grok Bot take the URL plus an x-api-key header, or the agent's secure add flow.

Where is the .env? You do not need one for Grok Bot or Cursor. The key lives in the connector settings or the agent's secure secret field, not in your project's code.

From the xAI API

Your own code calling Grok can use the same server as a remote MCP tool: the URL without the key, and the key as the authorization token.

{ "type": "mcp",
  "server_url": "https://automatesocials.net/mcp",
  "server_label": "automatesocials",
  "authorization": "sk_live_..." }
← All articlesNext: Claude Code and Cursor