{ "canonical_name": "Data-Everything/MCP-Platform", "compilation_id": "pack_69b301676f404f1e9527e68e735ccd98", "created_at": "2026-06-14T03:40:53.234880+00:00", "created_by": "project-pack-compiler", "feedback": { "carrier_selection_notes": [ "viable_asset_types=mcp_config, recipe, host_instruction, eval, preflight", "recommended_asset_types=mcp_config, recipe, host_instruction, eval, preflight" ], "evidence_delta": { "confirmed_claims": [ "identity_anchor_present", "capability_and_host_targets_present", "install_path_declared_or_better" ], "missing_required_fields": [], "must_verify_forwarded": [ "Run or inspect `pip install mcp-platform` in an isolated environment.", "Confirm the project exposes the claimed capability to at least one target host." ], "quickstart_execution_scope": "allowlisted_sandbox_smoke", "sandbox_command": "pip install mcp-platform", "sandbox_container_image": "python:3.12-slim", "sandbox_execution_backend": "docker", "sandbox_planner_decision": "llm_execute_isolated_install", "sandbox_validation_id": "sbx_4904a10888e946759d3808616e3eb165" }, "feedback_event_type": "project_pack_compilation_feedback", "learning_candidate_reasons": [], "template_gaps": [] }, "identity": { "canonical_id": "project_20ba3e0934492c6d83103921d8c01992", "canonical_name": "Data-Everything/MCP-Platform", "homepage_url": null, "license": "unknown", "repo_url": "https://github.com/Data-Everything/MCP-Platform", "slug": "mcp-platform", "source_packet_id": "phit_e0704f0db3bf4f2181f4c2340a9218f1", "source_validation_id": "dval_791b3447a12c4316a0c4fb9d14d86064" }, "merchandising": { "best_for": "需要工具连接与集成能力，并使用 mcp_host的用户", "github_forks": 4, "github_stars": 15, "one_liner_en": "A flexible platform that provides Docker & Kubernetes backends, a lightweight CLI (mcpt), and client utilities for seamless MCP integration. Spin up servers from templates, route requests through a single endpoint with load balancing, and support both deployed (HTTP) and local (stdio) transports — all with sensible defaults and YAML-based configs", "one_liner_zh": "一个灵活的 MCP 平台，提供 Docker 与 Kubernetes 后端、轻量级 CLI（mcpt）以及客户端工具，实现无缝的 MCP 集成。支持通过模板快速启动服务器、借助单一端点进行负载均衡路由，并兼容 HTTP 与 stdio 传输方式，配置基于 YAML，提供合理默认设置。", "primary_category": { "category_id": "tool-integrations", "confidence": "high", "name_en": "Tool Integrations", "name_zh": "工具连接与集成", "reason": "matched_keywords:mcp, integration, github" }, "target_user": "使用 mcp_host 等宿主 AI 的用户", "title_en": "MCP-Platform", "title_zh": "MCP-Platform 能力包", "visible_tags": [ { "label_en": "MCP Tools", "label_zh": "MCP 工具", "source": "repo_evidence_project_characteristics", "tag_id": "product_domain-mcp-tools", "type": "product_domain" }, { "label_en": "Tool Integration", "label_zh": "工具接入扩展", "source": "repo_evidence_project_characteristics", "tag_id": "user_job-tool-integration", "type": "user_job" }, { "label_en": "Project Capability", "label_zh": "项目能力包", "source": "repo_evidence_project_characteristics", "tag_id": "core_capability-project-capability", "type": "core_capability" }, { "label_en": "Verifiable Workflow", "label_zh": "可验证工作流", "source": "repo_evidence_project_characteristics", "tag_id": "workflow_pattern-verifiable-workflow", "type": "workflow_pattern" }, { "label_en": "Local-first", "label_zh": "本地优先", "source": "repo_evidence_project_characteristics", "tag_id": "selection_signal-local-first", "type": "selection_signal" } ] }, "packet_id": "phit_e0704f0db3bf4f2181f4c2340a9218f1", "page_model": { "artifacts": { "artifact_slug": "mcp-platform", "files": [ "PROJECT_PACK.json", "QUICK_START.md", "PROMPT_PREVIEW.md", "HUMAN_MANUAL.md", "AI_CONTEXT_PACK.md", "BOUNDARY_RISK_CARD.md", "PITFALL_LOG.md", "REPO_INSPECTION.json", "REPO_INSPECTION.md", "CAPABILITY_CONTRACT.json", "EVIDENCE_INDEX.json", "CLAIM_GRAPH.json" ], "required_files": [ "PROJECT_PACK.json", "QUICK_START.md", "PROMPT_PREVIEW.md", "HUMAN_MANUAL.md", "AI_CONTEXT_PACK.md", "BOUNDARY_RISK_CARD.md", "PITFALL_LOG.md", "REPO_INSPECTION.json" ] }, "detail": { "capability_source": "Project Hit Packet + DownstreamValidationResult", "commands": [ { "command": "pip install mcp-platform", "label": "Python / pip · 官方安装入口", "source": "https://github.com/Data-Everything/MCP-Platform#readme", "verified": true } ], "display_tags": [ "MCP 工具", "工具接入扩展", "项目能力包", "可验证工作流", "本地优先" ], "eyebrow": "工具连接与集成", "glance": [ { "body": "判断自己是不是目标用户。", "label": "最适合谁", "value": "需要工具连接与集成能力，并使用 mcp_host的用户" }, { "body": "先理解能力边界，再决定是否继续。", "label": "核心价值", "value": "A flexible platform that provides Docker & Kubernetes backends, a lightweight CLI (mcpt), and client utilities for seamless MCP integration. Spin up servers from templates, route requests through a single endpoint with load balancing, and support both deployed (HTTP) and local (stdio) transports — all with sensible defaults and YAML-based configs" }, { "body": "未完成验证前保持审慎。", "label": "继续前", "value": "publish to Doramagic.ai project surfaces" } ], "guardrail_source": "Boundary & Risk Card", "guardrails": [ { "body": "Prompt Preview 只展示流程，不证明项目已安装或运行。", "label": "Check 1", "value": "不要把试用当真实运行" }, { "body": "mcp_host", "label": "Check 2", "value": "确认宿主兼容" }, { "body": "publish to Doramagic.ai project surfaces", "label": "Check 3", "value": "先隔离验证" } ], "mode": "mcp_config, recipe, host_instruction, eval, preflight", "pitfall_log": { "items": [ { "body": "README/documentation is current enough for a first validation pass.", "category": "Capability evidence risk", "evidence": [ "capability.assumptions | https://github.com/Data-Everything/MCP-Platform" ], "severity": "medium", "suggested_check": "Reproduce the official install and quickstart path in an isolated environment.", "title": "Capability evidence risk requires verification", "user_impact": "May increase setup, validation, or first-run risk for the user." }, { "body": "Project evidence flags a maintenance risk. Review the linked source before relying on this workflow.", "category": "Maintenance risk", "evidence": [ "evidence.maintainer_signals | https://github.com/Data-Everything/MCP-Platform" ], "severity": "medium", "suggested_check": "Reproduce the official install and quickstart path in an isolated environment.", "title": "Maintenance risk requires verification", "user_impact": "May increase setup, validation, or first-run risk for the user." }, { "body": "no_demo", "category": "Security or permission risk", "evidence": [ "downstream_validation.risk_items | https://github.com/Data-Everything/MCP-Platform" ], "severity": "medium", "suggested_check": "Reproduce the official install and quickstart path in an isolated environment.", "title": "Security or permission risk requires verification", "user_impact": "May increase setup, validation, or first-run risk for the user." }, { "body": "no_demo", "category": "Security or permission risk", "evidence": [ "risks.scoring_risks | https://github.com/Data-Everything/MCP-Platform" ], "severity": "medium", "suggested_check": "Reproduce the official install and quickstart path in an isolated environment.", "title": "Security or permission risk requires verification", "user_impact": "May increase setup, validation, or first-run risk for the user." }, { "body": "Project evidence flags a security or permission risk. Review the linked source before relying on this workflow.", "category": "Security or permission risk", "evidence": [ "community_evidence:github | https://github.com/Data-Everything/MCP-Platform/issues/27" ], "severity": "medium", "suggested_check": "Reproduce the official install and quickstart path in an isolated environment.", "title": "Security or permission risk requires verification", "user_impact": "May increase setup, validation, or first-run risk for the user." }, { "body": "Project evidence flags a security or permission risk. Review the linked source before relying on this workflow.", "category": "Security or permission risk", "evidence": [ "community_evidence:github | https://github.com/Data-Everything/MCP-Platform/issues/43" ], "severity": "medium", "suggested_check": "Reproduce the official install and quickstart path in an isolated environment.", "title": "Security or permission risk requires verification", "user_impact": "May increase setup, validation, or first-run risk for the user." }, { "body": "Project evidence flags a security or permission risk. Review the linked source before relying on this workflow.", "category": "Security or permission risk", "evidence": [ "community_evidence:github | https://github.com/Data-Everything/MCP-Platform/issues/28" ], "severity": "medium", "suggested_check": "Reproduce the official install and quickstart path in an isolated environment.", "title": "Security or permission risk requires verification", "user_impact": "May increase setup, validation, or first-run risk for the user." }, { "body": "Project evidence flags a security or permission risk. Review the linked source before relying on this workflow.", "category": "Security or permission risk", "evidence": [ "community_evidence:github | https://github.com/Data-Everything/MCP-Platform/issues/20" ], "severity": "medium", "suggested_check": "Reproduce the official install and quickstart path in an isolated environment.", "title": "Security or permission risk requires verification", "user_impact": "May increase setup, validation, or first-run risk for the user." }, { "body": "Project evidence flags a security or permission risk. Review the linked source before relying on this workflow.", "category": "Security or permission risk", "evidence": [ "community_evidence:github | https://github.com/Data-Everything/MCP-Platform/issues/41" ], "severity": "medium", "suggested_check": "Reproduce the official install and quickstart path in an isolated environment.", "title": "Security or permission risk requires verification", "user_impact": "May increase setup, validation, or first-run risk for the user." }, { "body": "Project evidence flags a security or permission risk. Review the linked source before relying on this workflow.", "category": "Security or permission risk", "evidence": [ "community_evidence:github | https://github.com/Data-Everything/MCP-Platform/issues/24" ], "severity": "medium", "suggested_check": "Reproduce the official install and quickstart path in an isolated environment.", "title": "Security or permission risk requires verification", "user_impact": "May increase setup, validation, or first-run risk for the user." }, { "body": "Project evidence flags a security or permission risk. Review the linked source before relying on this workflow.", "category": "Security or permission risk", "evidence": [ "community_evidence:github | https://github.com/Data-Everything/MCP-Platform/issues/33" ], "severity": "medium", "suggested_check": "Reproduce the official install and quickstart path in an isolated environment.", "title": "Security or permission risk requires verification", "user_impact": "May increase setup, validation, or first-run risk for the user." }, { "body": "Project evidence flags a security or permission risk. Review the linked source before relying on this workflow.", "category": "Security or permission risk", "evidence": [ "community_evidence:github | https://github.com/Data-Everything/MCP-Platform/issues/36" ], "severity": "medium", "suggested_check": "Reproduce the official install and quickstart path in an isolated environment.", "title": "Security or permission risk requires verification", "user_impact": "May increase setup, validation, or first-run risk for the user." }, { "body": "issue_or_pr_quality=unknown。", "category": "Maintenance risk", "evidence": [ "evidence.maintainer_signals | https://github.com/Data-Everything/MCP-Platform" ], "severity": "low", "suggested_check": "Reproduce the official install and quickstart path in an isolated environment.", "title": "Maintenance risk requires verification", "user_impact": "May increase setup, validation, or first-run risk for the user." }, { "body": "release_recency=unknown。", "category": "Maintenance risk", "evidence": [ "evidence.maintainer_signals | https://github.com/Data-Everything/MCP-Platform" ], "severity": "low", "suggested_check": "Reproduce the official install and quickstart path in an isolated environment.", "title": "Maintenance risk requires verification", "user_impact": "May increase setup, validation, or first-run risk for the user." } ], "source": "ProjectPitfallLog + ProjectHitPacket + validation + community signals", "summary": "Found 14 structured pitfall item(s), including 0 high/blocking item(s). Top priority: Capability evidence risk - Capability evidence risk requires verification.", "title": "Pitfall Log" }, "snapshot": { "contributors": 3, "forks": 4, "license": "unknown", "note": "站点快照，非实时质量证明；用于开工前背景判断。", "stars": 15 }, "source_url": "https://github.com/Data-Everything/MCP-Platform", "steps": [ { "body": "不安装项目，先体验能力节奏。", "code": "preview", "title": "先试 Prompt" }, { "body": "理解输入、输出、失败模式和边界。", "code": "manual", "title": "读说明书" }, { "body": "把上下文交给宿主 AI 继续工作。", "code": "context", "title": "带给 AI" }, { "body": "进入主力环境前先完成安装入口与风险边界验证。", "code": "verify", "title": "沙箱验证" } ], "subtitle": "A flexible platform that provides Docker & Kubernetes backends, a lightweight CLI (mcpt), and client utilities for seamless MCP integration. Spin up servers from templates, route requests through a single endpoint with load balancing, and support both deployed (HTTP) and local (stdio) transports — all with sensible defaults and YAML-based configs", "title": "MCP-Platform 能力包", "trial_prompt": "# MCP-Platform - Prompt Preview\n\n> Copy the prompt below into your AI host before installing anything.\n> Its purpose is to let you safely feel the project's workflow, not to claim the project has already run.\n\n## Copy this prompt\n\n```text\nYou are using an independent Doramagic capability pack for Data-Everything/MCP-Platform.\n\nProject:\n- Name: MCP-Platform\n- Repository: https://github.com/Data-Everything/MCP-Platform\n- Summary: A flexible platform that provides Docker & Kubernetes backends, a lightweight CLI (mcpt), and client utilities for seamless MCP integration. Spin up servers from templates, route requests through a single endpoint with load balancing, and support both deployed (HTTP) and local (stdio) transports — all with sensible defaults and YAML-based configs\n- Host target: mcp_host\n\nGoal:\nHelp me evaluate this project for the following task without installing it yet: A flexible platform that provides Docker & Kubernetes backends, a lightweight CLI (mcpt), and client utilities for seamless MCP integration. Spin up servers from templates, route requests through a single endpoint with load balancing, and support both deployed (HTTP) and local (stdio) transports — all with sensible defaults and YAML-based configs\n\nBefore taking action:\n1. Restate my task, success standard, and boundary.\n2. Identify whether the next step requires tools, browser access, network access, filesystem access, credentials, package installation, or host configuration.\n3. Use only the Doramagic Project Pack, the upstream repository, and the source-linked evidence listed below.\n4. If a real command, install step, API call, file write, or host integration is required, mark it as \"requires post-install verification\" and ask for approval first.\n5. If evidence is missing, say \"evidence is missing\" instead of filling the gap.\n\nPreviewable capabilities:\n- Capability 1: A flexible platform that provides Docker & Kubernetes backends, a lightweight CLI (mcpt), and client utilities for seamless MCP integration. Spin up servers from templates, route requests through a single endpoint with load balancing, and support both deployed (HTTP) and local (stdio) transports — all with sensible defaults and YAML-based configs\n\nCapabilities that require post-install verification:\n- Capability 1: Use the source-backed project context to guide one small, checkable workflow step.\n\nCore service flow:\n1. page-overview: Platform Overview and System Architecture. Produce one small intermediate artifact and wait for confirmation.\n2. page-builtin-templates: Built-in Server Templates and Usage Guide. Produce one small intermediate artifact and wait for confirmation.\n3. page-custom-templates: Creating Custom Templates and Extensions. Produce one small intermediate artifact and wait for confirmation.\n4. page-deployment-and-client: Deployment Backends, Configuration Flow, and Client API. Produce one small intermediate artifact and wait for confirmation.\n\nSource-backed evidence to keep in mind:\n- https://github.com/Data-Everything/MCP-Platform\n- https://github.com/Data-Everything/MCP-Platform#readme\n- README.md\n- mcp_platform/__init__.py\n- mcp_platform/__main__.py\n- mcp_platform/__version__.py\n- mcp_platform/utils/__init__.py\n- mcp_platform/core/__init__.py\n- mcp_platform/template/templates/__init__.py\n- mcp_platform/template/templates/demo/README.md\n\nFirst response rules:\n1. Start Step 1 only.\n2. Explain the one service action you will perform first.\n3. Ask exactly three questions about my target workflow, success standard, and sandbox boundary.\n4. Stop and wait for my answers.\n\nStep 1 follow-up protocol:\n- After I answer the first three questions, stay in Step 1.\n- Produce six parts only: clarified task, success standard, boundary conditions, two or three options, tradeoffs for each option, and one recommendation.\n- End by asking whether I confirm the recommendation.\n- Do not move to Step 2 until I explicitly confirm.\n\nConversation rules:\n- Advance one step at a time and wait for confirmation after each small artifact.\n- Write outputs as recommendations or planned checks, not as completed execution.\n- Do not claim tests passed, files changed, commands ran, APIs were called, or the project was installed.\n- If the user asks for execution, first provide the sandbox setup, expected output, rollback, and approval checkpoint.\n```\n", "voices": [ { "body": "来源平台：github。github/github_issue: [BUG] Github workflow build-docs failing（https://github.com/Data-Everything/MCP-Platform/issues/43）；github/github_issue: [FEATURE] Snowflake MCP server（https://github.com/Data-Everything/MCP-Platform/issues/24）；github/github_issue: [FEATURE] Replicate postgres template to create new snowflake template（https://github.com/Data-Everything/MCP-Platform/issues/41）；github/github_issue: [FEATURE] Trino database template creation（https://github.com/Data-Everything/MCP-Platform/issues/36）；github/github_issue: [FEATURE] Support for elasticsearch MCP server（https://github.com/Data-Everything/MCP-Platform/issues/33）；github/github_issue: [BUG] Bigquery template docs has wrong information about how to call too（https://github.com/Data-Everything/MCP-Platform/issues/27）；github/github_issue: [BUG] Templates specific documentation inconsistent（https://github.com/Data-Everything/MCP-Platform/issues/28）；github/github_issue: [FEATURE] Bigquery mcp server（https://github.com/Data-Everything/MCP-Platform/issues/20）；github/github_release: Release 1.3.1 - Kubeconfig environment variable config（https://github.com/Data-Everything/MCP-Platform/releases/tag/release-pypi-1.3.1）；github/github_release: Release 1.3.0 - Postgres Template（https://github.com/Data-Everything/MCP-Platform/releases/tag/release-pypi-1.3.0）；github/github_release: Trino Template and many other improvements（https://github.com/Data-Everything/MCP-Platform/releases/tag/release-pypi-1.2.0）；github/github_release: Slack & bigquery template release - 1.1.0（https://github.com/Data-Everything/MCP-Platform/releases/tag/release-pypi-1.1.0）。这些是项目级外部声音，不作为单独质量证明。", "items": [ { "kind": "github_issue", "source": "github", "title": "[BUG] Github workflow build-docs failing", "url": "https://github.com/Data-Everything/MCP-Platform/issues/43" }, { "kind": "github_issue", "source": "github", "title": "[FEATURE] Snowflake MCP server", "url": "https://github.com/Data-Everything/MCP-Platform/issues/24" }, { "kind": "github_issue", "source": "github", "title": "[FEATURE] Replicate postgres template to create new snowflake template", "url": "https://github.com/Data-Everything/MCP-Platform/issues/41" }, { "kind": "github_issue", "source": "github", "title": "[FEATURE] Trino database template creation", "url": "https://github.com/Data-Everything/MCP-Platform/issues/36" }, { "kind": "github_issue", "source": "github", "title": "[FEATURE] Support for elasticsearch MCP server", "url": "https://github.com/Data-Everything/MCP-Platform/issues/33" }, { "kind": "github_issue", "source": "github", "title": "[BUG] Bigquery template docs has wrong information about how to call too", "url": "https://github.com/Data-Everything/MCP-Platform/issues/27" }, { "kind": "github_issue", "source": "github", "title": "[BUG] Templates specific documentation inconsistent", "url": "https://github.com/Data-Everything/MCP-Platform/issues/28" }, { "kind": "github_issue", "source": "github", "title": "[FEATURE] Bigquery mcp server", "url": "https://github.com/Data-Everything/MCP-Platform/issues/20" }, { "kind": "github_release", "source": "github", "title": "Release 1.3.1 - Kubeconfig environment variable config", "url": "https://github.com/Data-Everything/MCP-Platform/releases/tag/release-pypi-1.3.1" }, { "kind": "github_release", "source": "github", "title": "Release 1.3.0 - Postgres Template", "url": "https://github.com/Data-Everything/MCP-Platform/releases/tag/release-pypi-1.3.0" }, { "kind": "github_release", "source": "github", "title": "Trino Template and many other improvements", "url": "https://github.com/Data-Everything/MCP-Platform/releases/tag/release-pypi-1.2.0" }, { "kind": "github_release", "source": "github", "title": "Slack & bigquery template release - 1.1.0", "url": "https://github.com/Data-Everything/MCP-Platform/releases/tag/release-pypi-1.1.0" } ], "status": "已收录 12 条来源", "title": "社区讨论" } ] }, "homepage_card": { "category": "工具连接与集成", "desc": "A flexible platform that provides Docker & Kubernetes backends, a lightweight CLI (mcpt), and client utilities for seamless MCP integration. Spin up servers from templates, route requests through a single endpoint with load balancing, and support both deployed (HTTP) and local (stdio) transports — all with sensible defaults and YAML-based configs", "effort": "安装已验证", "forks": 4, "icon": "link", "name": "MCP-Platform 能力包", "risk": "可发布", "slug": "mcp-platform", "stars": 15, "tags": [ "MCP 工具", "工具接入扩展", "项目能力包", "可验证工作流", "本地优先" ], "thumb": "gray", "type": "MCP 配置" }, "manual": { "markdown": "# https://github.com/Data-Everything/MCP-Platform Project Manual\n\nGenerated at: 2026-06-14 03:28:34 UTC\n\n## Table of Contents\n\n- [Platform Overview and System Architecture](#page-overview)\n- [Built-in Server Templates and Usage Guide](#page-builtin-templates)\n- [Creating Custom Templates and Extensions](#page-custom-templates)\n- [Deployment Backends, Configuration Flow, and Client API](#page-deployment-and-client)\n\n\n\n## Platform Overview and System Architecture\n\n### Related Pages\n\nRelated topics: [Built-in Server Templates and Usage Guide](#page-builtin-templates), [Deployment Backends, Configuration Flow, and Client API](#page-deployment-and-client)\n\n
\nRelated Source Files\n\nThe following source files were used to generate this page:\n\n- [README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/README.md)\n- [mcp_platform/template/utils/__init__.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/utils/__init__.py)\n- [mcp_platform/template/utils/creation.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/utils/creation.py)\n- [mcp_platform/cli/interactive_cli.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/cli/interactive_cli.py)\n- [mcp_platform/template/templates/demo/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/demo/README.md)\n- [mcp_platform/template/templates/github/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/github/README.md)\n- [mcp_platform/template/templates/gitlab/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/gitlab/README.md)\n- [mcp_platform/template/templates/slack/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/slack/README.md)\n- [mcp_platform/template/templates/zendesk/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/zendesk/README.md)\n
\n\n# Platform Overview and System Architecture\n\n## Purpose and Scope\n\nMCP-Platform is a deployment framework for Model Context Protocol (MCP) servers. It packages a curated set of pre-built server templates (databases, developer tools, ticketing, messaging, search) and provides a unified CLI and runtime that turns a single command into a running, containerized MCP endpoint. The platform's stated goal is to let AI developers focus on integration rather than infrastructure, by replacing ad-hoc Docker, transport, and configuration plumbing with a templated, opinionated workflow. Source: [README.md:9-15]()\n\nThe project supersedes the legacy `mcp-templates` package. Existing configurations, Docker images, and deployment workflows remain compatible, but the active development line is the `mcp-platform` distribution installed via `pip install mcp-platform` and operated through the `mcpp` command. Source: [README.md:1-7]()\n\n## High-Level System Architecture\n\nThe platform is organized into three cooperating layers: a **Template Library**, a **Core Engine**, and a **Client/CLI surface**.\n\n```mermaid\nflowchart TB\n User([User / LLM Client]) --> CLI[mcpp CLI / Interactive REPL]\n CLI --> Core[Core Engine\\nCacheManager · ConfigProcessor · ResponseFormatter]\n Core --> Discovery[Template Discovery]\n Discovery --> Library[(Template Library\\ndemo · github · gitlab · slack · zendesk · postgres · bigquery · trino · elasticsearch)]\n Core --> Deployer[Containerized Deployer]\n Deployer --> Docker[(Docker Engine)]\n Docker --> MCPServer[MCP Server Process]\n MCPServer --> Tools[Tool Surface\\nstdio · HTTP · SSE]\n User -.calls tools.-> Tools\n```\n\nThe **Template Library** is the canonical set of directories under `mcp_platform/template/templates/`. Each template is a self-contained package (server code, configuration schema, documentation, and Docker assets) that the platform can list, validate, and deploy. Source: [mcp_platform/template/utils/__init__.py:1-8]()\n\nThe **Core Engine** is a set of utilities for discovering templates, processing configuration, formatting responses, and caching template metadata. The README advertises a 6-hour template cache with automatic invalidation to accelerate repeated operations. Source: [README.md:60-64]()\n\nThe **Client/CLI surface** is what the operator actually invokes. The non-interactive `mcpp` command handles one-shot lifecycle operations (`list`, `deploy`, `logs`, `tools`, `call`), while the interactive REPL — built on Typer — provides tab completion, command history, and session-style tool execution through `MCPClient`. Source: [mcp_platform/cli/interactive_cli.py:7-19]()\n\n## Template System and Lifecycle\n\nA template is more than a script — it is a deployable unit with a structured layout. The reference implementation in `templates/demo/` demonstrates the contract: a `server.py` entry point, a `config.py` schema module, FastMCP-decorated tools, a `requirements.txt`, a Dockerfile, and a docs directory. Source: [mcp_platform/template/templates/demo/README.md:9-14]()\n\nTemplates are discovered dynamically. The `TemplateDiscovery` utility (exported from `mcp_platform.template.utils`) scans the templates directory and surfaces each entry to the CLI. Source: [mcp_platform/template/utils/__init__.py:7-12]()\n\nWhen an operator needs a new integration that does not exist yet, the `TemplateCreator` class scaffolds one. It is an interactive Rich-based prompt flow that asks for an ID, name, and capabilities, then materializes a complete template directory (config, server stub, tests, docs) by adapting a shared `config.py` template. Source: [mcp_platform/template/utils/creation.py:24-44]()\n\nThe platform encourages reuse of upstream MCP implementations rather than rewriting them. Several templates wrap existing open-source MCP servers and surface them through a uniform configuration and deployment layer:\n\n| Template | Wrapped Capability | Configuration Mechanism | Source |\n|----------|-------------------|------------------------|--------|\n| demo | Reference FastMCP server with `say_hello`, `get_server_info`, `echo_message` | `MCP_HELLO_FROM`, `MCP_LOG_LEVEL` env vars | [mcp_platform/template/templates/demo/README.md:53-72]() |\n| github | 77+ GitHub API tools (repos, issues, PRs, actions) | `GITHUB_PERSONAL_ACCESS_TOKEN` | [mcp_platform/template/templates/github/README.md:1-12]() |\n| gitlab | 66+ GitLab tools (repos, MRs, pipelines, wiki, milestones) | `GITLAB_PERSONAL_ACCESS_TOKEN`, optional `GITLAB_READ_ONLY_MODE` | [mcp_platform/template/templates/gitlab/README.md:5-28]() |\n| slack | Channels, DMs, thread reads (XOXP or XOXC/XOXD tokens) | `SLACK_MCP_XOXP_TOKEN` or token pair | [mcp_platform/template/templates/slack/README.md:11-29]() |\n| zendesk | Tickets, users, knowledge base, analytics | Zendesk API credentials | [mcp_platform/template/templates/zendesk/README.md:1-15]() |\n\nCommunity requests have shaped recent additions. The Postgres template shipped in release 1.3.0, the gateway improvements in the same release, and a Snowflake template has been requested to follow the Postgres pattern (issues #24, #41). The Trino template was rewritten in release 1.2.0 and the Elasticsearch template added dual-engine support. Source: [release notes referenced in community context]()\n\n## Configuration, Transports, and Execution\n\nConfiguration is intentionally multi-channel. A single deployment can receive values from JSON files, YAML files, environment variables, CLI `--config key=value` flags, or override parameters. The override path performs type conversion (`\"true\"` → `bool`, `\"123\"` → `int`, JSON-like strings → `list`/`dict`), which is exercised by the demo template's `demonstrate_overrides` helper. Source: [mcp_platform/template/templates/demo/README.md:21-30]()\n\nTransports are abstracted. Templates expose `stdio` (default for many wrapped servers), HTTP (the demo defaults to HTTP on port 7071), and SSE where the upstream server supports it. The interactive CLI routes tool calls through `MCPClient` rather than raw HTTP, ensuring the platform's own error handling and formatting apply uniformly. Source: [mcp_platform/cli/interactive_cli.py:24-31](), [mcp_platform/template/templates/demo/README.md:37-47]()\n\nThe interactive REPL has been deliberately simplified: the prior implicit \"select a template for the session and auto-inject it\" behavior has been removed. Commands now require explicit template arguments and surface clear errors when omitted, trading a small ergonomic shortcut for predictable, scriptable behavior. Source: [mcp_platform/cli/interactive_cli.py:42-47]()\n\n## Known Failure Modes and Community Notes\n\n- **Documentation drift across templates** is a known issue (#28): the `docs/` directory under each template is inconsistent in its usage instructions. New template authors should follow the demo's structure.\n- **Stale tool-calling examples** have appeared in some template READMEs (e.g., BigQuery, #27) showing direct API calls rather than the `mcpp` / `MCPClient` flow. The platform's intended path is always through the client or CLI.\n- **Docs build workflow** has failed on shallow clones due to `setuptools_scm` warnings (#43), which can break the GitHub Actions documentation pipeline if not handled.\n\n## See Also\n\n- Template Creation Utility\n- CLI Reference\n- Configuration Schema and Overrides\n- Demo Template Walkthrough\n- Adding a New Template (Contributor Guide)\n\n---\n\n\n\n## Built-in Server Templates and Usage Guide\n\n### Related Pages\n\nRelated topics: [Creating Custom Templates and Extensions](#page-custom-templates), [Deployment Backends, Configuration Flow, and Client API](#page-deployment-and-client)\n\n
\nRelated Source Files\n\nThe following source files were used to generate this page:\n\n- [mcp_platform/template/templates/demo/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/demo/README.md)\n- [mcp_platform/template/templates/github/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/github/README.md)\n- [mcp_platform/template/templates/gitlab/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/gitlab/README.md)\n- [mcp_platform/template/templates/zendesk/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/zendesk/README.md)\n- [mcp_platform/template/utils/__init__.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/utils/__init__.py)\n- [mcp_platform/template/utils/creation.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/utils/creation.py)\n- [mcp_platform/cli/interactive_cli.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/cli/interactive_cli.py)\n- [README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/README.md)\n
\n\n# Built-in Server Templates and Usage Guide\n\n## Overview and Purpose\n\nThe MCP Platform ships with a curated library of built-in server templates under `mcp_platform/template/templates/`. Each template wraps a real-world service (databases, code hosting platforms, ticketing systems, search engines, demos) into a deployable MCP server with consistent configuration, transport handling, and tool exposure. Templates expose `template.json` metadata alongside a FastMCP-based Python server, enabling one-command deployment via the `mcpp` CLI.\n\nThe platform's core promise is \"zero-configuration deployment of production-ready MCP servers with Docker containers\" (Source: [README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/README.md)), and the template system is the mechanism that delivers it. Discovery, instantiation, and registration of templates are handled by the `TemplateDiscovery` and `TemplateCreator` classes exposed from the package entry point (Source: [mcp_platform/template/utils/__init__.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/utils/__init__.py)).\n\n## Template Architecture\n\nA template follows a modular layout: a `config.py` (typed config + env mapping), a `tools.py` (FastMCP tool definitions), and a `server.py` entrypoint. The `demo` template documents this structure explicitly, noting that the modular design makes each module \"testable, maintainable, extensible, reusable\" (Source: [mcp_platform/template/templates/demo/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/demo/README.md)).\n\n```mermaid\nflowchart LR\n A[mcpp CLI] --> B[TemplateDiscovery]\n B --> C[Template Catalog]\n C --> D[config.py]\n C --> E[tools.py]\n C --> F[server.py]\n D --> G[FastMCP Server]\n E --> G\n F --> G\n G --> H[Docker Container]\n G --> I[stdio Transport]\n G --> J[HTTP/SSE Transport]\n H --> K[MCP Client / LLM]\n I --> K\n J --> K\n```\n\n`TemplateDiscovery` enumerates all templates under the `TEMPLATES_DIR` constant, while `TemplateCreator` generates new templates from a `config.py` base, scaffolding a directory tree complete with a `Dockerfile`, `README.md`, `USAGE.md`, `docs/index.md`, and pytest suite (Source: [mcp_platform/template/utils/creation.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/utils/creation.py)).\n\n## Built-in Template Catalog\n\nThe catalog spans demos, developer platforms, ticketing, search, and databases. The community has been actively extending this list — feature requests exist for Snowflake, Trino, Elasticsearch, BigQuery, and a Postgres-based Snowflake replica, reflecting user demand for broader enterprise data coverage (Source: GitHub issues #24, #33, #36, #41).\n\n| Template | Primary Domain | Notable Capabilities | Source |\n|----------|----------------|----------------------|--------|\n| `demo` | Reference | Greeting tools, override demonstration, FastMCP HTTP-first | [demo/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/demo/README.md) |\n| `github` | Code Hosting | 77 tools covering repos, branches, issues, PRs, Actions, security | [github/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/github/README.md) |\n| `gitlab` | Code Hosting | 66+ tools for repos, issues, MRs, pipelines, wiki, milestones | [gitlab/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/gitlab/README.md) |\n| `zendesk` | Support | Ticket CRUD, user mgmt, knowledge base, analytics, orgs | [zendesk/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/zendesk/README.md) |\n| `postgres`, `trino`, `bigquery`, `elasticsearch` | Databases / Search | Shipped in releases 1.2.0 and 1.3.0 | Release notes in repository |\n\n### Demo Template Usage\n\nThe demo template is the canonical example. It exposes three tools — `say_hello`, `get_server_info`, and `echo_message` — and demonstrates both CLI and override-driven configuration (Source: [mcp_platform/template/templates/demo/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/demo/README.md)). Local usage:\n\n```bash\npip install -r requirements.txt\npython server.py --hello-from \"Custom Server\" --log-level debug\npython server.py --transport stdio\n```\n\nDocker usage binds port `7071` by default and can join the `mcp-platform` network for multi-container deployments.\n\n### GitHub Template Usage\n\nThe GitHub template wraps the official GitHub MCP server and exposes 77 tools grouped into repository, branch, issue, PR, Actions, and security categories. It emphasizes \"dynamic tool discovery, comprehensive monitoring, auto-scaling, configuration management, and security\" (Source: [mcp_platform/template/templates/github/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/github/README.md)). Users authenticate via GitHub tokens passed through the `env` block in their MCP client configuration.\n\n### GitLab Template Usage\n\nThe GitLab template supports `stdio`, SSE, and Streamable HTTP transports, plus a read-only mode (`GITLAB_READ_ONLY_MODE=true`) and feature toggles such as `USE_GITLAB_WIKI`, `USE_MILESTONE`, and `USE_PIPELINE` for granular capability control (Source: [mcp_platform/template/templates/gitlab/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/gitlab/README.md)). Self-hosted GitLab Enterprise requires setting `GITLAB_API_URL` and optionally `HTTP_PROXY`.\n\n## Template Lifecycle and CLI Integration\n\nThe interactive CLI (`mcpp`) provides session-level commands for browsing templates, listing tools, and calling them. It requires readline for command history and tab completion and lazily imports `typer`, `rich`, and `MCPClient` to keep startup fast (Source: [mcp_platform/cli/interactive_cli.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/cli/interactive_cli.py)). Note that the previous \"select template for session\" injection logic has been removed — commands now require an explicit template argument to avoid ambiguity.\n\nCreating a new template from scratch is interactive:\n\n```bash\nmcpp create my-template\n```\n\nThe `TemplateCreator.create_template_interactive` method walks the user through id, name, description, image, capabilities, and config schema, then writes `template.json`, `config.py`, `tools.py`, `server.py`, `Dockerfile`, `README.md`, `USAGE.md`, and `docs/index.md` (Source: [mcp_platform/template/utils/creation.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/utils/creation.py)). It generates a class name like `MyTemplateServerConfig` from the kebab-case id and stamps `metadata`, `env_mapping`, and `required` fields directly from the gathered schema.\n\n## Common Failure Modes and Community Notes\n\nSeveral recurring community pain points surface around templates:\n\n- **Documentation inconsistency** — Per-template `docs/` directories have historically differed in usage instructions (Source: GitHub issue #28). The `TemplateCreator` now generates `docs/index.md` from a shared layout to standardize the contract.\n- **Incorrect tool-call examples** — Older BigQuery docs showed raw HTTP-style calls rather than the `mcpp` client flow; this is addressed by routing all examples through `client.call` (Source: GitHub issue #27, see [mcp_platform/template/templates/demo/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/demo/README.md) for the canonical pattern).\n- **Docs build failures** — The GitHub Actions `build-docs` workflow has been observed failing on shallow clones (Source: GitHub issue #43); this affects CI only and not runtime behavior.\n- **Extending to new data sources** — Community requests consistently follow the same pattern: replicate an existing template's directory layout, map authentication env vars, and add a `template.json` entry (Source: GitHub issues #24, #33, #36, #41).\n\nFor advanced troubleshooting, the demo template documents debug logging via `MCP_LOG_LEVEL=debug`, port conflicts (`python server.py --port 7072`), and Docker network creation (`docker network create mcp-platform`) (Source: [mcp_platform/template/templates/demo/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/demo/README.md)).\n\n## See Also\n\n- [README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/README.md) — Top-level project overview and migration from `mcp-templates`.\n- [mcp_platform/template/utils/creation.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/utils/creation.py) — Reference for authoring new templates.\n- [mcp_platform/cli/interactive_cli.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/cli/interactive_cli.py) — Interactive `mcpp>` shell internals.\n- Release notes for `release-pypi-1.1.0` through `release-pypi-1.3.1` — Per-template changelog.\n\n---\n\n\n\n## Creating Custom Templates and Extensions\n\n### Related Pages\n\nRelated topics: [Built-in Server Templates and Usage Guide](#page-builtin-templates), [Deployment Backends, Configuration Flow, and Client API](#page-deployment-and-client)\n\n
\nRelated Source Files\n\nThe following source files were used to generate this page:\n\n- [mcp_platform/template/utils/__init__.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/utils/__init__.py)\n- [mcp_platform/template/utils/creation.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/utils/creation.py)\n- [mcp_platform/template/utils/discovery.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/utils/discovery.py)\n- [mcp_platform/template/templates/demo/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/demo/README.md)\n- [mcp_platform/template/templates/gitlab/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/gitlab/README.md)\n- [mcp_platform/template/templates/github/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/github/README.md)\n- [mcp_platform/template/templates/zendesk/README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/template/templates/zendesk/README.md)\n- [mcp_platform/client/client.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/client/client.py)\n- [mcp_platform/cli/interactive_cli.py](https://github.com/Data-Everything/MCP-Platform/blob/main/mcp_platform/cli/interactive_cli.py)\n- [README.md](https://github.com/Data-Everything/MCP-Platform/blob/main/README.md)\n
\n\n# Creating Custom Templates and Extensions\n\n## Overview and Scope\n\nMCP-Platform ships a template system that lets developers package an MCP server, its configuration schema, Docker assets, and documentation into a single deployable unit. Once installed (`pip install mcp-platform`), every template becomes addressable through the unified `mcpp` CLI for operations such as `mcpp deploy