Skip to main content
The Tightknit MCP server is currently in pilot. Contact Support if you’d like to join the pilot and turn it on for your community.
The Tightknit MCP server lets AI agents work inside your community on your behalf. It implements the Model Context Protocol, an open standard that connects AI apps to external tools, so an agent like Claude, ChatGPT, or Cursor can read your feeds, post and moderate discussions, run polls, manage members, and more, all through natural language. This is a remote, hosted server: there is nothing to install and no API key to manage. You add one URL to your agent and sign in with your Tightknit account. For a local, terminal-based option that ships inside the Tightknit CLI, see the CLI & MCP Server guide instead.

Let your agent set it up for you

The fastest way to get started is to hand this page to your agent and let it walk you through the setup. Paste the following prompt into Claude, ChatGPT, Cursor, or the agent of your choice:
Copy this into your agent
Your agent will read this guide, add the server to its configuration, and prompt you to sign in. If you’d rather set it up by hand, follow the steps below.

Connection details

Access requires the MCP User role (admins have full access), in a community that’s in the pilot. If you can’t sign in, ask Support to enable the MCP server for your community.
You never paste a token or secret. On first connect, your agent opens a browser window where you sign in, and the communities you can access are scoped to that account automatically.

Connect your agent

Add the server from the terminal:
Then run /mcp inside Claude Code and choose Authenticate to sign in through your browser. Once connected, /mcp lists the Tightknit tools as available.

How access works

The MCP server never holds your password and issues no long-lived key. Your agent completes a standard OAuth 2.1 sign-in, and every request is authorized against your role and permissions in the Studio. A few things follow from this:
  • Role-based — Admins have full access. Everyone else needs the MCP User role, which grants the mcp:access permission to connect. Without it, you can’t reach the server.
  • Tools follow your Studio permissions — Beyond connecting, each tool checks your Studio role and permissions, so an agent only sees the tools your roles allow. For example, pairing MCP User with Events Manager exposes the events tools but not the polls, members, or site tools. Admins can use every tool.
  • Scoped to your communities — The agent only acts on communities where your role has access. If you can reach more than one, ask the agent to run list_tenants first, then reference the community you want by the tenant_id it returns.

Available tools

The server exposes 46 tools. Each tool is annotated so your agent understands the impact of an action before it runs one:
  • Read — Fetches data. Never changes anything.
  • Write — Creates or updates content in your community.
  • Destructive — Deletes content. Cannot be undone.
Agents can create, edit, publish, and delete real content in your community. Review what your agent proposes before you approve write actions, and keep a human in the loop for moderation and member changes.

Communities

Events

Activity

Slack

Polls

Members

Posts and comments

Feeds

Groups

Site

Journeys

Awards

Content library

Troubleshooting

Access requires the MCP User role (or Admin) in a community that is in the pilot. Confirm you’re signing in with the right account, and ask Support to enable the MCP server for your community if it isn’t already.
If you can access more than one community, tools need to know which one to target. Ask the agent to run list_tenants and then reference the community by the tenant_id it returns.
The server uses the Streamable HTTP transport with OAuth. Make sure your client supports remote MCP servers (not only local stdio servers) and that you entered https://mcp.tightknit.ai/mcp exactly, including the /mcp path.

CLI & MCP Server

Run a local MCP server bundled with the Tightknit CLI, authenticated with an API key.

API Keys

Generate keys for direct access to the Tightknit Admin API.