Skip to main content
Pick the row that matches the tool you use. Every route reaches the same account, the same rules and the same reads and checks. Which changes an agent can make depends on the access level you allow: Read only or Read and change. See Access levels. An agent supplies its own prices. Allocait sends it none. See Prices.

Claude

Pick this if you use Claude on the web, in the desktop app or in Claude Code. You can add the connector, or install the plugin for its ready-made skills.

ChatGPT

Pick this if you use ChatGPT. You sign in to Allocait in your browser, and there is no key to copy.

Codex

Pick this if you use Codex. It uses the same Allocait server and sign-in as ChatGPT.

Cursor

Pick this if you work in Cursor. It connects as an MCP client, with the server URL.

Another MCP client

Pick this if your client speaks streamable HTTP and you want to connect with an API key.

REST API

Pick this if you want to call Allocait from your own script or service.

​
Cursor

Cursor connects as an MCP client. Add a server with this URL, in the place Cursor’s own documentation names for MCP servers:
If Cursor opens Allocait’s sign-in page, sign in with your Allocait account, then choose Read only or Read and change. If it does not, connect with an API key instead. See Other MCP clients.

​
Which route to choose

  • You want an agent to read and check your rules in conversation: connect Claude, ChatGPT or Codex. They sign in with OAuth, so you create no key. Cursor can connect with the server URL or with an API key.
  • You want a scheduled job or a bot: use the REST API or an MCP client with an API key. See Scheduled brief and Check from a script.
  • You haven’t set up rules yet: do that first. The quickstart takes you from holdings to a first check.

​
Next steps

Claude overview

What the connector can and can’t do.

MCP tools

Every MCP tool, grouped by feature.

Check a change

Ask which of your rules a change puts outside range.

Docs for agents

Point an agent at these docs.