Deploy a known version
Keep source, configuration and deployment history together. Inspect a failed build instead of guessing why the endpoint is unavailable.
Explore documentation →MCP hosting, with the controls you need
Your MCP.
Hosted. Under control.
Bring the server you already built. Give it an HTTPS endpoint, control who can call it, and understand what happens after every request.
Guided early access · Supported Node.js stdio repositories · Compatibility checks first
YOUR REPOSITORY→MCP Ops→YOUR CLIENTS
01 / FROM SOURCE TO SERVICE
A repository. A service. A workflow.
Follow the Basecamp MCP journey from source to a client connection. This is a walkthrough, not a live dashboard or a public Basecamp account.
Read the hosting guide →BASECAMP / MCPWALKTHROUGH
PUBLIC REPOSITORY
seven-hills-software / basecamp-mcpKeep the server. Lose the setup handoff.
Start with a repository you control. Review its runtime, start command and required credentials before building a pinned revision.
Repository → pinned commit → reviewed runtime
The operational layer around your tools
Ship the integration. Keep the control.
Give every consumer a boundary
Use separate keys, tool permissions and request limits. Revoke one consumer without replacing every client connection.
Explore documentation →See what happened
Review per-MCP request history and usage. Follow a failed call back to its context instead of treating a running container as proof of success.
Explore documentation →Choose your starting point
Already have an MCP? Start there.
Bring your GitHub repository
Public or private source. A reviewed Node.js stdio runtime. Your upstream credentials stay separate from source access.
Host an existing MCPStart from your API
Bring OpenAPI, documentation or Markdown. Review the generated tools and permissions before deployment.
Explore API-to-MCP →Know the connection contract
Open protocol. Explicit compatibility.
- Runtime
- Node.js · stdio import
- Remote transport
- Streamable HTTP · JSON responses
- Consumer access
- Scoped bearer API keys
Not supported today: OAuth-only clients, legacy SSE endpoints and long-lived event streams. Check your client's settings before deployment.
Check client requirements →DOCUMENTATION / HUMAN + MACHINE
For you. And the agent beside you.
Task-based guides and machine-readable documentation help you plan a deployment without guessing the platform contract.
Explore documentation →START WITH THE CONTRACT01 / Host an existing MCP ↗02 / Keys and upstream credentials ↗03 / Client compatibility ↗04 / Agent-assisted setup ↗
Agent-assisted planning is available through the docs. A deployment CLI and autonomous account provisioning are not released.
agents.md ↗Start with the right-sized deployment.
Review hosting allowances, resource limits and compatibility before committing to a customer workload. Guided early access does not include an uptime SLA.
Before your first deployment
Clear answers. Fewer surprises.
What is MCP server hosting?
MCP hosting runs your Model Context Protocol server as a service that compatible clients can reach. Beyond running a process, you need a stable endpoint, authentication, deployment controls and a way to investigate failed calls. MCP Ops brings those tasks into one workspace.
Can I bring an existing GitHub MCP server?
The current guided import supports Node.js stdio repositories, with public repositories or a scoped token for private access. It is a restricted beta, not an unrestricted public GitHub hosting service. Send your repository and start requirements for a compatibility review.
Does it work with every MCP client?
No. The current gateway uses Streamable HTTP with JSON responses and bearer API keys. A client must support those connection settings. OAuth-only clients, legacy /sse endpoints and long-lived event streams are not supported today.
How do I control who can call my tools?
Create a separate key for each consumer, set an expiry, restrict callable tool names and configure a per-key request limit. Revoke one consumer without replacing every client key. Tool-call permissions do not necessarily hide tool metadata.
Can I use my own domain?
Custom-domain routing is available as an operator-managed setup. DNS ownership, a trusted certificate and a deployment-bound configuration must be verified before activation. Pointing a DNS record alone is not enough.
Is this an enterprise service with an uptime SLA?
MCP Ops is currently in guided early access. We do not advertise an uptime SLA, SOC 2 certification, SSO or fully implemented MCP OAuth. Review the current feature and infrastructure fit before sending business-critical or sensitive workloads.
Go from understanding to operating
Guides worth keeping open.
How to host an existing GitHub MCP server without losing control
A practical deployment checklist for repository owners: runtime compatibility, private access, secrets, consumer keys and a real first tool call.
Read guide →MCP server best practices: a deployment and operations checklist
Design bounded tools, separate identity from upstream access, test failure paths and prepare a repeatable MCP release with an actionable acceptance checklist.
Read guide →MCP hosting costs: CPU, memory, traffic, and the idle problem
Why MCP cost depends on runtime isolation and usage patterns, and how to price a hosting platform sustainably.
Read guide →