42min MCP server
Commit Oct 20, 2026Lets an AI client manage scheduling tasks including bookings, availability, meeting polls, and routing forms.
Also known as 42min-us/42min-developers, 42min-developers
- Stars
- 2
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.0
- Last commit
- Oct 20, 2026
- License
- MIT
What is 42min MCP?
42min lets an AI client manage scheduling tasks including bookings, availability, meeting polls, and routing forms.
Summary generated from the project's README
About 42min MCP server
Managing meeting schedules, availability, and booking forms through an AI agent is what this remote MCP server enables. Developers can connect an AI client to the 42min platform to automate scheduling tasks using 43 specific tools. The server operates over streamable HTTP and uses OAuth 2.1 with PKCE for applications acting on behalf of users, or personal access tokens for individual scripts.
Users can integrate this directly into the Cursor editor via a dedicated plugin or connect any compliant MCP client by pointing to the remote endpoint. The system supports dynamic client registration and uses scoped permissions to ensure an agent only accesses the bookings and organizational data allowed by the authenticated user. Because the server interacts with a live production environment, all write operations create real calendar events and send actual emails.
What you can do with it
- 1Integrate with Cursor editorDevelopers can connect their coding environment to their scheduling account using the 42min plugin.
- 2Build custom automation scriptsYou can use personal access tokens to allow scripts to perform scheduling actions as a specific user.
- 3Connect to any MCP clientAny standard MCP client can discover and use the scheduling tools by connecting to the remote endpoint.
Written from the project's README. Every use case is checked against a quote from it.
How to install 42min MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall 42min MCP in Claude Code
$ claude mcp add --transport http 42min-developers https://api.42min.us/mcpInstall 42min MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"42min-developers": {
"url": "https://api.42min.us/mcp"
}
}
}Install 42min MCP in VS Code
.vscode/mcp.json
{
"servers": {
"42min-developers": {
"type": "http",
"url": "https://api.42min.us/mcp"
}
}
}Install 42min MCP in VS Code CLI
$ code --add-mcp '{"name":"42min-developers","type":"http","url":"https://api.42min.us/mcp"}'Install 42min MCP in Codex
$ codex mcp add 42min-developers --url https://api.42min.us/mcpInstall 42min MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.42min-developers] url = "https://api.42min.us/mcp"
Install 42min MCP in Gemini CLI
$ gemini mcp add -s user --transport http 42min-developers https://api.42min.us/mcpInstall 42min MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"42min-developers": {
"url": "https://api.42min.us/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachable42min-us/42min-developers is public and reachablegithub.com/42min-us/42min-developers ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-20github.com/42min-us/42min-developers ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHub42min developers
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 |
What is here
plugins/42min
The 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.yaml
The 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.json
The 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.json
The 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-receiver
A 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.
Built on this API
- n8n community node (
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.
Authentication in one paragraph
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.
Things worth knowing before you build
- Mutating booking calls accept
Idempotency-Key. Retry with the same key. A new key creates a second booking. A key belongs to the user behind the token and to one endpoint. PATCH /v1/bookings/{uid}uses ETags. Read the ETag, send it back asIf-Match, and a concurrent edit fails loudly instead of silently overwriting.- There is no test environment yet. Write operations act on production: they send real email and create real calendar events. Test on event types you own, and clean up after yourself. (Our help pages use "sandbox" for something else, the per-credential isolation of webhook subscriptions.)
- Ignore unknown response fields. We add fields without notice; see CHANGELOG.md for the full versioning policy and the six-month deprecation guarantee.
Support
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.
License
MIT. See LICENSE.
42min MCP questions
How do I add 42min MCP to Claude Code?
Run claude mcp add --transport http 42min-developers https://api.42min.us/mcp in your terminal. Add --scope user to make it available in every project.
How do I add 42min MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What authentication methods are supported?
The platform supports OAuth 2.1 with PKCE for user-acting applications and personal access tokens for individual scripts.
Is there a sandbox or test environment available?
No, there is currently no test environment; all write operations act on production and send real emails and calendar events.