Plug Chronos into any agent.
Chronos ships a full MCP server at https://app.chronos.ro/api/mcp.
Connect Claude, Codex, Cursor, or any MCP client and it can source contacts,
build campaigns, and send across every connected channel - with every
user-visible action gated behind your approval.
Connect your agent
One click mints a personal access token for this account and copies the terminal setup commands - the claude mcp add / codex mcp add commands plus a curl fallback. Run them in your own terminal to connect. They are commands you run yourself, not a message to paste into an agent chat.
Connected agents
Every MCP client that currently holds access to this account.
Set up your client
Prefer to wire it yourself? Pick your client. Replace
YOUR_TOKEN
with a token from Manage access tokens (or use the
one inside the copied setup commands above).
Add the remote server, then run /mcp in your session to load the geo_* tools.
claude mcp add --transport http geodo https://app.chronos.ro/api/mcp \ --header "Authorization: Bearer YOUR_TOKEN"
Codex reads the token from an environment variable, then picks the server up on the next turn.
export GEODO_MCP_TOKEN="YOUR_TOKEN" codex mcp add geodo --url https://app.chronos.ro/api/mcp \ --bearer-token-env-var GEODO_MCP_TOKEN
Settings → Connectors → Add custom connector, or drop this into claude_desktop_config.json.
{
"mcpServers": {
"geodo": {
"url": "https://app.chronos.ro/api/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global).
{
"mcpServers": {
"geodo": {
"url": "https://app.chronos.ro/api/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}
No MCP loader? Hit the server directly - same tools, plain JSON-RPC.
curl -s -X POST https://app.chronos.ro/api/mcp \
-H 'Authorization: Bearer YOUR_TOKEN' \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"geo_get_account_state","arguments":{}}}'
Tool catalog
Everything a connected agent can do. Read-only tools run immediately; asks first tools return a confirmation request and only run after you approve. Signed-in users see the catalog filtered to their connected channels.
Loading the live tool list from /api/mcp…