Self-hosted MCP Server
Run the Hyperstack API MCP Server yourself when the hosted server does not fit. A self-hosted instance runs in a network you control and authenticates every request with one API key, so all tool calls act as the account that issued it.
Run your own instance when one of the following applies:
- Your client is not supported by the hosted server. The hosted server accepts connections from clients running on your own machine, Claude on the web, and Open WebUI's hosted service.
- Your integration runs without a person present. The hosted server signs you in through a browser, so scheduled jobs and other unattended integrations authenticate with an API key instead.
- Your network restricts outbound connections.
Topics
Local Installation
Install Docker, run the server, verify it, manage the container, and connect a client to it.
Configuration Reference
Environment variables for authentication mode, API key, API endpoint overrides, and logging.
Was this page helpful?