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.

Verify without spending

For a connection test, request only account:read and books:read. They cover balance, list_my_books and quote_story. A read-only OAuth connection gets a monthly credit cap of 0 automatically. The consent page and Settings hide the cap when stories:write is absent.

Choose scopes in the client's OAuth settings before connecting. Alloglot's consent page currently lists the requested scopes but cannot deselect them. If it shows writing permission or language levels during this read-only test, cancel and narrow the client's request first. A cap of 0 does not remove unnecessary permissions.

After connecting, ask the assistant to call only balance, list_my_books with limit: 1, and quote_story with lang: "es", length: "short", difficulty: 3 and audiobook: false. A quote reports a price without spending it. Do not call create_story or story_status during this test.

Close the web client's tab, reopen it and ask for a fresh balance call. This checks persistence across reopening. It does not prove an expired access token was refreshed. To test revocation, revoke the app in Alloglot Settings → API keys, then request balance once more. Expect a sign-in error or reconnect prompt, not a cached balance. Remove the client installation after the test if you no longer need it.

Claude Desktop and claude.ai

• Open Customize → Connectors. Older clients may call this Settings → Connectors.
• Open Add connector → Add custom connector and name it Alloglot. Paste https://app.alloglot.com/api/mcp as the remote URL, then Continue.
• Choose Sign in now and Register automatically. Alloglot supports dynamic client registration, not Claude's published identity or a preconfigured client secret.
• Choose Add. On the connector's detail page, choose Connect to start OAuth. Adding the configuration alone does not connect the account.
• Sign in to Alloglot. Review the scopes. When writing permission is requested, set the monthly credit cap explicitly before approving. Its default is 200, not 0.
• In a conversation, enable the connector from the connectors menu. Ask “List my Alloglot books.”

The tested Claude.ai flow requested all advertised scopes and offered no scope picker. Changing only the authorization request's scopes to the two read scopes produced a read-only grant with cap 0, but Claude still failed to complete the connection. This is not a verified workaround. The callback reported “Authorization with this connector failed.” A saved app in Alloglot Settings does not prove the client is connected. Do not repeatedly approve new grants to fix this error.

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 Add, 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 and open Advanced OAuth settings. Wait for discovery to finish. Confirm Dynamic Client Registration (DCR). No client ID or secret needs to be pasted.
• For the read-only test, deselect stories:write and levels:read under Default scopes. Leave account:read and books:read selected and Base scopes empty. The default selection includes all four scopes.
• Review the connection warning, select I understand and want to continue, then Create as a plugin. Sign in to Alloglot and approve only the two read permissions. No cap field appears for that read-only grant.
• Open the installed Alloglot plugin and choose Try in chat, or start a new chat and select Alloglot with @. Ask for the three free tool calls above.
• After revoking the grant in Alloglot, the next test call should show Reconnect Alloglot. Choose Not now. To remove the installation, open the plugin's More actions → Uninstall. Uninstalling in ChatGPT is separate from revoking in Alloglot.

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.

Cursor must be installed on the Mac to test this desktop client. A browser alone does not exercise Cursor's MCP runtime. This setup was not verified in the live run below.

{
  "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.

Claude Code also needs access to Anthropic's service. A test sandbox blocking api.anthropic.com prevented setup in the live run below, even before Alloglot OAuth. That does not establish whether the MCP server works in Claude Code.

Verified with

• Verified with ChatGPT web — 2026-10-16, America/Los_Angeles: OAuth with the two read scopes succeeded. balance, list_my_books and quote_story succeeded. A fresh balance succeeded after closing and reopening the tab. After revocation, the next request required reconnection. The grant was revoked and the plugin uninstalled. Expired-token refresh was not observed.
• Verified with Claude.ai web — 2026-10-16, America/Los_Angeles: attempted, not connected. Both OAuth attempts failed at the callback. The narrowed grant's cap of 0 was confirmed through the signed-in settings read endpoint. No tool, refresh or post-revocation tool check completed. Claude Desktop was not tested separately.
• Verified with Cursor — 2026-10-16, America/Los_Angeles: not tested. Cursor was not installed on the test Mac. No connection, tool, refresh or revocation result is claimed.
• Verified with Claude Code 2.1.251 — 2026-10-16, America/Los_Angeles: setup blocked by the test environment's Anthropic network allowlist. No OAuth, tool, refresh or revocation result is claimed.

These lines record outcomes, including failures and untested clients. They are not a certification of every client. No story was created and no credits were spent in this run.

Tools

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.