API, MCP and Agent Skill

With MCP and the REST API, an AI agent such as Codex, Claude Code or Cursor can manage your application tracker, read your saved meetings and contexts, and add to your notes. For example: "move the Ozon card to Finals", "show my funnel for the last month", "review my answers from the last interview", "save the review to my notes". An active subscription is required.

1. Create a token

On sobes.tech, open Account → Integrations → API & MCP and click Create token. Set a name, permissions and an expiry; the default is 90 days.

• The token is shown only once: copy it right away.
• Create a separate token for each app. That way you can revoke any of them without touching the others, and revocation takes effect immediately.
• The agent sees only the tools the token has permissions for.
• Only the tracker and meeting permissions are checked by default. An issued token's permissions can't be changed: to give access to notes or contexts, create a new token.
• If your subscription ends, tokens stop working and start working again after renewal.

2. Connect MCP

Pass the token to the client's process in the SOBES_API_TOKEN environment variable. Don't put the token itself in the config file. Then add the configuration and restart the client. The same configurations are shown in the dashboard under Integrations → API & MCP.

Codex: ~/.codex/config.toml

[mcp_servers.sobes]
url = "https://backend.sobes.tech/mcp"
bearer_token_env_var = "SOBES_API_TOKEN"

Claude Code: .mcp.json in the project root

{
  "mcpServers": {
    "sobes": {
      "type": "http",
      "url": "https://backend.sobes.tech/mcp",
      "headers": { "Authorization": "Bearer ${SOBES_API_TOKEN}" }
    }
  }
}

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "sobes": {
      "url": "https://backend.sobes.tech/mcp",
      "headers": { "Authorization": "Bearer ${env:SOBES_API_TOKEN}" }
    }
  }
}

3. Install the skill

The skill explains to the agent how to work with the Sobes tracker and meetings properly: in what order to call tools, how to read long transcripts and how to avoid creating duplicates. One file works for all three clients. Download SKILL.md, save it at the path below and restart the client.

What the agent can do

In the tracker, the agent can do everything you do by hand: read the board, cards, their history, archive and statistics, export statistics to PDF, create and edit cards and columns, import cards in bulk, move cards between stages, attach meetings and set up reminders.

Meetings are read only: the list, summaries and the transcript of all subchats, including messages from before a context reset. The agent can't create or delete meetings or start summary generation. Images, video, model reasoning and tool calls aren't available through the API.

Contexts are read only too. The agent can create and edit notes, but test projects are read only: only "Use in RAG" and the folder can be changed on them.

To avoid overwriting an edit made in the app, the agent can pass the version of the note it read: if the note changed in the meantime, its edit is rejected.

Reading changes nothing: an empty board isn't created on its own and missing summaries aren't generated. To set up a board with the default stages and cards from past meetings with vacancies, the agent has a separate tracker_initialize command.

Deleting a card erases its history and removes it from the funnel statistics; attached meetings are kept. If a card is simply no longer needed on the board, archive it instead.

REST API

MCP and REST are built on the same operations. Full description: OpenAPI.

curl --fail-with-body --silent --show-error \
  -H "Authorization: Bearer $SOBES_API_TOKEN" \
  https://backend.sobes.tech/api/v1/tracker/board

Read tracker

Edit tracker

Read meetings

Notes

Contexts

Errors and limits

In MCP, errors from the tools themselves come back as the result text rather than an HTTP code, for example {"error":"card_not_found"}.

Creating a card, column or note accepts requestId or the Idempotency-Key header. If you repeat the request with the same key within 24 hours, you get the previous result and no duplicate is created.