​

Publishing Your MCP Server

​

Why Publish on Pylee?

​

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

​

Public vs Private Publishing

​

Choosing Your Publishing Strategy

​

Organization Security Guarantees

​

Step-by-Step Publishing Guide

​

Step 1: Prepare Your Server

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

​

Step 2: Create Your Listing

1. Navigate to Publishing
   Pylee Dashboard → Create Server → Marketplace Listing
2. 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

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

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

​

Step 3: Configure Parameters

{
  "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
      }
    }
  }
}

​

Step 4: Add Documentation

​

Quick Start Guide

## Quick Start
1. Install the server from Pylee marketplace
2. Add your API key when prompted
3. Connect to Claude/Cursor
4. 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

• 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

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

​

Version Management

• 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

## 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

## 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

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

​

Hosting Options

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

​

Monetization (Coming Soon)

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

​

Best Practices

• Start with Why
• Include examples
• Troubleshooting upfront

• Respond quickly
• Share roadmap
• Encourage contributions

​

Launch Checklist

​

Troubleshooting

​

Next Steps

​

Support Resources

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