Search, analyze and manage events on OpenAgenda.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"com-openagenda-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity
MCP Security Weekly
Get CVE alerts and security updates for com.openagenda/mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
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
yarn
yarn prepack
Thanks for contributing! ✨