OpenAgenda MCP Server

Search, analyze and manage events on OpenAgenda.

Local + remotestreamable-httpstdio

What is the OpenAgenda MCP Server?

OpenAgenda is an MCP integration. Search, analyze and manage events on OpenAgenda.

Hosted connection

The registry lists a streamable-http connection at https://mcp.openagenda.com/mcp.

Packages and local setup

The published npm package is @openagenda/mcp, version 1.5.2. Its declared MCP transport is stdio.

The package declares OA_API_KEY (required): 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.5.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
OA_API_KEYOpenAgenda API key (the stdio credential — a least-privilege/read key is advised). The hosted remote uses OAuth instead.Yes
OA_BASE_URLv3 API base URL (defaults to https://api.openagenda.com/v3).Check documentation
OA_EXECUTORCode 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).Check documentation
OA_LOCAL_NO_SANDBOXDisable the Node permission sandbox entirely (bare node, NO boundary at all) — trusted/dev use only.Check documentation