Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
Scheduling for AI assistants: bookings, availability, meeting polls and routing forms.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.42min.us/mcpRun this in your terminal
claude mcp add --transport http meetings https://api.42min.us/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"meetings": {
"url": "https://api.42min.us/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"meetings": {
"type": "http",
"url": "https://api.42min.us/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://api.42min.us/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified against the domain 42min.us (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Agent-Native Google Calendar - manage events, sync, and public booking
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Public packaging and contracts for 42min, a meeting scheduling platform. This repository holds what you need to build on 42min or connect an AI agent to it. The product itself is closed source.
| REST API | https://api.42min.us/v1 |
| MCP server | https://api.42min.us/mcp |
| Documentation | 42min.us/help/api |
| Status | OAuth 2.1, Dynamic Client Registration, personal access tokens |
plugins/42minThe 42min plugin for Cursor. Connects the editor's agent to your 42min account over OAuth and exposes 43 scheduling tools. See its README.
Any MCP client can connect without this plugin, by pointing at https://api.42min.us/mcp. The server publishes OAuth protected-resource metadata, so a compliant client discovers everything else on its own.
openapi/42min.v1.yamlThe OpenAPI 3.1 description of the public REST API, for generating clients, importing into Postman or Bruno, and feeding to a coding agent.
It is hand-written, and checked against the running API by a contract test suite that exercises every documented endpoint and validates the live response, headers and error bodies against these schemas. That is how the first draft's seven mistakes were found, including two that would have broken every generated client on every booking write. A route-coverage check fails the build if an endpoint exists but is undocumented, or the reverse.
Those checks run in our private repository, because they boot the API against a real database and cannot run here. What CI in *this* repository enforces is that the file is a valid OpenAPI 3.1 document, so a malformed spec never reaches you.
If you find a place where this file and the API disagree, the file is probably wrong: please open an issue.
server.jsonThe official MCP Registry entry. Declares this as a remote server on streamable HTTP at https://api.42min.us/mcp, so registry-backed directories can list it without anyone hand-filling a form.
mcp/tools.jsonThe MCP contract, as a machine-readable snapshot: every tool with its JSON Schema for arguments, the scopes it needs, whether it writes, and the annotations a client uses to decide when to ask you before calling. Generated from the running tool registry, not hand-maintained, and gated by a test that fails when the two disagree.
Read it if you are building a client, or feed it to a coding agent. The table in the plugin README is the human summary of the same thing.
examples/webhook-receiverA working receiver in about 120 lines with no dependencies, and ten tests for verify.js alone. Signature verification is where integrations break: the usual cause is verifying a re-serialized body rather than the raw bytes, which no amount of reading the docs makes obvious. Copy verify.js and move on.
n8n-nodes-42min). Bookings, event types, slots and the current user, plus a trigger for every webhook event with signature verification built in. Runs inside your own n8n, so booking data goes from 42min to your server and nowhere else.Two mechanisms. OAuth 2.1 with PKCE for applications acting on behalf of a user, including Dynamic Client Registration, so a client can register itself without a support ticket. Personal access tokens for scripts acting as one person. Both carry scopes; the API refuses anything a token's scopes do not cover. A token acts as its user: it sees and changes exactly what that member can in 42min, so an app connected by a regular user reaches that user's bookings, and one connected by an admin the whole organization. Discovery documents live at /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource.
Full detail: Authentication.
If-Match, and a concurrent edit fails loudly instead of silently overwriting.Open an issue for API bugs, specification errors, or plugin problems. Security reports go to plus@42min.us, not to the issue tracker: see SECURITY.md.
MIT. See LICENSE.