Skip to content
あ·atode Documentation
Main site Open atode

Documentation Advanced

Advanced CLI setup

This page is for command-line tools and other technical MCP clients that do not support atode's browser sign-in. If your app opens a browser when you add atode, use the simpler app connection guides instead.

Connection details

Your client needs these values:

Server URL: https://mcp.atode.dev/mcp
Transport: Streamable HTTP
Authorization header: Bearer atk_your_key_here

Create an API key

  1. In atode, open Settings, then API Keys.
  2. Create a key with a name that identifies the app or device.
  3. Copy the key immediately. It is shown only once and begins with atk_.

Treat the key like a password. Do not put it in a public repository, paste it into a chat, or share it with another person. Revoke it from atode if it may have been exposed.

Add the server from a CLI

Every client uses different commands. When its MCP command accepts an HTTP server and custom headers, provide the server URL above and this header:

Authorization: Bearer atk_your_key_here

For example, a Claude Code installation that supports HTTP headers can use:

claude mcp add --transport http atode \
  https://mcp.atode.dev/mcp \
  --header "Authorization: Bearer atk_your_key_here"

Check the command against your client's current documentation before running it. Prefer a secret store or environment-variable feature if the client offers one, so the key is not saved in shell history.

Add the server in a configuration file

Some clients use a JSON settings file. A common shape is:

{
  "mcpServers": {
    "atode": {
      "type": "http",
      "url": "https://mcp.atode.dev/mcp",
      "headers": {
        "Authorization": "Bearer atk_your_key_here"
      }
    }
  }
}

This is a pattern, not a universal file format. Use the filename, property names, and secret-handling method documented by your client. Restart the client after changing its configuration if it does not reload automatically.

Test and remove the connection

Ask the client to list the available atode tools, then ask it to show your recent lessons. If authorization fails, confirm that the key is active and the header begins with Bearer.

To remove access, delete the server from the client and revoke its key in atode. Create a separate key for each client so one can be revoked without affecting the others.

Last verified: 2026-07-29 — MCP authorization specification