Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Document how to publish MCP servers as Actors

Abierto
  • ¿Algo no está bien?
#2,541 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@TC-MO ya está trabajando en esto.

Desde el 27/5/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

documentation t-docs

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

Lenguaje dominante
JavaScript
Estrellas
82
Forks
240
Merge medio
4 d 3 h
PR fusionados (30 d)
40

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apify/apify-docs

Todos los issues de apify/apify-docs

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.