Template Marketplace
1. Overview
Purpose: Facilitate collaboration and reuse by publishing community‑ or organization‑contributed MCP templates.
Key Features:
Browse and search curated template catalog
Preview template details and dependencies
Install or import templates into your project
Versioning and update notifications
Rating, reviews, and usage metrics
2. Template Structure
Each template consists of:
Manifest Metadata (
manifest.json): Name, version, description, author, tags.Nodes:
Resource Nodes (data sources, APIs)
Prompt Nodes (prebuilt prompt sequences)
Tool Nodes (CLI, scripts)
Sampling Nodes (LLM integration)
Connector Edges (data flow definitions)
Configuration Files: Environment variables, credential stubs.
Documentation: Usage guide and examples.
3. Browsing & Discovery
3.1 Catalog View
Grid/List of available templates with thumbnails and metadata tags.
Filters: Category, tags, popularity, recent updates.
Sorting: Alphabetical, most installed, highest rated.
3.2 Template Details
When selecting a template, users see:
Full description and screenshot
Author and version history
Node diagram preview
Required dependencies and permissions
Installation instructions
Ratings & Reviews
4. Installing Templates
Click "Install" on the desired template.
Select target workspace or create a new project.
Configure variables (e.g., API keys, URIs) via a guided form.
Import nodes into the Manifest Studio canvas.
Review & confirm the imported workflow.
Once installed, the template appears in your local Templates panel for reuse.
5. Publishing Your Templates
Define manifest metadata including tags and categories.
Package nodes & docs into a versioned template bundle.
Run validation to ensure compatibility.
Publish to the marketplace: public or private scope.
Receive feedback: track installs, ratings, and issue reports.
6. Versioning & Updates
Templates follow semantic versioning.
Update Notifications appear when newer versions are released.
Users can diff changes and upgrade safely.
7. Community & Governance
Review Process: Templates undergo automated CI checks and community review before public listing.
Contribution Guidelines: Best practices for naming, documentation, and testing.
Support Channels: Discussion forums and issue trackers.
8. Best Practices
Tag templates accurately for discoverability.
Provide clear examples and minimal configurable parameters.
Include stub data for quick prototyping.
Keep nodes modular and reusable.
Next Steps: Try browsing the Template Marketplace or contribute your own MCP templates today!
Last updated