Skip to main content

​
ankra mcp

Connect a coding agent to the Ankra MCP server. ‘ankra mcp connect’ is the guided setup. To manage the external MCP servers your organisation’s agent runs may call, see ‘ankra org mcp-servers’.

​
ankra mcp connect

Register the Ankra MCP server with Claude Code, Cursor or Codex. This creates a personal API token that only the MCP server accepts, read-only unless you pass --write, pinned to the project you are acting in (--project chooses another) and expiring in 90 days. Running connect again replaces it and revokes the old one, which is also how to renew it. The token is never printed. It is stored in ~/.ankra/mcp/<client>.json, readable only by you, and is not written into the agent’s config:
  • Claude Code gets a headers helper, so it fetches the token when it needs it.
  • Cursor and Codex read ANKRA_MCP_TOKEN, so add this to your shell profile: export ANKRA_MCP_TOKEN=”$(ankra mcp token --client cursor)”
Reads are the place to start; give an agent --write when you want it to act, for example to open a fix pull request. Writes still ask for confirmation.
Examples
Flags

​
ankra mcp token

Print the token ‘ankra mcp connect’ stored for a client, for use in export ANKRA_MCP_TOKEN=”$(ankra mcp token --client cursor)”. It refuses to print to a terminal, so the token stays out of your scrollback.
Flags