Before you start
- An Ankra account with a confirmed email address.
- The agent on your computer: Claude Code, Cursor, Codex, the Claude app, or any client that signs in to a remote MCP server in the browser. On a phone, the choice says Needs your computer: email yourself the step, and the page offers to mail you a link that opens the same step on your computer.
- For Codex, the Ankra CLI. The page installs it for you with Homebrew.
Connect the agent
1
Choose Connect my AI agent
On Where do you want to start? (
/next/onboarding), under Connect my AI agent, press Connect my agent.Check: the heading reads Add Ankra to your agent, with one tab per agent: Claude Code, Cursor, Claude app, Codex, Ankra CLI and Other.2
Add Ankra to the agent
Choose your agent’s tab and do what it shows. The address of Ankra’s MCP server is Check: the page says Waiting for your agent to connect (for Codex, to make its first call), and notices on its own when it does.
https://platform.ankra.app/api/v1/mcp.- Claude Code
- Cursor
- Claude app
- Codex
- Ankra CLI
- Other
Run this in your terminal:
--scope user adds Ankra for every project on this computer. Leave it out to add it only for the folder you are in. Then start Claude Code (restart it if it is open), type /mcp, choose ankra, then Authenticate.3
Approve the sign-in
For Claude Code, Cursor, the Claude app and Other, a browser tab opens on Ankra. It names the agent, lists what it asks for, and has one Authorize button: you cannot narrow the access there. Press Authorize, and the tab hands you back to your agent. For the Ankra CLI, approve the sign-in on the tab that opened. Codex needs no approval: its access came with the connect line.Check: the heading changes to Now tell it what you want, and the page says your agent is connected. Paste this to it and watch it work here.
4
Give it a first job
The page offers a first sentence. Press Copy and paste it into your agent. For example:
- Create a playground on Ankra and tell me when it is ready. It starts a playground: free for 24 hours, no card.
- Show me what is running on Ankra and what needs attention. This one only reads, and is what an agent that may only read is offered.
What the agent can and cannot do
The agent acts as you, inside your role. What it may do is shown under the job: your agent may read and change, as you or may only read, as you.- The Ankra CLI is a second way in. The CLI stays signed in as you, and an agent that runs shell commands can use it, whatever its MCP access says.
ankra logoutends that sign-in and leaves the agent its own token. - Access is never widened in place. To let an agent that may only read change things, end its access and connect it again with more: for Codex, run
ankra mcp connect --client codex --writeagain. For the other agents, end it on API access in your account and sign the agent in again. - A token with a narrower scope.
ankra mcp connect --client claude-code(orcursor,codex) makes a token only the MCP server accepts, read-only unless you add--write, pinned to the project you are acting in and expiring after 90 days. Seeankra mcp connect. - Clusters of your own. An agent that may change things reaches every cluster you can reach. Marking a cluster Production stops Ankra AI from changing it unasked, not your agent.
Where its calls show up
- On the agent page. While the job runs, the page lists each call as it lands. Afterwards, What your agent did, call by call keeps the list.
- In the audit log. Every call, a refused one included, is recorded in your organisation’s audit log as
mcp_tool_call: you, the address it came from, the token and agent it came through, the tool, whether it is a tool that changes things, whether the call worked (with the error when it did not), the cluster it acted on, and the names of the arguments, not their values. What a tool answered is not recorded. The agent’s answers stay in the agent.
Manage or remove it
Under the job, Manage or remove opens API access in your account (/next/account/api), where every agent’s access is listed and can be ended at any time. Add another agent connects a second one. For the Ankra CLI tab the button is How to end it: run ankra logout.
Make your agent better at Ankra
Ankra publishes skills that teach an agent how the platform works: how to ship an app, read a failing deployment, write a Stack. Install them with the Ankra CLI:What can go wrong
When the agent stays silent, the page says No agent has connected yet (for Codex, your agent has not called Ankra yet; for the CLI, The Ankra CLI has not signed in yet) and keeps watching. Open What usually stops it:
Still stuck? Talk to a person on the same page opens support.
Where to go next
MCP Server
Every client, tokens, and how the server handles writes.
MCP Tool Reference
Every tool the agent can call, and the scope it needs.
Service tokens
Give an agent its own identity and a narrower role.
Try a playground
What the playground your agent starts is, and how to keep it.