Home Settings and integrations MCP and the public API

MCP and the public API

Last updated on Sep 03, 2026

There are two ways to connect Telegrin to your tools:

  • MCP server - for AI assistants (Claude, ChatGPT, Cursor): the assistant gets direct access to your feed, campaigns and pipeline, so tasks get done right in the chat.
  • Public API - for your own integrations and scripts: the same capabilities over REST requests.

The MCP server mirrors the public API one to one: everything the API can do (around 90 operations) is available to the assistant through MCP as well.

MCP: connect in 2 minutes

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

What the assistant can do through MCP

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

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

Public API: keys and access

  1. Open Settings → API keys.
  2. Click "Create key" and give it a name.
  3. Copy the key immediately - it is shown only once.
  4. Pass the key in the Authorization: Bearer <key> header.

⚠️ Important: a key gives programmatic access to the entire workspace, so only the workspace admin can create and revoke keys. Revoke a compromised key on the same screen - it takes effect instantly.

What the API covers

Groups of operations (the same ones are available through MCP):

  • Campaigns - list, create, edit, start/pause, campaign deliverers.
  • Signals and leads - the feed, approve/reject, lead cards, pipeline stages.
  • Agents - the list of agents and templates.
  • AI cores - reading and updating cores.
  • Tracked posts - connecting and archiving posts.
  • Analytics - dashboard metrics, the monitoring funnel.
  • Billing - credit balance and limits (no payments - purchases happen in the app only).
  • Blocklist - adding and removing entries.
  • Webhooks - managing delivery endpoints (details in the article "Webhook delivery of leads to your CRM").
  • History scanning, workspace, chat search - utility operations.

Which plans include it

API and MCP are available on every plan - during the trial and on the paid plans (Starter, Growth and Scale). Keys are created by the workspace admin in Settings → API keys.

Related articles

"Webhook delivery of leads to your CRM" · "Multiple lead delivery channels and their order" · "Plan and limits"