🔌 MCP Server

The tchop MCP Server lets you connect any AI assistant - like Claude, Cursor or Windsurf - directly to your tchop app. Once connected, the assistant can create cards, manage mixes, moderate comments, send push notifications and run analytics queries on your behalf, all in plain language. No code required.

It is the fastest way to bring AI into your editorial and community workflows while keeping full control and your data inside tchop.

What is MCP?

MCP (Model Context Protocol) is an open standard that lets AI assistants call external tools and APIs safely and reliably. Instead of copy-pasting between your AI assistant and tchop, the assistant talks to your app directly.

The tchop MCP server exposes every operation as a named, typed tool. You describe what you want in natural language - for example "create a poll card asking the team where to host the next offsite" - and the assistant calls the right tool with the right parameters.

For developers who prefer to build directly, the same operations are also available as a stable GraphQL API. Both paths share one set of credentials and the same permission model. Full documentation lives in the tchop Developer Portal:

https://api.tchop.live/

What you can do with it

Because the MCP exposes the full tchop operation set, your assistant can:

• Create and update cards of every type (article, poll, image, video, audio and more)

• Publish, schedule, pin or repost content across mixes and channels

• Read, hide, highlight and reply to comments for moderation

• Send push notifications and in-app messages

• Manage tags, mixes and channels

• Query analytics and pull engagement data

Every action respects the same roles and permissions as the app - the assistant can only do what the connected user is allowed to do.

Compatible clients

The tchop MCP works with any MCP-compatible assistant, including:

• Claude.ai and Claude Desktop

• Claude Code

• Cursor

• Windsurf

How to set it up

Setup takes a few minutes and needs no local installation - the server runs remotely at mcp.tchop.live.

1. Get your credentials. Every request needs three values: your org URL (e.g. acme.tchop.io), your auth token, and your API client ID. Request them from our team at support@tchop.io. Treat the auth token like a password - all permissions derive from it.

2. Add the connector in your assistant. Point it at the remote MCP server URL https://mcp.tchop.live and pass your three credentials.

In Claude Desktop: Settings → Connectors → Add custom connector, set the Remote MCP server URL to https://mcp.tchop.live and enter your org URL and auth token, then authorise.

In Claude Code, run once in your terminal:

claude mcp add --transport http tchop https://mcp.tchop.live --header "x-tchop-org-url: acme.tchop.io" --header "x-tchop-auth-token: YOUR_TOKEN" --header "x-tchop-api-client-id: YOUR_CLIENT_ID"

In Cursor or Windsurf, add a tchop entry to your MCP config file with the URL https://mcp.tchop.live and the same three headers.

3. Start working. Ask your assistant to create or manage content in plain language. The full step-by-step guide for each client, plus the complete operation reference, is in the Developer Portal: https://api.tchop.live/.

Good to know

• The MCP Server is currently in Beta; the GraphQL API is stable.

• The server is hosted and always up to date - no reinstalls or version upgrades on your side.

• Keep your auth token private. Never paste it into chats, share it in Slack or include it in screenshots.

Summary

The tchop MCP Server turns your AI assistant into a hands-on editor for your community - creating cards, sending pushes and managing content through natural language, with full control and your data staying in tchop. Connect in minutes and explore everything in the Developer Portal at api.tchop.live.