42min

MCP开发工具

提供方 42min

开发工具 HTTP · 远程 OAuth 授权 社区 / 第三方 ClaudeCursorVS CodeWindsurf
查看接入方式

官方 42min MCP 服务器:让 Claude、ChatGPT、Cursor 或任何 MCP 客户端管理你的会议日程。查询空闲时间、查找可用时段,预约、取消和改期会议,管理周期性会议系列、私密预约

一句话选型结论

按资料字段整理

42min 属于开发工具类 MCP 服务器,HTTP · 远程,OAuth 授权,可直接接入 Claude、Cursor、VS Code 等,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式HTTP · 远程 鉴权OAuth 授权 部署方式支持远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

scheduling calendar meetings booking appointments availability outlook zoom

支持客户端

适用场景

schedulingcalendarmeetings

安装与配置

HTTP · 远程 OAuth 授权
连远程 HTTPS 端点,通常为 Streamable HTTP
https://api.42min.us/mcp

把它填进客户端的 MCP 配置即可,不需要在本地安装运行时。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
42min当前 未标注 HTTP · 远程 支持远程部署 有 2026-11-20
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方42min上游标注的维护方 42min
分类开发工具本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型支持远程部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

4.7 KB
来自项目仓库与上游目录的原文,未做删改

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 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 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 plus@42min.us, not to the
issue tracker: see SECURITY.md.

License

MIT. See LICENSE.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
42min 怎么安装?

在客户端按下面的安装命令接入:https://api.42min.us/mcp。装完在客户端配置里引用同一个包或端点。

42min 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式是HTTP · 远程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

42min 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

42min 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

42min 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Windsurf、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

42min 能提供哪些能力?

资料显示能力标签包括 scheduling、calendar、meetings、booking、appointments、availability。具体工具清单以官方文档为准。

42min 需要什么运行环境?

运行时为 Cross-platform;属于远程端点,不需要在本地装运行时。

42min 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。