Agent-Native Calendar MCP server
io.github.BuilderIO · Updated
Agent-Native Google Calendar - manage events, sync, and public booking
At a glance
Agent-Native Calendar is an MCP server in the Dev Tools & Git category. It is hosted remotely and connects over HTTP, and declares no required credentials. It scores A (88/100) on the MCP Skills Hub health score as of Oct 28, 2026.
One-click install
Opens your editor and pre-fills the config. Your editor will ask before adding it.
How to install Agent-Native Calendar in your AI client
Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.
How to install Agent-Native Calendar in Claude CodeAnthropic's agentic CLI
Add the server
bashclaude mcp add --transport http agent-native-calendar https://calendar.agent-native.com/mcpVerify it's connected
bashclaude mcp listSharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes. It discovers them automatically.
How to install Agent-Native Calendar in Claude DesktopDesktop app (MCP config)
Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json
Add this server
json{ "mcpServers": { "agent-native-calendar": { "command": "npx", "args": [ "-y", "mcp-remote", "https://calendar.agent-native.com/mcp" ] } } }Why the wrapper?
This is a remote (HTTP) server and Claude Desktop only launches local processes, so mcp-remote proxies the connection. It will open a browser window if the server needs OAuth.
Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.
How to install Agent-Native Calendar in CursorAI-first code editor
Create / edit .cursor/mcp.json in your project
json{ "mcpServers": { "agent-native-calendar": { "url": "https://calendar.agent-native.com/mcp" } } }Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.
How to install Agent-Native Calendar in Codex CLIOpenAI coding agent
Add to ~/.codex/config.toml
toml[mcp_servers.agent-native-calendar] command = "npx" args = ["-y", "mcp-remote", "https://calendar.agent-native.com/mcp"]Why the wrapper?
Codex runs MCP servers as local processes, so mcp-remote bridges this HTTP endpoint to stdio.
Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.
How to install Agent-Native Calendar in WindsurfCodeium's agentic IDE
Edit ~/.codeium/windsurf/mcp_config.json
json{ "mcpServers": { "agent-native-calendar": { "serverUrl": "https://calendar.agent-native.com/mcp" } } }Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.
How to install Agent-Native Calendar in ClineVS Code autonomous agent
Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.
Add the server
json{ "mcpServers": { "agent-native-calendar": { "type": "streamableHttp", "url": "https://calendar.agent-native.com/mcp" } } }
How to install Agent-Native Calendar in VS CodeCopilot / MCP support
Create .vscode/mcp.json
json{ "servers": { "agent-native-calendar": { "type": "http", "url": "https://calendar.agent-native.com/mcp" } } }Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.
What tools does Agent-Native Calendar expose?
This server requires credentials before it will list its tools, so we cannot enumerate them here. Connect it in your client to see what it offers.
What the code can do
This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.
Before you install
Signals gathered from the source repo and package registry — not a safety verdict.
What it can reach
- Third-party hosted service — Your requests and any data in them are sent to calendar.agent-native.com.
- No local execution — Nothing is installed or run on your machine.
- Last commit today — Actively maintained.
- 7.5k GitHub stars — Community adoption signal.
Client compatibility
Health score
A · 88Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated
- Maintenance30%100%
Last commit 0 days ago.
- Adoption20%100%
7546 stars.
- Transparency20%75%
3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.
- Provenance15%75%
Links to its own repository; package linkage unverified.
- Packaging15%75%
Remote endpoint; authentication requirements not declared.
Documentation
Full READMEAgent-Native
Agent-Native is an open-source TypeScript framework for building agents that pair autonomous work with a purpose-built UI. Define each capability once as an action: the agent uses it as a tool, and the UI calls it from code.
Quick start
npx --yes @agent-native/core@latest create my-agent --standalone --template chatFollow the getting started guide for a full intro to the framework.
Why build agents with UIs?
Coding agents work with more than a text box. Their environment provides context, tools, files, tests, and previews that make their capabilities and results visible.
Knowledge work needs that same kind of environment. A UI shows what an agent can do and gives people familiar ways to inspect, edit, approve, and share its work.
How Agent-Native works
- [Shared actions](https://agent-native.com/docs/actions-overview?utm_source=github&utm_medium=referral&utm_content=readme). The agent calls each capability as a tool, and the UI calls it from code. Both paths use the same validation, permissions, and implementation.
- [Shared data](https://agent-native.com/docs/server-database?utm_source=github&utm_medium=referral&utm_content=readme). Work done by the agent appears in the UI, and work done in the UI is available to the agent.
- [Shared application state](https://agent-native.com/docs/context-awareness?utm_source=github&utm_medium=referral&utm_content=readme). The agent receives relevant UI state, such as the current page, selected record, or active view.
The agent does not click through the UI. It works through the same action layer as the UI.
Example: a shared action
Create actions/hello.ts:
import { defineAction } from "@agent-native/core/action";
import { z } from "zod";
// One action powers every app surface: UI, agent, HTTP, MCP, A2A, and CLI.
export default defineAction({
description: "Return a friendly greeting.",
schema: z.object({
name: z.string().default("world").describe("Name to greet"),
}),
http: { method: "GET" },
run: async ({ name }) => {
return { message: `Hello, ${name}!` };
},
});Excerpt — the full document is on GitHub.
Alternatives to Agent-Native Calendar
- Google Calendar MCPB · 79MCP server for the Google Calendar API: events, recurrence, invitations, availability, calendars.
- ms-calendar-mcpB · 70Microsoft Calendar (Outlook Calendar) MCP server for managing events via Microsoft Graph.
- Agent GuildB · 79See and steer Claude Code, Codex, Antigravity, Grok, Docker Agent and shell sessions in Agent Guild.
- iCloud Calendar (CalDAV)B · 73iCloud Calendar over CalDAV: list, create, update, move and delete events. Optional read-only mode.
Maintain Agent-Native Calendar? Add a badge to your README
Shows its health grade, and links readers to install steps for every client.
[](https://mcp-skills-hub.vercel.app/mcps/io-github-builderio-agent-native-calendar)Catalog data refreshed . Something wrong? Report it.