Is this an official Circle MCP server?

No. It is Memtro's MCP server with Memtro's Circle connector behind it: the connector reads Circle through its API with the credentials you connect on Dashboard → Connections, and Circle publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Circle?

Only when you ask, and only what it has been granted: create a post in a space (draft, published or scheduled; notifies members only when asked); edit a post's title, text, topics, pin or comment settings; delete a post; comment on a post or reply to a comment (no notifications unless asked); delete a comment and its replies (permanent); send a chat message to a member, a group of members or a chat room; create a virtual or to-be-decided event in an event space (draft or published); invite a member to an event (emails them if the event is published); invite a person to the community by email (no invitation email unless asked); add a person to a space by email; apply a member tag to a member; deactivate a member (cancels their running paywall subscriptions). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Social and reputation

Circle MCP server

Circle in any MCP client, through Memtro: Circle does not publish this server. Memtro's Circle connector reads Circle through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Circle community: spaces, posts with their text, comments, members by name, events with their times and places, and member tags; can create, edit or delete posts, comment or delete comments, send chat messages, create events and invite to them, invite, deactivate or tag members, and add members to spaces.

Reads

circle_spacesSpaces in the Circle community: id, name, type (posts, events, chat, course, members), private, hidden or draft, and URL.
circle_postsPosts in the community, newest first by default: title, space, author's name, published and updated times, comment and like counts and URL…
circle_commentsComments, newest first, on a post or across a space or the community: the commenter's name, the post, time, text cut short, reply and like counts.
circle_membersCommunity members by name only (never email or profile fields).
circle_eventsPublished events: name, start and end, in person or virtual, the venue, host, space and URL.
circle_member_tagsThe community's member tags: id (what circle_tag_member and circle_invite_member take), name, whether it shows on profiles…

Acts, when you ask

These change something in Circle. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

circle_create_postCreates a post in a Circle space (a posts-type space, from circle_spaces).
circle_update_postEdits a Circle post: its title, its text (replaced whole, and only on posts written in Circle's current editor), its topics (replaced)…
circle_delete_postDeletes a Circle post from its space (Circle soft-deletes it; the API offers no restore) and unpins it.
circle_create_commentComments on a Circle post, or replies to a top-level comment with parent_comment_id.
circle_delete_commentPermanently deletes a Circle comment and every reply to it.
circle_send_messageSends a Circle chat message from the token's admin: a direct message to one member (to_email), a group chat with several (to_emails)…
circle_create_eventCreates an event in a Circle event space (from circle_spaces).
circle_invite_event_attendeeInvites a community member (by email) to a Circle event and adds them to its space if needed.
circle_invite_memberAdds a person to the Circle community by email, creating a Circle account if they have none, and gives them access to the community…
circle_add_space_memberAdds a person to a Circle space by email, giving them access to it.
circle_tag_memberApplies a member tag (from circle_member_tags) to a community member, by email.
circle_deactivate_memberRemoves a member from the Circle community (deactivates their membership): they lose access at once…

Connect it

First connect Circle on Dashboard → Connections, then add Memtro to your client once. The Circle tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Circle connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› What were people posting about in the community this week?
› Which posts in the Announcements space got the most comments?
› What did people say in the comments on the pricing update post?
› What events do we have next month, and are they in person?
› Create the March meetup as a draft event with this Zoom link

Questions

Is this an official Circle MCP server?: No. It is Memtro's MCP server with Memtro's Circle connector behind it: the connector reads Circle through its API with the credentials you connect on Dashboard → Connections, and Circle publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Circle?: Only when you ask, and only what it has been granted: create a post in a space (draft, published or scheduled; notifies members only when asked); edit a post's title, text, topics, pin or comment settings; delete a post; comment on a post or reply to a comment (no notifications unless asked); delete a comment and its replies (permanent); send a chat message to a member, a group of members or a chat room; create a virtual or to-be-decided event in an event space (draft or published); invite a member to an event (emails them if the event is published); invite a person to the community by email (no invitation email unless asked); add a person to a space by email; apply a member tag to a member; deactivate a member (cancels their running paywall subscriptions). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.