Logo ContextForge

Artificial Intelligence

ContextForge

ContextForge — your MCP gateway on a VPS: MCP servers and REST APIs behind a single endpoint, with API tokens and an admin console.

About ContextForge

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

Ready when the VPS starts

Compatible OS
Choice of Linux distributions
Application
ContextForge
Tech stack
DockerPythonSQLite
Minimum RAM
2 GB minimum
Minimum CPU
2 vCPU
Default port
8118
Access
root over SSH

Key features

  • A single MCP endpoint — your agents connect to one address, however many tools sit behind it.
  • REST APIs turned into MCP tools — a URL, a method and an input schema are enough, no MCP server to write.
  • Virtual servers — group the tools an agent or a project needs, each with its own /servers/<id>/mcp address.
  • MCP server federation — register remote MCP servers and expose their tools in the same place.
  • Time-limited API tokens — one token per client or agent, revocable without touching the others.
  • A web admin console — tools, servers, tokens and users are managed from /admin.

When to use this solution?

Give tools to your AI agents

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.

Centralise a team's access

One place to declare tools, one token per developer or agent: when someone leaves, you revoke their token and nothing else changes.

Separate tools by project

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

Deploy ContextForge on your VPS

  1. Create the VPS and choose the address

    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.

  2. Install ContextForge from the Marketplace

    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.

  3. Log in for the first time

    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.

  4. Register a tool

    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.

  5. Connect an MCP client

    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

Questions about ContextForge

← Back to Artificial IntelligenceAll applications
An MCP server provides tools; ContextForge brings them together. The gateway registers several MCP servers and REST APIs, exposes them behind a single address and controls who can reach them with tokens. Your clients have only one connection to configure.

Need help?

Browse our help center and FAQ, or reach our team — callback, WhatsApp or email.

Message us on WhatsAppopens in a new tab