Artificial Intelligence
ContextForge — your MCP gateway on a VPS: MCP servers and REST APIs behind a single endpoint, with API tokens and an admin console.
ContextForge is an open-source gateway for the Model Context Protocol (MCP), published by IBM under the Apache-2.0 licence. It sits between your AI agents and the tools they call: you register remote MCP servers, turn existing REST APIs into MCP tools, and group everything into virtual servers — each with its own MCP address.
Instead of configuring every tool in every client (Claude, Cursor, VS Code, n8n, your own agents), you give them one address and a token. The ServOrbit installation locks the instance by default: the API, the admin console and the MCP endpoint refuse any request without a token or a session. The data (tools, servers, tokens) lives in an SQLite database on the VPS.
What gets installed
Expose your internal APIs (CRM, billing, stock) as MCP tools and plug them into Claude, Cursor or an in-house agent, without writing one MCP server per API.
One place to declare tools, one token per developer or agent: when someone leaves, you revoke their token and nothing else changes.
Create one virtual server per client or project: each agent only sees the tools of its server, even if the gateway knows many more.
Guide
Order an Ubuntu 24.04 VPS with 2 GB of RAM and 2 vCPUs. ContextForge requires a domain: your agents call it over HTTPS, with a token, on a stable name, and the console checks where logins come from. It opens on a subdomain of one of your domains, or on the VPS's free subdomain (contextforge.{dns_slug}.servorbit-dns.com), HTTPS included. No need to buy a domain name.
In your client area, select ContextForge, choose the address and click Install. The script deploys the official image, generates the administrator password and the signing and encryption secrets, locks the instance against any request without a token and configures the nginx reverse proxy over HTTPS.
Open https://your-domain/admin and log in with the address [email protected] and the password shown in your client area. Keep this password in a password manager: it is the gateway's administrator account.
From the console, add a remote MCP server by its URL, or declare a REST API as a tool. Through the API, with a token:
`bash
curl -s https://your-domain/tools -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
-d '{"tool":{"name":"github_zen","url":"https://api.github.com/zen","integration_type":"REST","request_type":"GET","input_schema":{"type":"object","properties":{}}}}'`
Then group your tools in a virtual server: it gets its own ID and MCP address.
Create an API token in the console (or with POST /tokens), then give your MCP client the address https://your-domain/servers/<id>/mcp and the header Authorization: Bearer <token>. The client then lists the virtual server's tools and can call them. Without a token, the gateway answers 401.
Frequently asked questions
Self-hosted OpenAI-compatible API gateway for 100+ LLMs — route between Ollama, Anthropic, Azure and more from a single endpoint, with per-key rate limits and spend tracking.
Automation & WorkflowsAutomate your workflows across applications without code. Over 400 integrations, 100% self-hosted on your VPS.
Artificial IntelligenceWeb interface to interact with your local or remote LLMs. Your data stays on your infrastructure — no third party involved.
Browse our help center and FAQ, or reach our team — callback, WhatsApp or email.
Message us on WhatsAppopens in a new tab