Add SuperEbook to GitHub Copilot. The CLI, Visual Studio, JetBrains, Xcode and Eclipse.
GitHub Copilot can use SuperEbook’s MCP server wherever it runs, and plan and write books in your SuperEbook account from your code and notes. The server is the same everywhere, but each app reads its config a little differently: here is the right entry for each. For VS Code, see its own guide.
Server URL
https://www.superebook.ai/api/mcpPaste it exactly as it is, with www.
Before you start
- A SuperEbook account with Starter, Pro or any credit pack. SuperEbook’s Free plan doesn’t include connecting apps: see plans.
- An API key, for every app here but Visual Studio, which signs in instead. In Settings → Connect apps, choose Create API key and copy it: you see the whole key only once, it starts
ebk_live_, and it needs a verified email address. Give each app its own key. - Copilot Business or Enterprise: an admin must turn on the MCP servers in Copilot policy first; it’s off by default. Copilot Free, Pro, Pro+ and Max aren’t governed by it.
- The www address,
https://www.superebook.ai/api/mcp, in every app: the address without www can’t sign you in.
Copilot CLI
Create an API key.
In SuperEbook, open Settings → Connect apps and choose Create API key. Name it after the Copilot CLI, then copy it: you see the whole key only once, and it starts
ebk_live_. It needs a verified email address.In a Copilot CLI session, enter /mcp add.
Move between fields with Tab. Server Name:
superebook. Server Type: press the number for HTTP or SSE. URL:https://www.superebook.ai/api/mcp. HTTP Headers:{"Authorization": "Bearer ebk_live_YOUR_KEY"}. Tools:*. Press Ctrl+S: the server works at once, with no restart.
Or add it with one command, which saves it to ~/.copilot/mcp-config.json. The key also lands in your shell history, so the form or the file is safer:
copilot mcp add --transport http --header "Authorization: Bearer ebk_live_YOUR_KEY" superebook https://www.superebook.ai/api/mcp
Or write it in ~/.copilot/mcp-config.json yourself. A project’s .mcp.json or .github/mcp.json works too, but loads only after you trust the folder, and never commit a real key to one. The CLI doesn’t read .vscode/mcp.json.
{
"mcpServers": {
"superebook": {
"type": "http",
"url": "https://www.superebook.ai/api/mcp",
"headers": {
"Authorization": "Bearer ebk_live_YOUR_KEY"
},
"tools": [
"*"
]
}
}
}To sign in instead of using a key, add the server without the header and run /mcp auth. The CLI’s changelog says it signs in to MCP servers through the browser with dynamic client registration, but nobody has tried it with SuperEbook yet. SuperEbook’s page opens in your browser. If the app is coming back to your own computer, the page names it, with no warning; if it isn’t, the page warns you, and you tick the box only if you started connecting yourself. Then choose Allow.
Visual Studio
Open the chat pane and switch to Agent mode.
Visual Studio 2022 17.14 or later, or Visual Studio 2026.
Select Tools, then the plus (+) button.
In Visual Studio 2026 choose Add custom MCP server; in Visual Studio 2022 the Add MCP server dialog opens.
Enter the name superebook, the type HTTP/SSE and the server URL, then Save.
Or create
%USERPROFILE%\.mcp.json, for every solution, or.mcp.jsonin a solution’s folder, with this:{ "servers": { "superebook": { "url": "https://www.superebook.ai/api/mcp" } } }Sign in from the code lens.
In the
.mcp.jsonfile, choose Authentication Required above the server (later, Manage Authentication) and sign in in the browser window. If there’s no code lens, turn it on in Tools → Options → Text Editor → CodeLens.SuperEbook’s page opens in your browser. If the app is coming back to your own computer, the page names it, with no warning; if it isn’t, the page warns you, and you tick the box only if you started connecting yourself. Then choose Allow.
Turn on its tools.
Tools start switched off: turn them on in the tool picker, then approve each one when asked (Allow in Visual Studio 2022, Confirm in 2026).
Not yet tested from Visual Studio. Microsoft documents signing in to remote servers but no header, so there’s no key route here; if signing in fails, tell us.
JetBrains IDEs
Open Copilot’s MCP settings.
Click the Copilot icon in the lower right corner, choose Open Chat, and make sure you’re in Agent mode. Click the tools icon (Configure your MCP server) at the bottom of the chat, then Add MCP Tools.
Paste the entry into the mcp.json that opens.
Replace
ebk_live_YOUR_KEYwith your key from Settings → Connect apps. The header goes underrequestInit.{ "servers": { "superebook": { "url": "https://www.superebook.ai/api/mcp", "requestInit": { "headers": { "Authorization": "Bearer ebk_live_YOUR_KEY" } } } } }Click the tools icon again: superebook’s tools are listed.
Xcode
Open GitHub Copilot for Xcode’s settings.
It needs the GitHub Copilot for Xcode extension. In a workspace, use Editor → GitHub Copilot → Open GitHub Copilot for Xcode Settings.
Select the MCP tab, click Edit Config, and paste the entry.
The same entry as JetBrains’, with your key in place of the placeholder.
{ "servers": { "superebook": { "url": "https://www.superebook.ai/api/mcp", "requestInit": { "headers": { "Authorization": "Bearer ebk_live_YOUR_KEY" } } } } }
Eclipse
Open Copilot’s MCP settings.
Eclipse 2024-09 or later. Click the Copilot icon in the status bar, choose Open Chat, then the Configure Tools… icon. Or go to Edit preferences → GitHub Copilot → MCP.
Paste the entry under Server Configurations.
The same entry as JetBrains’; Eclipse keeps it in its preferences, not a file.
{ "servers": { "superebook": { "url": "https://www.superebook.ai/api/mcp", "requestInit": { "headers": { "Authorization": "Bearer ebk_live_YOUR_KEY" } } } } }
For organization admins
- Organization: your profile picture → Organizations → the organization → Settings. In the sidebar, under Code, planning, and automation, click Copilot, then Policies. Under Features, set MCP servers in Copilot to Enabled.
- Enterprise: the enterprise → AI controls → MCP, and set MCP servers in Copilot to Enabled everywhere.
- If Restrict MCP access to registry servers is set to Registry only, only servers in your registry run, so SuperEbook needs adding to it.
Try it
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.
- “Read CHANGELOG.md and use SuperEbook to plan a how-to guide on upgrading to v3.”
- “Turn docs/workshop.md into a SuperEbook workbook and show me the chapters first.”
- “List my SuperEbook books.”
- “How long until my book is written?”
If it doesn’t work
- MCP servers are switched off
- On Copilot Business or Enterprise, the MCP servers in Copilot policy is off until an admin turns it on (see For organization admins).
- Only registry servers are allowed
- Your organization set Restrict MCP access to registry servers to Registry only. Ask an admin to add SuperEbook to the registry.
- The Copilot CLI ignores a project’s .mcp.json
- Project files load only after you trust the folder. The CLI never reads .vscode/mcp.json.
- Visual Studio shows no Authentication Required
- Turn on code lenses in Tools → Options → Text Editor → CodeLens, then open .mcp.json again.
- SuperEbook refuses the key
- Check the whole key follows “Bearer ” in the header, that the address has www, and that the key isn’t revoked in Settings.
For credits, limits and the other messages an app may relay, see if something goes wrong.