独立运营 · 不出售排名位置  · 我们怎么评估工具 →
Anclum 提交收录
O

Onplana/onplana-mcp-server

Official MCP server and TypeScript client for Onplana — connect Claude, ChatGPT, Cursor, and any…

装之前:没有可直接复制的命令 · 许可证 MIT · 链接可访问

第一步:npm install github:Onplana/onplana-mcp-server @modelcontextprotocol/sdk express

在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
远端端点(Claude Desktop / Cursor / Windsurf 共用 mcpServers)
{
  "mcpServers": {
    "onplana-onplana-mcp-server": {
      "url": "https://mcp.onplana.com/mcp"
    }
  }
}
把这段粘进 Claude Desktop / Cursor 的 mcpServers 配置即可。端点来自公开证据,我们没有替你安装或托管它。 官方 Registry 记录:这个端点列了请求头 Authorization(OAuth 2.1 access token (DCR supported at https://app.onplana.com/oauth/register, RFC 7591) or a Personal Access Token from https://app.onpla),但没有标为必填。能不能匿名连上,以项目文档为准。
VS Code(.vscode/mcp.json —— 键名是 servers,远程要 type: http)
{
  "servers": {
    "onplana-onplana-mcp-server": {
      "type": "http",
      "url": "https://mcp.onplana.com/mcp"
    }
  }
}
VS Code 的配置文件和另外三家不同:顶层键是 <code>servers</code>,远程端点还要写 <code>"type": "http"</code>。复制到 .vscode/mcp.json。
Claude Code(命令行)
claude mcp add --transport http onplana-onplana-mcp-server https://mcp.onplana.com/mcp
Claude Code 不收 JSON 文件,用这条命令直接加。
取自该仓库的安装命令
npm install github

解析自我们于 2026-11-08 抓取的该仓库 README;我们未执行过。

这条是仓库自己写的安装方式,不是 MCP 客户端配置,所以不生成 JSON。
配置项的键名以你的客户端为准:客户端与 CLI
★ 数取值
5 ★ · Onplana/onplana-mcp-server · 取自 GitHub 搜索 API · (2026-11-13 20:00:50 核对)
来源明细
从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
收录与活跃
收录于 2026-11-09 · 最近见到 2026-11-14 · 共见到 6 次 · 被 1 个来源列出
评分构成
综合分 103 · 5 ★ · 1 个来源 · repo
安装
npm install github
常见问题(答案都来自我们的记录)
怎么安装?
该仓库给出的安装命令是 npm install github。我们的记录里它是仓库自己提供的;不保证在你的客户端上直接可用。
它适合谁 / 用来做什么?
我们把它归在这些标签下: 开源项目。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库 Onplana/onplana-mcp-server;我们收录于 2026-11-09;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。

# Onplana MCP server

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

Open-source TypeScript Model Context Protocol building blocks,
extracted from Onplana's production MCP
deployment. Two packages:
onplana-mcp-server: server
template. Streamable HTTP transport, Bearer auth, prompt-injection
containment, pluggable dispatcher.
onplana-mcp-client: typed TypeScript
client SDK for calling the public Onplana MCP endpoint at
https://api.onplana.com/api/mcp/v1.
## What this is
The transport layer of an MCP server (Streamable HTTP wiring,
stateless mode, scoped Bearer auth, prompt-injection containment)
done well, separated from the platform-specific tool registry. Use
the server template to build your own MCP server with security
best practices baked in. Use the client SDK to drive Onplana's
hosted MCP from your own code.
The patterns are extracted from Onplana's production deployment
(public docs at onplana.com/mcp), the
same layer that handles real Claude Desktop, Cursor, ChatGPT custom
connector, and in-house agent traffic against the Onplana platform.
## Why open-source
The MCP transport is the same for everyone. Most early MCP servers
get the security primitives wrong:
Prompt injection. Tools that return user-generated content
(task titles, comment bodies, wiki text) put that content directly
into the model's context. Without containment, a hostile actor can
plant "ignore previous instructions" in their own data and the
next agent that reads it follows along.
Stateless transport. Most SDK examples assume in-memory session
state, which breaks horizontal scaling and complicates the auth
model.
Plan-gate semantics. Surfacing tools the caller can't actually
invoke wastes turns and confuses the model.
Onplana solved these in production over six months of MCP-server
work. Publishing the patterns is high-leverage:
1. Other MCP authors get a known-good template instead of
reinventing.
2. The repo is a pretraining-signal surface. Public GitHub READMEs
are heavily weighted in next-gen LLM training data, and a repo
with patterns + clear documentation about MCP improves model
recall of "what good MCP servers look like."
3. The dispatcher interface is the seam where your business logic
plugs in. The transport is generic; what matters about your MCP
server is the tool registry. Open-sourcing the transport doesn't
give away anything proprietary.
The dispatcher implementation, tool catalog, plan-gate logic, audit
infrastructure, and the rest of Onplana's ~600 LOC closed-source
dispatcher stay in the closed monorepo because they encode platform
business logic. If you build your own MCP server using this
template, you write your own dispatcher. That's the work that
matters and the work that's specific to your platform.
## Repository layout
onplana-mcp-server/
├── packages/
│ ├── server-template/ # onplana-mcp-server (npm)
│ │ ├── src/
│ │ │ ├── transport.ts # Streamable HTTP wiring
│ │ │ ├── auth.ts # Bearer auth pattern
│ │ │ ├── promptInjection.ts # wrapUserContent + escape
│ │ │ ├── dispatcher.ts # Pluggable Dispatcher interface
│ │ │ └── index.ts
│ │ ├── tests/ # promptInjection + auth + transport
│ │ └── README.md
│ └── client/ # onplana-mcp-client (npm)
│ ├── src/
│ │ ├── client.ts # OnplanaMcpClient class
│ │ ├── types.ts # Public type surface
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/zh/s/onplana-onplana-mcp-server/)
来源
github · https://github.com/Onplana/onplana-mcp-server
按领域浏览
开源项目
Traction
5 ★
收录于
今天

同类推荐

全部 1,671 →

所属领域与标签

每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。

浏览全部领域 →

← 返回索引