PlexMCP-OSS

PlexMCP is an MCP gateway platform that orchestrates MCP servers with enterprise-grade features like authentication, multi-tenant isolation, and audit logging. The OSS release focuses on providing a self-hosted gateway you can run locally or in your own infrastructure, backed by a Rust backend, a Next.js frontend dashboard, and a PostgreSQL database. You can deploy the entire stack using Docker, then access the web dashboard to manage MCP servers, API keys, and tenants. The system handles routing, connection pooling, and audit trails for your MCP clients and servers, making it suitable for multi-user environments and usage-based scenarios.

Once the stack is running, you can use the included dashboard to create and configure MCP server instances, apply access controls, monitor usage, and view audit logs. The API reference documentation is available in the docs site, enabling programmatic management of MCP servers, keys, and tenants. If you prefer automation or CI/CD, you can script deployment using the Docker workflow and the environment variables described in the installation notes. PlexMCP also provides a guide for self-hosting that covers prerequisites, networking, and scaling considerations.

Prerequisites:

• Docker and Docker Compose installed on your host
• Git
• Optional: access to a PostgreSQL and Redis instance (or run locally with Docker Compose)

Installation steps:

1. Clone the repository: git clone https://github.com/PlexMCP/PlexMCP-OSS.git cd PlexMCP-OSS

2. Prepare environment (examples):

   • Create or connect to a PostgreSQL database and a Redis instance
   • Set DATABASE_URL and REDIS_URL as needed in your environment or .env file

3. Run the initial setup script to generate secrets (optional but recommended): ./scripts/setup.sh

4. Start the prebuilt Docker images with Docker Compose: docker compose --profile prebuilt up -d

5. Open the dashboard in your browser: http://localhost:3000

Notes:

• The setup script generates a .env file with secrets used by the stack. If you run without it, you may need to supply your own secrets and environment variables.
• If you need to customize ports or services, modify docker-compose files under the docker setup in the repository.
• For production deployments, configure TLS termination and proper domain routing in your reverse proxy.

Tips and known considerations:

• Environment variables: DATABASE_URL and REDIS_URL are commonly required; ensure they point to reachable instances for stability.
• Data persistence: Ensure PostgreSQL data directory and Redis persistent storage are properly mounted in production setups.
• Access control: Use the dashboard and API keys features to enforce scoped permissions and MFA where applicable.
• Updates: When upgrading, review the release notes in PlexMCP-OSS for changes to the Docker setup or API changes.
• Troubleshooting: If the dashboard fails to load, check container logs (docker compose logs) for database or API errors, and verify network connectivity between services.