Skip to main content
Every Zapnito community has its own MCP server. It gives AI assistants access to your community’s users, groups, content, discussions, events and more, through a wide range of tools.
To read and manage community data from your own systems, use the API. To be notified when something happens in your community, use webhooks.

Why use MCP

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external systems. An MCP server describes the tools it offers, and the assistant decides when to call them to answer a question.
  • Answers come from your community, not guesswork. Assistants fetch live records instead of relying on what they were trained on.
  • One integration works across assistants. Any MCP-compatible client can connect to the same server.
  • No custom code. Your team can ask questions in plain language instead of building API calls.

What you can do

Ask your assistant questions about your community, and it chooses the right tools to answer them. For example:
  • “Which discussions mention onboarding in the last month?”
  • “Find the experts in our community who work in data science.”
  • “What events are coming up, and who is hosting them?”
  • “Summarise the documents in our community about carbon capture.”

Connect to your community

Each community has its own MCP server at /mcp on the community’s domain:
MCP server URL
Replace https://your-community.zapnito.com with your community’s domain.
1

Open your LLM provider's connection settings

Open your LLM provider’s custom MCP connection (or plugin) settings.
2

Enter your community's details

Enter your community’s name and the MCP URL.
3

Sign in

Sign in when prompted.
Zapnito’s MCP server supports Dynamic Client Registration (DCR). Your LLM client registers itself as an OAuth client each time a user connects, so you don’t need to create a client ID or paste one in. Most providers detect the connection details from the URL automatically. Each server is connected to one community. To work with more than one community, add a server for each.

How the tools work

The server has 28 tools across 11 resources. Most resources have the same three kinds of tool: A typical request uses two steps. The assistant calls list or search to find the record, then calls get with the record’s id or slug to read it in full. Each list and search tool description names the get tool to follow up with. Metrics are the exception. They return aggregate values, such as total members, instead of records, and list isn’t paginated.

Pagination

list and search tools return 25 results per page. Pass page, starting at 1, to move through the results. All dates and times are in UTC.

Search syntax

Most search tools support these operators in the query: zapnito_search_groups is the exception: it matches any part of a group’s name and doesn’t support these operators.

Tools

The server has tools for users, groups, badges, content, discussions, comments, topics, channels, rooms, events and metrics. See what your assistant can do for example questions and the tools behind them.

What your assistant can do

Example questions and the 28 tools behind them.

Metrics

Answer aggregate questions, such as how many members your community has.