> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pyleeai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pylee Marketplace - Discover and Use MCP Servers

> Find, connect to, and use Model Context Protocol servers from the Pylee marketplace. Browse public servers and access private organization servers.

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

<Info>
  **Anthropic Registry Included**: Pylee provides full support for all servers from Anthropic's official registry, plus community contributed and private organization servers.
</Info>

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

<Tabs>
  <Tab title="Public 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
  </Tab>

  <Tab title="Private Servers">
    **Restricted to your organization**

    * Only visible to organization members
    * Access controlled by organization admins
    * Proprietary or sensitive integrations
    * Examples: Internal APIs, custom databases, business logic

    Perfect for: Company tools, sensitive data, proprietary systems
  </Tab>
</Tabs>

<Note>
  **Admin Control**: Organization admins can restrict users to only approved public servers, ensuring compliance and security.
</Note>

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

```bash theme={null}
# 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

<Info>
  **Coming Soon**: Native Pylee hosting will let you deploy any server with one click, eliminating infrastructure complexity.
</Info>

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

<Tip>
  **Pro Tip**: Start with local servers for personal use, then move to remote servers when you need team access or production reliability.
</Tip>

## Connecting to Servers

### Quick Connect Options

<CardGroup cols={2}>
  <Card title="Claude Desktop" icon="robot">
    Configure in `claude_desktop_config.json`

    ```json theme={null}
    {
      "mcpServers": {
        "server-name": {
          // Server configuration
        }
      }
    }
    ```
  </Card>

  <Card title="Cursor" icon="code">
    One-click deep link or configure in `.cursor/mcp.json`
  </Card>

  <Card title="VS Code" icon="terminal">
    Extension settings or one-click install
  </Card>

  <Card title="Custom Integration" icon="gear">
    Use MCP SDK to integrate with your tools
  </Card>
</CardGroup>

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

<Steps>
  <Step title="Browse the Marketplace">
    Visit [app.pyleeai.com](https://app.pyleeai.com) to explore available servers
  </Step>

  <Step title="Choose Your Servers">
    Select servers that match your workflow needs
  </Step>

  <Step title="Configure Connection">
    Add required API keys and settings through Pylee's secure interface
  </Step>

  <Step title="Connect Your Tools">
    Use one-click install or manual configuration for your AI tools
  </Step>

  <Step title="Start Using">
    Your AI assistants now have access to new capabilities!
  </Step>
</Steps>

## Common Questions

<Accordion title="Can I use servers without installing anything locally?">
  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.
</Accordion>

<Accordion title="How do I know which servers are safe to use?">
  * **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
</Accordion>

<Accordion title="What if a server I need isn't available?">
  You have several options:

  1. Request it from the community
  2. [Build your own](/mcp-servers/hello-world-tutorial)
  3. [Publish an existing server](/using-pylee/marketplace-publishing) to the marketplace as public or private
  4. Contact the service provider to request MCP support
</Accordion>

## Next Steps

<CardGroup cols={2}>
  <Card title="Publish Your Server" icon="upload" href="/using-pylee/marketplace-publishing">
    Share your MCP server with the community
  </Card>

  <Card title="Create a Registry" icon="folder" href="/understanding-pylee/registry">
    Organize servers for your team
  </Card>

  <Card title="Build Your First Server" icon="hammer" href="/mcp-servers/hello-world-tutorial">
    Create a custom MCP server
  </Card>

  <Card title="Platform Management" icon="building" href="/get-started/platform-teams">
    Set up enterprise governance
  </Card>
</CardGroup>

## Related Resources

* 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