> ## 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 Platform Overview – Secure MCP Hosting and Registries

> The complete platform for MCP: one-click hosting, private registries, version control, audit, and observability. Learn how Pylee enables developers, platform teams, and enterprises to adopt MCP safely at scale.

# Pylee Platform Overview

Pylee is the infrastructure layer that makes MCP production-ready.\
Where MCP defines the open protocol for exposing tools and data, Pylee provides the secure hosting, registries, governance, and observability that enterprises need to operate at scale.

We apply proven infrastructure patterns — organizations, registries, versioning, secrets, and audit — to MCP. Developers focus on building servers. Pylee handles everything else.

***

## Organizations and Teams

Every account in Pylee begins with an **organization**.\
Organizations are the top-level container for:

* **Inviting team members**: manage admins, developers, and users with role-based permissions.
* **Access control**: grant permissions at the org, registry, server, or tool level.
* **Audit and compliance**: track activity across the entire org.

See [Understanding Organizations](/understanding-pylee/organizations) for details.

***

## Secrets and Variables

Secrets and environment variables are managed centrally in Pylee’s encrypted vault.\
Resolution follows a clear **most specific → least specific** order:

* **User level**: personal tokens or local configs.
* **Server level**: one server’s runtime.
* **Registry level**: shared across all servers in a registry.
* **Org level**: defaults shared across the entire organization.

This hierarchy allows centralized defaults with granular overrides where needed.\
No keys in configs, no drift between environments. All reads/writes are audited, and masked values never display in plaintext.

| Scope    | Example                        | Override?                              | Typical Use                          |
| -------- | ------------------------------ | -------------------------------------- | ------------------------------------ |
| User     | `GITHUB_TOKEN (nick)`          | ✅ overrides server/registry/org        | Personal tokens, local testing       |
| Server   | `DB_CONN_STR (customer-svc)`   | ✅ overrides registry/org               | Per service credentials/config       |
| Registry | `OPENAI_MODEL (prod-registry)` | ✅ overrides org                        | Shared server defaults for a project |
| Org      | `SENTRY_DSN (org)`             | ⛔ cannot override user/server/registry | Global defaults/fallbacks            |

See [Secrets](/understanding-pylee/secrets) & [Variables](/understanding-pylee/variables).

***

## Registries

Registries are the unit of governance in Pylee. They are more than a list of servers — they provide:

* Namespaces and versioning rules.
* Role based access controls.
* Approval workflows.
* Shared secrets and configs.

Teams often use multiple registries:

* **Production registry** with pinned, approved versions.
* **Development registry** for experimentation.
* **Team registries** for specialized workflows.

See [Understanding Registries](/understanding-pylee/registries).

***

## Servers and Configurations

An MCP server in Pylee includes its **runtime, configuration, secrets, and versions**.\
When you deploy a server, Pylee:

* Provisions secure endpoints with SSL/TLS.
* Injects secrets at runtime.
* Configures authentication (OAuth 2.1, API key, JWT, SAML/SSO).
* Autos-scales based on load.
* Enables version pinning and rollback.

### Versioning

* Pin exact versions to prevent drift.
* Run canary deployments for new builds.
* Roll back instantly if needed.
* Track config and version history with full audit.

See [Server Configurations and Versions](/understanding-pylee/server-configurations-and-versions).

***

## Observability and Governance

Pylee gives every team visibility and control:

* **Monitoring dashboards**: requests, latency, errors, token usage.
* **Cost management**: attribute spend by team, registry, or server.
* **Approval workflows**: require reviews for deployments, updates, or access.
* **Audit logging**: immutable, exportable logs of every change and invocation.

See [Governance & Approvals](/understanding-pylee/governance).

***

## Developer Experience

Pylee is designed to make MCP servers easy to build, test, and adopt:

* **Local development support**: run and debug with production-like authentication.
* **One-click IDE integration**: deep links for Claude Desktop, Cursor, VS Code.
* **APIs for automation**: publish new server versions, update configs, integrate with CI/CD.

See [Developer Experience](/understanding-pylee/developer-experience).

***

## How the Platform Fits Together

Think of Pylee as the platform layer on top of MCP:

* **MCP Protocol** defines interoperability.
* **Pylee Platform** provides hosting, registries, governance, observability.
* **Clients & Agents** consume MCP servers safely and consistently.

## Layered architecture

```mermaid theme={null}
flowchart TB
    subgraph Sources["Systems & APIs"]
        API1[REST/gRPC API]
        SaaS[SaaS Platform]
        Logic[Custom Logic]
    end

    subgraph MCP["MCP Servers & Registries"]
        S1[MCP Server 1]
        S2[MCP Server 2]
        R[Private Registry]
    end

    subgraph Clients["Clients"]
        IDE[IDE]
        Agent[Agent]
        Job[Automation Job]
    end

    API1 --> S1
    SaaS --> S1
    Logic --> S2
    S1 --> R
    S2 --> R
    R --> IDE
    R --> Agent
    R --> Job
```

***

## Example Journeys

* **Developer** publishes a new server → hosted, versioned, shared via registry.
* **Platform team** imports an external server → reviews, applies RBAC, pins version.
* **Security team** monitors audit logs → enforces approval workflows, manages secrets centrally.

***

## Deployment Options

Pylee fits different operational models:

* **Pylee-hosted**: fastest path to production.
* **Enterprise VPC or on-prem**: for regulated environments with strict compliance.

\[Diagram Placeholder: Deployment options diagram – Pylee Cloud vs Customer VPC/On-Prem, same registry + governance experience]

See [Platform Implementation](/enterprise/platform-implementation).

***

## Next Steps

* Learn [Why Pylee](/get-started/why-pylee) for the strategic case (includes comparison to alternatives).
* Explore [Pylee Marketplace](/platform/pylee-marketplace) to discover servers.
* See [Hosting & Deployment](/developers/hosting-and-deployment-of-mcps) and [Publishing Servers](/developers/publishing-mcp-servers) to get started.
* Review [Understanding Pylee](/understanding-pylee) for detailed guides on organizations, registries, servers, and governance.