Documentation
MCPGoose guide
Deploy Python and Node.js MCP repositories or exact npm/PyPI package versions and connect clients through authenticated remote endpoints. Source access follows your account’s hosting allowances.
Deploy an MCP server
Sign in and open Deploy MCP, or choose a template. Enter the source, startup command and instance variables, then review before deployment. Builds and readiness checks run on the hosting service; the progress screen reflects their actual state.
A failed instance retains its configuration and occupies a slot until cleanup completes.
npm and Python packages
In Deploy MCP, choose npm package or Python package · PyPI, enter the package name and an exact released version, and continue to verify it with the registry. Version ranges, latest tags, install flags and arbitrary download URLs are not accepted. Review shows the full source fingerprint and artifact integrity separately from Git commits.
The package type selects its matching runtime. npm executable names come from the package documentation, not necessarily its package name; use its installed executable under /app/source/node_modules/.bin. Python console scripts are on PATH, or use python with -m and the documented module in separate argument fields. Startup does not install or resolve packages with npx or pip.
Changing a package name or version requires registry verification again. Builds install the verified source and dependencies into an immutable instance artifact, and readiness checks still have to pass. Unsupported dependencies or startup commands produce a failed deployment with configuration and build output retained.
Repository setup suggestions
For public GitHub repositories, source verification inspects supported manifests and README examples for installed startup commands, environment settings and authentication requirements. Suggestions include their evidence and stay editable. Add only the hints your chosen startup needs; alternative login methods and HTTP settings may not apply to a stdio server. No README login or installation commands run automatically.
Authenticate using the repository’s own instructions. If it reads a saved credential file, map a secret variable to a relative path under /home/mcpruntime in Variables. Paste the complete file content into the blank secret field. Review shows the path and variable name, never the content. Mapped files are restored privately at startup; runtime changes remain temporary. Internet access is an explicit permission even when the repository suggests it.
Variables and runtime storage
Environment values are encrypted for their instance. Secret values cannot be read back after saving. Runtime files, caches and sessions are temporary; restarts restore built code and saved environment values.
Connect an MCP client
After readiness succeeds, copy the endpoint from the instance and add it to an OAuth-compatible client. Complete authorization in your browser, review the requested scopes and instance tools, then approve the connection. MCPGoose supports OAuth client access; clients that require a manually supplied bearer token cannot connect.
Review active connections and revoke them individually in the instance’s Access tab. Revocation blocks future requests and closes sessions for that client.
Free availability and catalog
Check Free availability on the Free access page. Signing in does not reserve a hosting place: activation is a separate request, and a closed or full cohort offers waitlist options. You can check your status or leave the waitlist after signing in.
Free hosting deploys published catalog entries with fixed source, startup and network settings. Configure the instance name and declared environment fields, then review the immutable source and prepared artifact. Catalog activation stays closed until supported Python and npm artifacts are available. Accounts with custom-source access retain editable repository and package deployments.
Check Free availabilityAccount and allowances
Settings shows your authenticated account and assigned hosting allowances. Monthly usage shows recorded requests and builds separately from your allowances, with the next UTC reset. Stopped and failed instances count toward capacity.
Open settingsAccount security and deletion
Sensitive actions can ask you to verify your Clerk credentials again. Canceling verification leaves the hosting action unapplied. Settings offers full sign-in and security management only when the operator has enabled the signed identity-lifecycle integration; otherwise the account-name editor remains available.
Delete hosting account requires typing your account ID. Access is disabled immediately while resource cleanup continues. Return to Settings to check status or retry cleanup. Your sign-in identity remains available until you separately arrange its removal; usage and audit records are retained.
Help
For a failed deployment, open its Logs and review the saved Configuration before retrying. If a client cannot connect, check its endpoint, OAuth authorization and tool permissions in Access. Revoke and reconnect the OAuth client if its grant is no longer valid.
For account sign-in changes, use the configured security controls or contact your pilot operator.
Local development
The Next.js application exports static assets. Hosting operations require the same-origin Cloudflare control API and a configured Clerk session. A plain static file server can render public pages but cannot provision servers or authenticate a hosting account.