API
Integrate Crosslybot with your systems
Two integration paths. Webhooks for servers and no-code platforms. MCP for AI agents like Claude Desktop and Cursor.
Webhooks DEV
HTTP API for integrations
Accept posts from your services and publish to Telegram, VK, Max via a single HTTP request. Bearer auth + optional HMAC. Discovery endpoint exposes the structure automatically.
- •Use for: servers, n8n, Zapier, cron scripts, mobile apps
- •Targeted publishing to specific channels
- •Idempotency-key for safe retries
- •Deferred project/target pause after publish
MCP NEW
For AI agents and LLMs
Connect Crosslybot to Claude Desktop, Cursor, Cline or any MCP client. The AI agent publishes posts to your channels in response to natural-language prompts.
- •Use for: Claude Desktop, Cursor, Cline, Continue
- •Hosted — no local install required
- •Natural language commands ("publish to marketing channel…")
- •Fuzzy target resolution by name substring
When to use which
Both options use the same backend — pick based on your scenario.
Scenario
Server integration (backend, script, no-code)
Pick
Webhooks
Why
Stable HTTP API, idempotency, direct control of requests
Scenario
AI agent drives publishing
Pick
MCP
Why
LLM figures out where to publish via discovery + fuzzy resolve
Scenario
Scheduled cron job
Pick
Webhooks
Why
Script decides what and where — deterministic flow
Scenario
AI chat: "publish this to channel X"
Pick
MCP
Why
AI understands context and forms the payload without copying IDs
Get started in five minutes
Open the bot, create a project and get a token — both APIs are available immediately.
