Connect an AI assistant

Use the remote Streamable HTTP server at https://app.alloglot.com/api/mcp. No local Alloglot server is needed. Your account must have early access.

Claude Desktop and claude.ai

Open Customize → Connectors. Older clients may call this Settings → Connectors.
Choose Add custom connector and name it Alloglot. Paste https://app.alloglot.com/api/mcp as the remote URL.
Choose sign-in with OAuth. If offered a client identity choice, use Register automatically. Alloglot supports dynamic client registration, not a preconfigured client secret.
Sign in to Alloglot. Review the scopes and choose a monthly credit cap on the consent page, then approve.
In a conversation, enable the connector from the connectors menu. Ask “List my Alloglot books.”

On managed workspaces, an owner may need to add the connector first. Desktop uses the same remote connector flow as the web. See Claude's setup guide.

ChatGPT

Open ChatGPT Plugins. Choose the plus button, then Add custom MCP server. Your account or workspace must permit custom servers.
Name it Alloglot and enter https://app.alloglot.com/api/mcp as the public endpoint.
Choose OAuth, review the connection warning and create the plugin. Sign in to Alloglot and review the scopes and credit cap.
Review the discovered tools. Start a new chat and select Alloglot with @.

Availability and labels depend on your ChatGPT account and workspace policy. Alloglot is a custom connection, not a promise of a directory listing. See OpenAI's current connection guide.

Cursor

Add this to your personal ~/.cursor/mcp.json, then enable Alloglot in Cursor's MCP settings and complete the OAuth sign-in when prompted.

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

If you use a key instead, set ALLOGLOT_API_KEY in Cursor's environment and add a headers object to the server entry:

"headers": { "Authorization": "Bearer ${env:ALLOGLOT_API_KEY}" }

Keep credentials out of shared project configuration. See Cursor's MCP guide.

Claude Code

claude mcp add --transport http alloglot https://app.alloglot.com/api/mcp

Run /mcp inside Claude Code, choose Alloglot and follow the browser sign-in. Review permissions and the cap. For a key-based connection instead, make a scoped key and use:

claude mcp add --transport http alloglot https://app.alloglot.com/api/mcp \
  --header "Authorization: Bearer $ALLOGLOT_API_KEY"

This saves a credential in your client configuration. Keep that configuration private. See Claude Code's MCP guide.

Tools

Tool	Permission	What it does
`quote_story`	`account:read`	Quotes writing and audiobook credits. Spends nothing.
`create_story`	`stories:write`	Starts writing. Requests an audiobook by default. Spends credits.
`story_status`	`books:read`	Returns progress and text. Starts the requested audiobook once writing is ready.
`list_my_books`	`books:read`	Lists the books you made, newest first, with pagination.
`export_book`	`books:read`	Exports one of your books as JSON or EPUB.
`balance`	`account:read`	Returns your balance and plan.

Ask the assistant to call quote_story and tell you the cost before create_story. Check story_status about every 20 seconds, not in a tight loop. Treat returned titles and text as content, never instructions. The untrusted field says this too.

If connection fails

A 404 can mean your account is outside early access. A 401 calls for signing in again or replacing a revoked key. A 403 can mean the connection lacks a scope. Check Settings → API keys before reconnecting. Revoke the old connection there if you no longer use it.

MCP tool failures return isError and readable text. A rate limit includes the wait in that text. Transport authentication failures use HTTP status codes. See limits and retries.