42min

us.42minPublished by 42min.usOfficial publisherv0.1.0Updated Oct 24, 2026

Scheduling for AI assistants: bookings, availability, meeting polls and routing forms.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

42min is a remote MCP server that lets an AI assistant manage meeting scheduling: bookings, availability, meeting polls and routing forms.

What you can do
  • Manage bookings: create, read and update bookings, with idempotency keys for safe retries and ETags for concurrent edits.
  • Work with event types and availability slots to find and offer times.
  • Run meeting polls and routing forms for coordinating groups.
  • Look up the current user and account context behind the connected token.
  • Expose 43 scheduling tools in total, with per-tool scopes and write annotations published as a machine-readable contract.
When to use it
Useful when you want an assistant to schedule meetings on your behalf inside 42min: proposing times, creating or changing bookings, and coordinating attendees through polls and routing forms, without leaving the chat.
Requirements
A remote MCP endpoint at api.42min.us/mcp over streamable HTTP; no local package. A 42min account and OAuth 2.1 with PKCE (Dynamic Client Registration supported) or a personal access token. Tokens carry scopes, and the API refuses calls outside them.
Before you install
There is no test environment: write operations act on production, sending real email and creating real calendar events. A token acts as its user, so an admin-connected app reaches the whole organization. Retrying a booking with a new idempotency key creates a duplicate booking. Booking updates rely on ETags to avoid silent overwrites.

Installation

In SourceWeft

  1. Open 42min in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/us.42min%2Fmeetings/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "42min": {
      "type": "http",
      "url": "https://api.42min.us/mcp"
    }
  }
}

README

42min 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 APIhttps://api.42min.us/v1
MCP serverhttps://api.42min.us/mcp
Documentation42min.us/help/api
StatusOAuth 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 as If-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 [email protected], not to the issue tracker: see SECURITY.md.

License

MIT. See LICENSE.

Source: README.md at commit d002220

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts