Publishing Your MCP Server

Ready to share your MCP server with the world or your organization? This guide covers everything you need to know about publishing, maintaining, and potentially monetizing your Model Context Protocol servers on Pylee.

Quick Start: Have an MCP server ready? You can publish it in under 5 minutes. Jump to publishing steps

Why Publish on Pylee?

Publishing your MCP server on Pylee’s marketplace unlocks powerful benefits:

For Open Source Developers

Instant Distribution: Reach thousands of AI developers
Community Recognition: Build reputation and get feedback
Zero Infrastructure: Let users connect without hosting costs
Contribution Tracking: See your impact through usage metrics

For Organizations

Internal Distribution: Share tools within your company
Centralized Management: Control versions and access
Security Compliance: Apply consistent governance
Cost Allocation: Track usage by team or project

For Commercial Products

Customer Reach: Access Pylee’s growing user base
Revenue Opportunity: Monetization features coming soon
Reduced Support: Pylee handles configuration and secrets
Marketing Channel: Built-in discovery and recommendations

Strategy Tip: Start with a free public server to build adoption, then create premium private versions with advanced features for enterprise customers.

Public vs Private Publishing

Choosing Your Publishing Strategy

Public Servers
Private Servers

Open to the entire communityBenefits:

Maximum visibility and adoption
Community contributions and feedback
Network effects from widespread use
Potential for monetization (coming soon)

Best for:

Open source projects
Developer tools
API wrappers
Community resources

Examples:

GitHub integration
Popular API connectors
Utility functions

Organization Security Guarantees

When publishing private servers, Pylee ensures: ✅ Complete Isolation: Other organizations cannot see or access your servers
✅ Access Control: Only invited organization members can use them
✅ Audit Trail: Full tracking of who uses what, when
✅ Data Protection: Configuration and secrets stay within your boundary

Step-by-Step Publishing Guide

Step 1: Prepare Your Server

Before publishing, ensure your server:

Follows MCP protocol specifications
Has clear, descriptive tool names
Includes comprehensive error handling
Works with standard MCP clients

Pre-Publishing Checklist:

Server runs without errors
All tools have descriptions
Authentication is properly handled
Documentation is complete
Sensitive data is parameterized (not hardcoded)

Step 2: Create Your Listing

Navigate to Publishing
Pylee Dashboard → Create Server → Marketplace Listing
Basic Information

Server Name: your-server-name  # URL-friendly identifier
Display Name: Your Server Name  # Human-readable name
Description: Clear description of what your server does
Category: Choose the most relevant category
Tags: Add searchable keywords

Choose Connection Type Package-Based (npm, PyPI, Docker):

{
  "type": "package",
  "package_manager": "npm",
  "package_name": "@yourorg/mcp-server",
  "version": "1.0.0"
}

Remote Endpoint (HTTP/SSE):

{
  "type": "remote",
  "url": "https://api.yourserver.com/mcp",
  "transport": "http"
}

Step 3: Configure Parameters

Define what users need to provide:

{
  "configuration": {
    "secrets": {
      "API_KEY": {
        "description": "Your API key from the service",
        "required": true,
        "pattern": "^sk-[a-zA-Z0-9]{48}$"
      }
    },
    "environment": {
      "BASE_URL": {
        "description": "API endpoint URL",
        "default": "https://api.example.com",
        "required": false
      },
      "TIMEOUT": {
        "description": "Request timeout in seconds",
        "type": "number",
        "default": 30
      }
    },
    "options": {
      "ENABLE_CACHE": {
        "description": "Enable response caching",
        "type": "boolean",
        "default": true
      }
    }
  }
}

Security Best Practice: Never hardcode secrets. Always use placeholder fields that prompt users for their own credentials.

Step 4: Add Documentation

Comprehensive documentation ensures successful adoption: Required Documentation Sections

Quick Start Guide

## Quick Start
Install the server from Pylee marketplace
Add your API key when prompted
Connect to Claude/Cursor
Try: "Use the weather tool to check Seattle"

Available Tools

## Tools
- `get_weather(city)` - Get current weather
- `forecast(city, days)` - Get weather forecast
- `alerts(region)` - Get weather alerts

Configuration Guide

## Configuration
Required:
- API_KEY: Get from weather-api.com/keys

Optional:
- UNITS: "metric" or "imperial" (default)
- CACHE_TIME: Cache duration in seconds

Troubleshooting

## Common Issues

### "Invalid API Key"
- Verify key at weather-api.com
- Check for extra spaces
- Ensure key has proper permissions

Step 5: Test Your Listing

Before making it public:

Create a test listing (private to your organization)
Install and configure as a user would
Test all tools with various inputs
Verify documentation accuracy
Check error messages are helpful

Step 6: Publish

Once testing is complete:

Click Publish to Marketplace
Choose visibility (public/private)
Set initial version (recommend 1.0.0)
Add release notes
Submit for publication

Launch Strategy: Consider a soft launch to your organization first, gather feedback, then go public.

Version Management

Semantic Versioning Strategy

