Home Settings and integrations MCP and the public API

MCP and the public API

Last updated on Oct 15, 2026

You can connect Telegrin to your tools in two ways:

  • MCP server - for AI assistants (Claude, ChatGPT, Cursor, Codex): the assistant gets direct access to the feed, campaigns and pipeline, and you get things done right in the chat.
  • Public API - for your own integrations and scripts: about 130 operations over plain REST requests.

The MCP server works through the same public API, so the assistant has the same capabilities.

MCP: connecting in 2 minutes

  1. Open the MCP section in the app menu.
  2. Pick the tab for your client - Claude Code, Claude Desktop, Cursor or Codex - and copy the ready-made snippet with the copy button:
    • Claude Code - one command in the terminal, the server adds itself;
    • Claude Desktop - paste into claude_desktop_config.json (Settings → Developer → Edit Config);
    • Cursor - paste into ~/.cursor/mcp.json and restart Cursor;
    • Codex - add to ~/.codex/config.toml, then run codex mcp login telegrin to sign in.
  3. The server address (already inside the snippets): https://mcp-tg.grinfi.io/mcp.
  4. On first connection a sign-in window opens - log in with your Telegrin account. No separate key is needed for MCP.

Claude in the browser (claude.ai)

In claude.ai, Telegrin is connected as a custom connector: add a connector with the address https://mcp-tg.grinfi.io/mcp and sign in with your Telegrin account. You need this connector, for example, for a Claude routine that handles new leads by itself - step by step in the article "Telegrin → Claude: your Claude routine handles new leads".

What the assistant can do over MCP

  • reads the feed and approves signals right from the chat;
  • manages campaigns - launch, pause, keywords;
  • shows the credit balance and limits;
  • moves leads through pipeline stages;
  • reports monitoring stats and metrics.

Example requests: "show today's new signals and approve the relevant ones", "pause campaign X", "how many credits are left and what were the last ones spent on".

Public API: keys and access

  1. Open Settings → API keys.
  2. Press Create key, fill in the Name and choose the Permissions: Read only or Read and write. Press Create.
  3. Copy the key right away - it is shown only once.
  4. Pass the key in the Authorization: Bearer <key> header.

API address: https://tg.grinfi.io/api/v1/ext. Every operation is described at tg.grinfi.io/api/v1/ext/reference.

⚠️ Important: a key grants programmatic access to the whole workspace, so only an Admin can create and revoke keys. Revoke a compromised key with the Revoke button on the same screen. The list shows when each key was last used.

💡 Tip: if an integration only needs to read data (for example, to export leads into a report), give it a Read only key.

What the API covers

The same groups of operations are available over MCP:

  • Campaigns - list, create, edit, pause and resume, archive, copy, keywords, the campaign's agents and deliverers.
  • Feed and leads - cards, the "lead / not a lead" verdict, conversations, sending a message to a lead, a follow-up draft, the blocklist.
  • Pipeline and tasks - lead stages and reminders about leads.
  • Agents and AI-Brains - list, create and edit.
  • Chat selection - the free chat catalogue and picking new chats, plus message history scans.
  • Delivery - webhooks, CRM connections and Grinfi lists.
  • Analytics - metrics and monitoring stats.
  • Billing - balance, limits and spending. Payments and top-ups happen only in the app.
  • Workspace - team members and the lead email frequency.

Which plans include it

The API and MCP are available on every plan, including the free trial.

Related articles

"Telegrin → Claude: your Claude routine handles new leads" · "Multiple lead delivery channels and their order" · "Agents in a campaign" · "Plan and limits"