English Français العربية

OpenAgenda

Official registry Search and web

Search, analyze and manage events on OpenAgenda.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http openagenda 'https://mcp.openagenda.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "openagenda": {
            "type": "http",
            "url": "https://mcp.openagenda.com/mcp"
        }
    }
}
NPM package @openagenda/mcp
Claude Code 
claude mcp add openagenda -e 'OA_API_KEY=<your oa_api_key>' -e 'OA_BASE_URL=<OA_BASE_URL>' -e 'OA_EXECUTOR=<OA_EXECUTOR>' -e 'OA_LOCAL_NO_SANDBOX=<OA_LOCAL_NO_SANDBOX>' -- npx -y @openagenda/mcp@1.5.4
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "openagenda": {
            "command": "npx",
            "args": [
                "-y",
                "@openagenda/mcp@1.5.4"
            ],
            "env": {
                "OA_API_KEY": "<your oa_api_key>",
                "OA_BASE_URL": "<OA_BASE_URL>",
                "OA_EXECUTOR": "<OA_EXECUTOR>",
                "OA_LOCAL_NO_SANDBOX": "<OA_LOCAL_NO_SANDBOX>"
            }
        }
    }
}

Environment variables

  • OA_API_KEY required secret OpenAgenda API key (the stdio credential — a least-privilege/read key is advised). The hosted remote uses OAuth instead.
  • OA_BASE_URL v3 API base URL (defaults to https://api.openagenda.com/v3).
  • OA_EXECUTOR Code engine: node (default — Node's permission sandbox: no filesystem/subprocess; network NOT bounded) or deno (adds a scoped network egress boundary; recommended hardening, needs deno installed).
  • OA_LOCAL_NO_SANDBOX Disable the Node permission sandbox entirely (bare node, NO boundary at all) — trusted/dev use only.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

OpenAgenda Monorepo – public subtree

Welcome to the public portion of the OpenAgenda (oa) monorepo.
Here you’ll find all the open-source packages we publish on npm along with their documentation.

⚠️ Contributor notice (Yarn v4)

This project uses Yarn v4 / Berry, which stores its workspace lockfile as yarn.lock-workspace.
To avoid dependency conflicts and keep the Git history clean, always rename the lockfile:

# Before you start working
mv yarn.lock-workspace yarn.lock

# …do your usual work: yarn install, yarn prepack, tests, etc.

# Just before committing / pushing
mv yarn.lock yarn.lock-workspace

Quick start

yarn
yarn prepack

Thanks for contributing! ✨

Frequently asked questions

What is OpenAgenda?

Search, analyze and manage events on OpenAgenda.

How do I install OpenAgenda?

It runs as a remote server. In Claude Code: claude mcp add --transport http openagenda 'https://mcp.openagenda.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does OpenAgenda need an API key?

Yes. It expects OA_API_KEY, which you set in its configuration.

Is OpenAgenda open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains OpenAgenda?

It is published by OpenAgenda. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.