OpenAgenda
com.openagendaPublished by openagenda.comOfficial publisherv1.6.0Updated Nov 4, 2026
Search, analyze and manage events on OpenAgenda.
Overview
OpenAgenda MCP server that lets an assistant search, analyze and manage events on the OpenAgenda platform, hosted remotely or run locally via npx.
- What you can do
- Search and analyze events on OpenAgenda
- Manage event records on the platform
- Run through a hosted remote endpoint with OAuth, or locally over stdio with an API key
- Choose the local code engine (node or deno) and its sandbox level
- When to use it
- Use it when you work with OpenAgenda event data and want an assistant to look up, analyze or manage events without leaving the conversation. The hosted endpoint suits quick setup; the local package suits users who prefer an API key and their own runtime.
- Requirements
- Either the hosted remote endpoint at mcp.openagenda.com with OAuth, or the npm package @openagenda/mcp run with npx (Node.js). The local mode needs an OpenAgenda API key in OA_API_KEY; OA_BASE_URL, OA_EXECUTOR and OA_LOCAL_NO_SANDBOX are optional settings. Network access to the OpenAgenda API.
Installation
In SourceWeft
- Open OpenAgenda in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.openagenda%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"openagenda": {
"type": "http",
"url": "https://mcp.openagenda.com/mcp"
}
}
}README
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:
Quick start
Thanks for contributing! ✨
Source: README.md at commit 6486095
Tools
0Version history
7- v1.6.0LatestNov 4, 2026
- v1.5.4Oct 22, 2026
- v1.5.2Oct 8, 2026
- v1.5.1Oct 1, 2026
- v1.5.0Sep 26, 2026
- v1.4.0Sep 17, 2026
- v1.3.2Sep 16, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.
