Guide
Host an existing MCP
Bring a supported GitHub repository, review its configuration and verify the hosted connection.
Check the fit first
Existing repository hosting is currently a restricted Node.js stdio import. Review the package manifest, dependency lockfile, build/start requirements and upstream credential needs. Python, arbitrary containers and persistent disk requirements are not implied by GitHub support.
Import your repository
Open MCP servers → Create MCP → GitHub import. Use a public repository URL you control, or provide a scoped repository credential for private source. Pin the source revision. Do not use the repository token as an upstream API credential. Hosting is subject to workspace entitlement and runtime availability.
Build and verify readiness
Review the build output and configured entrypoint. Store upstream credentials through the platform secret controls, never in the repository, tool description or a chat prompt. Wait for runtime readiness; a submitted deployment is not proof that a client can call it.
Connect one consumer
Create an expiring, scoped consumer key and copy the deployment endpoint from the console. Use a client that supports Streamable HTTP with JSON responses and an Authorization bearer token. Initialize the connection, list tools, and run a permitted read-only call. A Basecamp repository still requires valid upstream Basecamp access.
Accept the workflow before handoff
Inspect the call outcome and per-MCP request history. Test an invalid key, a disallowed tool and the configured request limit without running destructive operations. Keep the source revision and operating instructions with the deployment. Pause or revoke access if the acceptance check fails.