Major (1.0.0 → 2.0.0): Breaking changes
Minor (1.0.0 → 1.1.0): New features
Patch (1.0.0 → 1.0.1): Bug fixes

Publishing Updates

## Version 2.1.0

### 🎉 New Features
- Added batch processing support
- New `analyze_sentiment` tool
- Streaming response option

### 🐛 Bug Fixes
- Fixed timeout on large requests
- Improved error messages
- Resolved authentication edge case

### ⚠️ Breaking Changes
- None

Migration Guide

## Migrating from 1.x to 2.0
1. Update configuration:
   - Add `BATCH_SIZE` parameter
   - Remove deprecated `LEGACY_MODE`

2. Update tool usage:
   - `search()` now requires `limit` parameter
   - `process()` returns different schema

Version Rollback

Go to Deployments tab
Select previous stable version
Click Rollback
Users automatically get the stable version

Hosting Options

Comparison Matrix

Option	Setup Complexity	Control	Cost	Scalability	Best For
Self-Hosted	High	Full	You pay	You manage	Large-scale products
Pylee-Hosted	None	Shared	Usage-based	Automatic	Most servers
Package-Based	Low	User’s	Free	N/A	Open source tools
Hybrid	Medium	Mixed	Varies	Flexible	Enterprise solutions

Self-Hosted
Pylee-Hosted
Package-Based

You run the infrastructure

{
  "type": "remote",
  "url": "https://mcp.yourcompany.com",
  "transport": "sse"
}

Pros: Complete control, scaling, debugging
Cons: You handle DevOps, uptime, costs

Monetization (Coming Soon)

Planned models:

Usage-Based Pricing
Subscription Tiers
One-Time Purchase
Revenue Sharing

Early Access: Join our publisher program. Apply here

Best Practices

Technical Excellence
✅ Do: error handling, semantic versioning, input validation
❌ Don’t: hardcode credentials, break backward compatibility Documentation Standards

Start with Why
Include examples
Troubleshooting upfront

Community Engagement

Respond quickly
Share roadmap
Encourage contributions

Launch Checklist

Troubleshooting

Server doesn't appear in marketplace

Verify publication status
Check visibility settings
Wait 5-10 minutes for indexing

Users can't connect to server

Verify server URL
Check authentication config
Review error logs

Version update not reflecting

Clear caches
Verify version incremented
Ensure publication succeeded

Next Steps

Browse the Marketplace

Build Your Server

Security Guide

Platform Teams

Support Resources

Documentation: docs.pyleeai.com
Community Forum
Office Hours: Weekly publishing Q&A
Email: publishers@pyleeai.com
Publisher Program: Early access

Get Started

Platform

Architecture

Developers

Enterprise

Reference

Support

Publish MCP Servers on Pylee Marketplace

Publishing Your MCP Server

Why Publish on Pylee?

For Open Source Developers

For Organizations

For Commercial Products

Public vs Private Publishing

Choosing Your Publishing Strategy

Organization Security Guarantees

Step-by-Step Publishing Guide

Step 1: Prepare Your Server

Step 2: Create Your Listing

Step 3: Configure Parameters

Step 4: Add Documentation

Quick Start Guide

Available Tools

Configuration Guide

Troubleshooting

Step 5: Test Your Listing

Step 6: Publish

Version Management

Hosting Options

Monetization (Coming Soon)

Best Practices

Launch Checklist

Troubleshooting

Next Steps

Browse the Marketplace

Build Your Server

Security Guide

Platform Teams

Support Resources

Get Started

Platform

Architecture

Developers

Enterprise

Reference

Support

​Publishing Your MCP Server

​Why Publish on Pylee?

​For Open Source Developers

​For Organizations

​For Commercial Products

​Public vs Private Publishing

​Choosing Your Publishing Strategy

​Organization Security Guarantees

​Step-by-Step Publishing Guide

​Step 1: Prepare Your Server

​Step 2: Create Your Listing

​Step 3: Configure Parameters

​Step 4: Add Documentation

​Quick Start Guide

​Available Tools

​Configuration Guide

​Troubleshooting

​Step 5: Test Your Listing

​Step 6: Publish

​Version Management

​Hosting Options

​Monetization (Coming Soon)

​Best Practices

​Launch Checklist

​Troubleshooting

​Next Steps

Browse the Marketplace

Build Your Server

Security Guide

Platform Teams

​Support Resources

Publishing Your MCP Server

Why Publish on Pylee?

For Open Source Developers

For Organizations

For Commercial Products

Public vs Private Publishing

Choosing Your Publishing Strategy

Organization Security Guarantees

Step-by-Step Publishing Guide

Step 1: Prepare Your Server

Step 2: Create Your Listing

Step 3: Configure Parameters

Step 4: Add Documentation

Quick Start Guide

Available Tools

Configuration Guide

Troubleshooting

Step 5: Test Your Listing

Step 6: Publish

Version Management

Hosting Options

Monetization (Coming Soon)

Best Practices

Launch Checklist

Troubleshooting

Next Steps

Support Resources