# Circle MCP server

> Manage Circle community members, spaces, posts, events, courses and analytics from your AI assistant.

- Listing: https://mcp.tc/i/circle
- Connect: use the server's own URL `https://app.circle.so/api/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Productivity & Projects](https://mcp.tc/c/productivity)
- Vendor: Circle
- Homepage: <https://api.circle.so/mcp>

## About

Connects an AI assistant to a Circle community. It can browse and search members, spaces, posts, events, courses and tags, view analytics, form submissions and live room transcripts, and get summaries of space activity. With full access it can also invite or update members, create posts, manage events and send messages.

Runs as a hosted streamable HTTP endpoint at https://app.circle.so/api/mcp. Users sign in with their Circle account and choose Read only or Full access when connecting. Read only hides all write tools.

## What it can do

- Browse and search members, spaces, posts, events, courses and tags
- View community analytics and form submissions
- Read live room transcripts
- Get summaries of space activity
- Invite, update or remove members (full access)
- Create posts and manage events (full access)
- Choose read only or full access at connection

## Example prompts

- "Show me the spaces in my Circle community."
- "Summarize recent activity in my community's general space."
- "Find members who joined this month."
- "Create a post announcing next week's live event."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http circle https://app.circle.so/api/mcp
```

2. Start Claude Code, type `/mcp`, pick **circle** and choose **Authenticate**. A browser window opens for the Circle sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Circle** and paste this URL:

```url
https://app.circle.so/api/mcp
```

3. Click **Add**, then **Connect**, and sign in when Circle asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Circle&connectorUrl=https%3A%2F%2Fapp.circle.so%2Fapi%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://app.circle.so/api/mcp` and click **Add**.

3. Click **Connect** and sign in when Circle asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://app.circle.so/api/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Circle to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=circle&config=eyJ1cmwiOiJodHRwczovL2FwcC5jaXJjbGUuc28vYXBpL21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "circle": {
      "url": "https://app.circle.so/api/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=circle&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fapp.circle.so%2Fapi%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"circle","type":"http","url":"https://app.circle.so/api/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "circle": {
      "type": "http",
      "url": "https://app.circle.so/api/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "circle": {
      "serverUrl": "https://app.circle.so/api/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add circle --url https://app.circle.so/api/mcp
codex mcp login circle
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.circle]
url = "https://app.circle.so/api/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http circle https://app.circle.so/api/mcp
```

Then, inside Gemini CLI, run `/mcp auth circle` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "circle": {
      "type": "http",
      "url": "https://app.circle.so/api/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://app.circle.so/api/mcp`.

## Details

- Server version: 1.0.0
- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-10-14
- Updated: 2026-10-14

---
Source: https://mcp.tc/i/circle (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
