Document how to publish MCP servers as Actors
维护者通常 1 天内回复
@TC-MO 已经在做这个了。
开始于 2026年5月27日。
评估
这个 Issue 还没有评估数据。
描述
The "build and deploy MCP servers" content currently lives only on the blog (Build and deploy MCP servers in TypeScript). A Slack thread flagged that this should be promoted into docs, broadened in scope, and paired with a starter repo.
Current docs cover MCP almost entirely from the consumer side. Connecting clients to mcp.apify.com, configuring tool selection, OAuth (sources/platform/integrations/ai/mcp/). The publisher side, how to wrap an MCP server as an Actor, monetize it, register it with the Apify MCP server, is a one-liner in develop_ai_agents.md and conceptual prose in the Academy actorization playbook. No step-by-step guide exists.
Scope
A new how-to guide covering:
- Both transports as first-class paths: stdio (wrap existing stdio MCP server) and native remote streamable HTTP (not just proxy mode, which is all the current TS template covers)
- Step-by-step using existing templates: TypeScript MCP server, Python MCP server
- Configure standby mode, pay-per-event monetization, Actor metadata (webServerMcpPath, etc.)
- Explain the re-publishing model: when an MCP server Actor is in the store, its tools are exposed by mcp.apify.com - via explicit registration (?tools=user/actor-name) or dynamic discovery
- Explain the monetization narrative: any Apify user can call paid third-party MCP servers through a single Apify account; Apify handles billing and revenue share to creators
- Deploy via apify push and publish to Apify Store
Companion work
- Cross-links from:
- sources/platform/integrations/ai/mcp/index.md (consumer-side hub)
- sources/platform/actors/development/quick-start/develop_ai_agents.md (templates list)
- sources/academy/build-and-publish/actor-ideas/what_software_an_actor_can_be.md (§ MCP servers and tools for AI)
- sources/academy/build-and-publish/how-to-build/actorization_playbook.mdx (examples table)
Acceptance criteria
- Both TypeScript and Python templates referenced with deploy-ready configs
- Re-publishing via mcp.apify.com documented with a worked example (explicit and dynamic discovery)
- Monetization section explains PPE setup and revenue share for MCP-server Actors
- pnpm run build passes; pnpm run lint clean; all links resolve
- Cross-links added from the four touchpoints above
References
- Blog post: https://blog.apify.com/build-and-deploy-mcp-servers-typescript/
- Monorepo: https://github.com/apify/actor-mcp-servers
- Templates: TS, Py
- Existing consumer-side docs: sources/platform/integrations/ai/mcp/
- 主要语言
- JavaScript
- 星标
- 82
- 派生
- 240
- 平均合并
- 3 天 15 小时
- 30 天内合并 PR
- 41
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
apify/apify-docs 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 85/100
apify/apify-docs#3071 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 85/100
apify/apify-docs#3049 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
apify/apify-docs#2742 ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 82/100
apify/apify-docs#2741 ·
维护者通常 1 天内回复
-
low priority t-unblocking tech enhancement
难度 2/5 1-3 小时 新手友好度 65/100
apify/apify-docs#2451 ·
维护者通常 1 天内回复
相似的 Issue
-
data
难度 1/5 1 小时以内 新手友好度 74/100
gaseous-project/hasheous#637 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
gramps-project/gramps-web#1549 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
-
change request evaluating
难度 2/5 1-3 小时 新手友好度 72/100
sindresorhus/eslint-plugin-unicorn#3907 ·
维护者通常 1 天内回复
-
Priority: Low Production Type: Bug
难度 2/5 1-3 小时 新手友好度 68/100
GrottoCenter/grottocenter-api#1903 ·
维护者通常 1 天内回复