Skip to main content

​
Pylee Marketplace Overview

The Pylee marketplace is your central hub for discovering and using Model Context Protocol (MCP) servers. Whether you’re looking for pre-built solutions or organization specific tools, the marketplace makes it easy to find, configure, and connect to the servers you need.
Anthropic Registry Included: Pylee provides full support for all servers from Anthropic’s official registry, plus community contributed and private organization servers.

​
What is the Marketplace?

The Pylee marketplace is a curated collection of MCP servers that you can:
  • Discover through search and categories
  • Configure with your own API keys and settings
  • Connect to your AI applications & tools (Claude, Cursor, VS Code)
  • Manage through registries for team coordination
Think of it as an app store for AI capabilities - each server adds new tools and integrations your AI agents can use.

​
Finding Servers

​
Search and Filter

  • Search by name, functionality, or description
  • Filter by connection type (local/remote)
  • View only public or private servers in your organization
  • Sort by popularity, recent updates, or alphabetically

​
Server Access Levels

  • Public Servers
  • Private Servers
Available to everyone in the Pylee community
  • Appear in public search results
  • Can be used by any Pylee user
  • Often open source or freemium
  • Examples: GitHub, Slack, popular APIs
Perfect for: General-purpose tools, open source projects, community resources
Admin Control: Organization admins can restrict users to only approved public servers, ensuring compliance and security.

​
Using Servers from the Marketplace

Once you’ve found a server, you have three ways to use it:

​
1. Direct Connection

Connect individual servers directly to your AI tools: 
# One-click install for supported apps
cursor://install/server-name
vscode://install/server-name

​
2. Self-Hosted Remote Access

Convert package-based servers to remote endpoints:
  • Pylee hosts the server for you
  • Access it remotely from any tool
  • No local installation required
  • Perfect for team sharing

​
3. Registry Collection

Add servers to registries for organized management:
  • Group related servers together
  • Share configuration across teams
  • Version control at the registry level
  • Apply consistent security policies
Coming Soon: Native Pylee hosting will let you deploy any server with one click, eliminating infrastructure complexity.

​
Understanding Server Types

​
Local Servers (stdio)

How they work: Run on your local machine via packages (npm, PyPI, Docker)
Best for: File system access, local development, personal tools Configuration options:
  • Runtime arguments
  • Environment variables
  • Package settings
  • Secrets management
Example use cases:
  • File system operations
  • Local database connections
  • Development tools

​
Remote Servers (HTTP/SSE)

How they work: Connect to servers running at specified URLs
Best for: Shared services, production APIs, team resources Configuration options:
  • Header values
  • Authentication tokens
  • API endpoints
  • Secrets injection
Example use cases:
  • Cloud APIs
  • Shared databases
  • Production services
Pro Tip: Start with local servers for personal use, then move to remote servers when you need team access or production reliability.

​
Connecting to Servers

​
Quick Connect Options

Claude Desktop

Configure in claude_desktop_config.json
{
  "mcpServers": {
    "server-name": {
      // Server configuration
    }
  }
}

Cursor

One-click deep link or configure in .cursor/mcp.json

VS Code

Extension settings or one-click install

Custom Integration

Use MCP SDK to integrate with your tools

​
Configuration Management

Pylee handles the complex parts of server configuration:
  • Secrets Vault: Encrypted storage for API keys
  • Environment Variables: Managed at org/registry/server levels
  • Version Pinning: Lock to specific versions for stability
  • Auto-Updates: Optional automatic updates for latest features

​
Working with Registries

Registries are collections of servers that work together. Why Use Registries?
  • Simplified Management: Configure once, use everywhere
  • Team Coordination: Ensure everyone uses the same versions
  • Shared Configuration: Inherit secrets and settings
  • Access Control: Manage permissions at registry level
Registry Types
  • Personal Registry: Your individual server collection
  • Team Registry: Shared within your department
  • Organization Registry: Company-wide approved servers
  • Public Registry: Community-curated collections
Learn more: Registry Management Guide

​
Getting Started

1

Browse the Marketplace

Visit app.pyleeai.com to explore available servers
2

Choose Your Servers

Select servers that match your workflow needs
3

Configure Connection

Add required API keys and settings through Pylee’s secure interface
4

Connect Your Tools

Use one-click install or manual configuration for your AI tools
5

Start Using

Your AI assistants now have access to new capabilities!

​
Common Questions

Yes! Pylee can host package-based servers remotely, so you can access them without local installation. This is perfect for team sharing or when you don’t want to manage local dependencies.
  • Public servers are reviewed by the community
  • Verified badges indicate official or trusted sources
  • Usage metrics show how many people use the server
  • Source code links let you audit the implementation
  • Organization servers are managed by your IT team
You have several options:
  1. Request it from the community
  2. Build your own
  3. Publish an existing server to the marketplace as public or private
  4. Contact the service provider to request MCP support

​
Next Steps

Publish Your Server

Share your MCP server with the community

Create a Registry

Organize servers for your team

Build Your First Server

Create a custom MCP server

Platform Management

Set up enterprise governance
  • Publishing Guide - Share your servers on the marketplace
  • Security Best Practices - Secure server configuration
  • MCP vs API - Understanding the differences
  • Platform Teams Guide - Enterprise MCP management