Search, analyze and manage events on OpenAgenda.
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! ✨
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @openagenda/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"com-openagenda-mcp": {
"command": "npx",
"args": [
"-y",
"@openagenda/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@openagenda/mcpnpmOpenAgenda works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.