Public-facing access
Expose MCP endpoints through a controlled web layer instead of ad hoc local setups.
Secure by default
Secure MCP infrastructure for lightweight deployment
mcpdev.co.uk provides a clean public front door for tenant-aware MCP services, with a path toward a fuller management and routing platform over time.
Built for controlled exposure, lightweight hosting, and future multi-tenant operations.
Overview
A practical foundation for public MCP services
The project is aimed at making MCP deployments easier to expose, route, and manage without starting with heavy infrastructure.
Tenant-aware routing
Separate demo, customer, or environment-specific routes under one managed domain.
Platform-ready structure
Start with a landing page and grow toward a fuller admin and runtime platform over time.
Why It Matters
Real public exposure needs more than a local demo
Many MCP experiments work locally but are not prepared for internet-facing use.
Demo and customer environments need clearer separation and more predictable routing.
Security matters immediately once a service moves from development to public access.
Lightweight hardware should still support disciplined platform design.
Capabilities
Built to start small and expand cleanly
Tenant-aware routes
Prepare for path-based routing such as /demo/mcp or /customer/mcp.
Secure web edge
Serve the public layer through HTTPS, reverse proxying, and strict headers.
Lightweight hosting
Keep the stack lean enough for local development and future Raspberry Pi deployment.
Management-ready design
Leave space for future admin tools, tenant controls, and service visibility.
Demo to production path
Support early demos now without blocking later platform growth.
Security
Security is part of the design, not an afterthought
The first public release stays intentionally small: one landing page, minimal exposed surface area, HTTPS-only delivery, and clear separation from future admin and tenant endpoints.
- HTTPS-only public access behind a reverse proxy
- Strict response headers and minimal client-side complexity
- No exposed admin routes in version 1
- Clear separation between public, admin, and tenant paths as the platform expands
- Portable deployment model for controlled transfer to Raspberry Pi hosting
Architecture
How the project grows
The public site comes first. Later, the same domain can expand to include an admin interface and tenant-specific MCP routes without replacing the front door.
01
Landing Page
Fast, low-risk public presence with a small attack surface.
02
Admin Layer
Future management tooling for tenants, testing, and service visibility.
03
Tenant MCP Endpoints
Path-based routes for demos, customers, and environment-specific services.
Contact
Follow the project
Interested in secure, lightweight MCP deployment? Register your interest and stay close to the build as the platform develops.
Contact mcpdev
Replace hello@mcpdev.co.uk with your preferred mailbox when you are ready to go live.