Add SuperEbook to Grok. On grok.com, in the xAI API or the Grok CLI.

• A SuperEbook account with Starter, Pro or any credit pack. SuperEbook’s Free plan doesn’t include connecting apps: see plans.
• Plans. xAI says connectors are available to all Grok users, but doesn’t say which plans can add a custom MCP server, so check yours.
• Grok Business and Enterprise. A team admin with Team Read-Write permission adds the connector first; then each member connects their own account.
• An API key for the xAI API and the Grok CLI, from Settings → Connect apps. On grok.com you sign in instead.

Not yet tested with Grok. These are xAI’s steps, and SuperEbook should work with them, but nobody has connected it from grok.com yet. If a step doesn’t go as described, tell us.

1. 1

   Go to grok.com/connectors, choose New Connector, then Custom.

   Or, in a chat: + in the chat box, then Connectors, then + Add connector.

2. 2

   Enter the server URL and sign in.

   Enter https://www.superebook.ai/api/mcp, with www, and complete the sign-in Grok asks for.

3. 3

   Allow it on SuperEbook.

   Sign in to SuperEbook if it asks. SuperEbook’s page asks “Connect an app at …?” with Grok’s web address, and warns that it isn’t a Claude address: SuperEbook trusts only Claude’s own addresses and your computer, so every other app gets this warning. If you started connecting from Grok yourself, tick the box that says so (“I started connecting from … myself.”) and choose Allow.

4. 4

   Ask Grok for a book.

   Grok finds SuperEbook’s nine tools on its own and uses them in your conversations.

Grok’s iOS and Android apps list connectors under Settings → Connectors. xAI doesn’t describe adding a custom server there, so add SuperEbook on grok.com.

1. 1

   An admin opens the connectors page in the cloud console.

   At console.x.ai, pick the team, then Grok Business → Connectors. Adding a connector needs Team Read-Write permission.

2. 2

   Choose + Add Connector, then Other.

   Enter https://www.superebook.ai/api/mcp and complete the authentication it asks for.

3. 3

   Each member connects their own account.

   On grok.com/connectors. Each person signs in to their own SuperEbook account, so books and credits stay theirs.

For developers: a request to xAI’s Responses API can give Grok SuperEbook as a remote MCP tool. xAI connects to the server for you, with your key in a header.

1. 1

   Create an API key.

   In SuperEbook, open Settings → Connect apps and choose Create API key. Name it after the app that sends the requests, then copy it: you see the whole key only once, and it starts ebk_live_. It needs a verified email address.

2. 2

   Add SuperEbook to the request’s tools.

   server_url and server_label are required. Put the whole Authorization: Bearer … value in headers, not in authorization: SuperEbook needs the word Bearer, and xAI doesn’t say whether authorization adds it.

   The model is the one xAI’s own examples use today; use a current one.

   Copy xAI API request

   {
     "model": "grok-4.7",
     "input": [
       {
         "role": "user",
         "content": "List my SuperEbook books."
       }
     ],
     "tools": [
       {
         "type": "mcp",
         "server_url": "https://www.superebook.ai/api/mcp",
         "server_label": "superebook",
         "server_description": "Plans and writes books in a SuperEbook account",
         "allowed_tools": [
           "get_account",
           "list_books",
           "create_book",
           "plan_book",
           "get_plan",
           "edit_plan",
           "get_progress",
           "get_download_links"
         ],
         "headers": {
           "Authorization": "Bearer ebk_live_YOUR_KEY"
         }
       }
     ]
   }

3. 3

   Choose which tools Grok may call.

   allowed_tools lists them, and left out it allows all nine. The API can’t stop to ask anyone first (require_approval isn’t supported), so this example leaves out start_writing, the tool that spends credits. Add it only if your own code confirms the price with the person before Grok writes.

In xAI’s Python SDK, the same fields are allowed_tool_names and extra_headers:

from xai_sdk.tools import mcp

mcp(
    server_url="https://www.superebook.ai/api/mcp",
    server_label="superebook",
    allowed_tool_names=["get_account", "list_books", "create_book", "plan_book", "get_plan", "edit_plan", "get_progress", "get_download_links"],
    extra_headers={"Authorization": "Bearer ebk_live_YOUR_KEY"},
)

1. 1

   Create an API key.

   In SuperEbook, open Settings → Connect apps and choose Create API key. Name it after the Grok CLI, then copy it: you see the whole key only once, and it starts ebk_live_. It needs a verified email address.

2. 2

   Add the server.

   One command saves it, key and all, in ~/.grok/config.toml. Replace ebk_live_YOUR_KEY with your key.

   Copy Grok CLI command

   grok mcp add --transport http superebook https://www.superebook.ai/api/mcp --header "Authorization: Bearer ebk_live_YOUR_KEY"

3. 3

   Or keep the key out of the file.

   Write the entry in ~/.grok/config.toml yourself, with ${SUPEREBOOK_KEY} where the key goes, and set that variable in your shell profile. Grok fills it in from your environment when it loads.

   Copy Grok CLI config

   [mcp_servers.superebook]
   url = "https://www.superebook.ai/api/mcp"
   headers = { "Authorization" = "Bearer ${SUPEREBOOK_KEY}" }

4. 4

   Check it.

   grok mcp list shows it, and grok mcp doctor superebook checks its configuration and connection.

Without a header, the Grok CLI signs in through your browser the first time it needs to; in its terminal interface, /mcps then i signs in. We haven’t tried that with SuperEbook yet, so this guide uses a key.

Once it’s connected, ask for a book in plain words. Planning is free, and the app is told to quote the price and wait for your yes before it writes.

• “Use SuperEbook to plan a lead magnet on tax basics for new freelancers.”
• “Show me the chapters of my newest SuperEbook book, and make the brief punchier.”
• “What would a course companion cost in credits, and how many do I have?”
• “How far along is the book I started this morning?”

Grok asks for an OAuth client ID

SuperEbook has none to give: apps register themselves with it. Leave the field empty if Grok lets you; if it won’t carry on without one, use the Grok CLI or the xAI API with a key, and tell us.

You chose Cancel, and SuperEbook’s page says “Cancelled. You can close this tab.”

Grok isn’t told you cancelled: SuperEbook sends answers back only to Claude and to apps on your own computer. Close the tab and start connecting again from Grok.

The xAI API’s calls to SuperEbook are refused

Send the key as the whole header value, “Bearer ” and then the key, in headers. SuperEbook refuses a key without the word Bearer, and xAI doesn’t say whether its authorization field adds it.

The Grok CLI can’t connect

Run grok mcp doctor superebook. If you used ${SUPEREBOOK_KEY} in config.toml, check the variable is set in the shell Grok starts from.

For credits, limits and the other messages an app may relay, see if something goes wrong.

• How connecting works
• Credits and limits
• What an app can see
• Claude app
• ChatGPT
• Perplexity
• Le Chat
• Claude Code
• Cursor
• VS Code
• GitHub Copilot
• Codex
• Gemini CLI
• Zed
• Devin Desktop
• Other apps