emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Sempera MCP, stdio or hosted. Phone tools need a plan and owner approval per call.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 20/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Sempera。按照 https://mcp.popnx.com/i/sempera-ai-sempera.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(api.sempera.org) · ✓ 命令已检查 2026年11月19日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Semperahttps://api.sempera.org/v1/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsSempera
用 Sempera 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Sempera,或回答中出现 Sempera 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Semperahttps://api.sempera.org/v1/mcp开启新聊天,输入前先从插件列表中选择 Sempera
用 Sempera 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Sempera,或回答中出现 Sempera 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user sempera https://api.sempera.org/v1/mcp应能看到 Sempera 在列表中并显示已连接
用 Sempera 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Sempera,或回答中出现 Sempera 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Sempera 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Sempera,或回答中出现 Sempera 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Sempera 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Sempera,或回答中出现 Sempera 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://api.sempera.org/v1/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user sempera https://api.sempera.org/v1/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"sempera": {
"url": "https://api.sempera.org/v1/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"sempera": {
"type": "http",
"url": "https://api.sempera.org/v1/mcp"
}
}
}Claude Code
claude mcp add --scope user sempera --env SEMPERA_API_KEY=your-value -- npx -y @sempera/mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"sempera": {
"command": "npx",
"args": [
"-y",
"@sempera/mcp"
],
"env": {
"SEMPERA_API_KEY": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"sempera": {
"command": "npx",
"args": [
"-y",
"@sempera/mcp"
],
"env": {
"SEMPERA_API_KEY": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"sempera": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sempera/mcp"
],
"env": {
"SEMPERA_API_KEY": "your-value"
}
}
}
}SEMPERA_API_KEY 机密 必填 envSEMPERA_MCP_ALLOW_WRITES envSEMPERA_BASE_URL env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 Sempera-AI 验证,该账户拥有此仓库
代码最后更新于5天前
使用 MIT
在 386 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
OSV.dev 中没有 @sempera/mcp@0.1.1 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月19日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/sempera-ai-sempera)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:SEMPERA_API_KEY
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于5天前,最新版本(0.1.1)于今天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Build and fix Discord bots from a chat. Kite hosts them 24/7, with no code to deploy.
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.
CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.
| 本项 Sempera | emailmd | Kite Discord Bot Builder | e2a — email for AI agents | Infobip MCP | kernelCAD | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 5/5 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | AGPL-3.0 | Apache-2.0 | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Documentation | MCP guide | OpenAPI document | MIT licence
@sempera/mcp 0.1.1 is a Model Context Protocol server for the Sempera API. It runs on your machine over stdio and lets an AI assistant (Claude Desktop, Claude Code, Cursor, VS Code and other MCP clients) read your AI phone agents, calls, conversations and numbers, and, only if you turn it on, place a call or send a text.
It calls the public API at https://api.sempera.org (contract: /openapi.json) with your workspace API key. Sempera also hosts an MCP endpoint at https://api.sempera.org/v1/mcp for clients that connect over HTTP; this package is the local, stdio alternative.
Two connections. They do not offer the same tools.
Hosted, for an assistant that speaks streamable HTTP:
https://api.sempera.org/v1/mcp
The endpoint answers one JSON body per POST and does not open an event stream. A host can sign in with OAuth: it registers itself, and PKCE with S256 is required. An OAuth grant can hold only phone:read, phone:call and phone:text. Phone tools need a Sempera Phone plan. Each call needs owner approval unless a standing approval covers that preview. A preview places no call. Read tools and builder tools are not on an OAuth grant. They need a bearer API key whose scopes allow them. The live tool list is what tools/list returns for that credential.
On your machine, over stdio:
npx -y @sempera/mcp
Set SEMPERA_API_KEY, or use a key saved by sempera login. Read tools are always on. send_call and send_sms are off unless you pass --allow-writes. This package does not serve the hosted phone, read or builder tools. Client config for this package is under Configure your MCP client.
Node.js 20 or newer.
# From npm (MCP clients usually run it with npx, below)
npm install -g @sempera/mcp
git clone https://github.com/Sempera-AI/sempera-mcp.git cd sempera-mcp npm install
Create an API key in the Sempera App under Settings, API keys. Give the key only the scopes you want the assistant to have.
Claude Desktop (claude_desktop_config.json), Cursor (.cursor/mcp.json) and most other clients use this shape:
{
"mcpServers": { "sempera": { "command": "npx", "args": ["-y", "@sempera/mcp"], "env": { "SEMPERA_API_KEY": " " } } } }
From a source checkout, use "command": "node" and "args": ["/path/to/sempera-mcp/bin/sempera-mcp.js"].
Claude Code:
claude mcp add sempera --env SEMPERA_API_KEY=<your API key> -- npx -y @sempera/mcp
VS Code (.vscode/mcp.json):
{
"servers": { "sempera": { "type": "stdio", "command": "npx", "args": ["-y", "@sempera/mcp"], "env": { "SEMPERA_API_KEY": " " } } } }
If you have run sempera login with the Sempera CLI on the same machine, you can leave SEMPERA_API_KEY out: the server reads the same saved key (OS keychain, or the 0600 config file).
Read tools are always on. None of them changes anything or contacts anyone.
| Tool | What it returns | API |
|---|---|---|
get_credential | The key's workspace, role and scopes | GET /v1/me |
list_agents | Agents, with status and published version | GET /v1/agents |
get_agent | One agent in full | GET /v1/agents/{agent_id} |
list_calls | One agent's phone calls, newest first | GET /v1/calls |
get_call | One call, with its transcript when there is one | GET /v1/calls/{call_id} |
list_conversations | One agent's conversations on every channel | GET /v1/sessions |
get_conversation | One conversation with its transcript | GET /v1/sessions/{session_id} |
list_phone_numbers | Numbers bound to one agent | GET /v1/phone-numbers |
list_sms_numbers | Numbers that can send texts | GET /v1/sms/numbers |
verify_webhook_signature | Whether an X-Sempera-Signature header matches a body and secret (local, no request) | none |
Write tools are off unless you start the server with --allow-writes (or set SEMPERA_MCP_ALLOW_WRITES=1):
| Tool | What it does | API |
|---|---|---|
send_call | Places one real outbound phone call | POST /v1/calls |
send_sms | Sends one real text message | POST /v1/sms/send |
"args": ["-y", "@sempera/mcp", "--allow-writes"]
The write tools have no defaults. Every call must name the agent, the recipient in E.164 form, a consent sentence saying why the person agreed to be contacted, and an idempotency key (send_sms also needs the sending number and the exact message). Their descriptions tell the assistant to show you the details and wait for your confirmation, and they are marked as non-read-only so MCP clients ask before running them. The API still applies calling and sending hours, the do-not-contact list, opt-outs, caps and billing, and sending needs an owner key with the calls:write scope. Reusing the same idempotency key replays the first answer instead of contacting the person twice.
Answers are the API's JSON. Call and conversation reads can include transcripts and phone numbers, as the key's scopes allow. A refusal comes back as a tool error carrying the API's code, message and request_id.
| Variable | Use |
|---|---|
SEMPERA_API_KEY | The API key; overrides a saved one |
SEMPERA_BASE_URL | Another API base URL |
SEMPERA_MCP_ALLOW_WRITES | 1 to offer send_call and send_sms |
SEMPERA_CONFIG_DIR | Where a key saved by sempera login lives |
SEMPERA_NO_KEYCHAIN | 1 to never use the OS keychain |
npm install
npm test # a real MCP client against the server; the HTTP layer is mocked npx @modelcontextprotocol/inspector node bin/sempera-mcp.js # try it by hand
src/client.js, src/webhooks.js and src/credentials.js are shared with the Sempera CLI and kept identical to it.
This repository is published from Sempera's main source tree; open issues and pull requests here and they are carried back.
server.json lists io.github.Sempera-AI/sempera and pins the npm package version. The matching mcpName in package.json proves the npm package belongs to that listing. npm always includes package.json; the files list selects files, not fields. The packing test checks that the actual tarball keeps this metadata and server.json.
Publish the npm package first. Then, from an account with Actions write access to this repository, run:
gh workflow run publish-mcp-registry.yml --repo Sempera-AI/sempera-mcp --ref main
The workflow is manual only. It installs the official mcp-publisher Linux amd64 release and uses GitHub OIDC to publish the listing. No repository secrets are needed. The workflow does not publish to npm.
MIT. Copyright (c) 2026 Sempera Labs, Inc. See the LICENSE file.