Reads · run at once
- Get ACL Rule
- List ACL Rules
- Get Single Calendar by ID
- Get Color Definitions
- Get Event
- Get Event Instances
- List Events
- List Events from All Calendars
Give Claude Code, Cursor, Codex or your own agent Google Calendar through one MCP URL and one key. Your team signs in to Google Calendar once and the agent never holds a token. Reads run at once; anything that changes Google Calendar waits for your approval.
Actions
A sample of the 47 actions. Your agent sees the full list with tools/list.
Quickstart
Claude Code · Terminal
claude mcp add --transport http vellarin https://hub.vellarin.ai/api/hub/mcp --header "Authorization: Bearer <key>"Cursor · ~/.cursor/mcp.json (or .cursor/mcp.json in a project)
{
"mcpServers": {
"vellarin": {
"url": "https://hub.vellarin.ai/api/hub/mcp",
"headers": {
"Authorization": "Bearer ${env:VELLARIN_HUB_KEY}"
}
}
}
}Codex · ~/.codex/config.toml
[mcp_servers.vellarin]
url = "https://hub.vellarin.ai/api/hub/mcp"
bearer_token_env_var = "VELLARIN_HUB_KEY"Questions
Create a free Vellarin account, connect Google Calendar with its normal sign-in, create an agent key on the Developers page and add the Vellarin Hub MCP server to your client with one line. Your agent then sees the Google Calendar actions as tools.
No. Read actions run at once. Any action that sends, creates, changes or deletes something in Google Calendar waits for the workspace owner's approval and then runs exactly once.
No. The sign-in lives on the server side. Your agent holds only a Vellarin Hub key, which you can scope to Google Calendar alone, cap per day and per month, and revoke at any moment.
Hub Free includes 500 app calls a month and 1 agent key, with no card. Over the cap the answer is "upgrade or wait", never a charge.
Google Calendar is a trademark of its owner. Vellarin Hub is an independent product and is not affiliated with or endorsed by it.