# OpenAgenda MCP server

> Search, analyze and manage events on OpenAgenda by running sandboxed code against the v3 API.

- Listing: https://mcp.tc/i/openagenda
- Connect: use the server's own URL `https://mcp.openagenda.com/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: OpenAgenda
- Homepage: <https://mcp.openagenda.com>
- Repository: <https://github.com/OpenAgenda/oa-public>
- Package: npm `@openagenda/mcp`

## About

Connects an assistant to the OpenAgenda v3 API using a code-mode pattern. Instead of one tool per endpoint, it offers two tools: one to search the API documentation for the right operation, and one to run JavaScript against the API. This covers reading agendas, events and locations, and writing events and media.

The hosted endpoint uses Streamable HTTP and needs an OpenAgenda account: the first connection opens a browser consent screen. A local option runs with npx -y @openagenda/mcp over stdio and needs an OpenAgenda API key in OA\_API\_KEY. Code runs in a sandbox with per-caller rate limits.

## What it can do

- Search OpenAgenda API documentation for the right operation
- Run sandboxed code against the OpenAgenda v3 API
- Read agendas, events and locations
- Create and update events
- Upload media for events
- Analyze event data across agendas

## Example prompts

- "Find upcoming events in my OpenAgenda agenda this month"
- "Create a new event in my agenda for next Friday at 7pm"
- "Count events per location in my agenda over the last year"
- "Which OpenAgenda API operation lists events for an agenda?"

## Install

### Claude Code

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

```bash
claude mcp add --transport http openagenda https://mcp.openagenda.com/mcp
```

2. Start Claude Code, type `/mcp`, pick **openagenda** and choose **Authenticate**. A browser window opens for the OpenAgenda 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 **OpenAgenda** and paste this URL:

```url
https://mcp.openagenda.com/mcp
```

3. Click **Add**, then **Connect**, and sign in when OpenAgenda 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=OpenAgenda&connectorUrl=https%3A%2F%2Fmcp.openagenda.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.openagenda.com/mcp` and click **Add**.

3. Click **Connect** and sign in when OpenAgenda 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://mcp.openagenda.com/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to OpenAgenda 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=openagenda&config=eyJ1cmwiOiJodHRwczovL21jcC5vcGVuYWdlbmRhLmNvbS9tY3AifQ%3D%3D>) (opens Cursor)

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

`mcp.json`:

```json
{
  "mcpServers": {
    "openagenda": {
      "url": "https://mcp.openagenda.com/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=openagenda&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.openagenda.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"openagenda","type":"http","url":"https://mcp.openagenda.com/mcp"}'
```

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

`.vscode/mcp.json`:

```json
{
  "servers": {
    "openagenda": {
      "type": "http",
      "url": "https://mcp.openagenda.com/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": {
    "openagenda": {
      "serverUrl": "https://mcp.openagenda.com/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 openagenda --url https://mcp.openagenda.com/mcp
codex mcp login openagenda
```

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

`config.toml`:

```toml
[mcp_servers.openagenda]
url = "https://mcp.openagenda.com/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http openagenda https://mcp.openagenda.com/mcp
```

Then, inside Gemini CLI, run `/mcp auth openagenda` 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": {
    "openagenda": {
      "type": "http",
      "url": "https://mcp.openagenda.com/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://mcp.openagenda.com/mcp`.

## Details

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

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