Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Apache Camel API Gateway with REST-to-MCP bridging for LLM agents.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"capi-core": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/surisoft/capi-core:1.417.5"
]
}
}
}Run this in your terminal
claude mcp add capi-core -- docker run -i --rm docker.io/surisoft/capi-core:1.417.5Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"capi-core": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/surisoft/capi-core:1.417.5"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"capi-core": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/surisoft/capi-core:1.417.5"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account surisoft-io, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 8 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
CAPI is a lightweight API Gateway and load balancer built on Undertow's async proxy architecture. Services register themselves in HashiCorp Consul, and CAPI automatically discovers them, creates proxy handlers, and applies security, throttling, and observability policies — no database required.
X-Forwarded-*)CAPI's MCP Gateway turns any existing REST API into an MCP tool — no code changes on your backends.
Register a service in Consul with MCP metadata, and LLM agents (Claude Desktop, Cursor, custom agents) can discover and invoke it immediately. Your REST services don't need to know anything about MCP, JSON-RPC, or tool schemas. CAPI handles the translation:
LLM Agent CAPI Your REST API
(unchanged) tools/list ──────────────► reads Consul metadata ◄────────────── returns tool catalog
tools/call ──────────────► extracts arguments {"name":"..."} POST /endpoint ──────────────► handles request wraps response ◄────────────── returns JSON ◄────────────── MCP-formatted result
CAPI also supports real MCP Server backends — services that already speak JSON-RPC 2.0. Register them with mcp-type: server and CAPI discovers their tools automatically via tools/list, then proxies tools/call requests transparently. Both REST and MCP Server backends are aggregated under one unified MCP endpoint.
Unlike dedicated MCP gateways that require all backends to be MCP Servers, CAPI bridges the gap between existing REST infrastructure and LLM-native protocols. See the MCP Gateway docs and the demo for a working example with both backend types.
CAPI requires the CAPI_CONFIG_FILE environment variable pointing to a valid configuration file.
CAPI_CONFIG_FILE=config/config.yaml java -jar capi-core.jar
docker run -p 8380:8380 -p 8381:8381 \
-v $(pwd)/config/config.yaml:/capi/config/config.yaml \ -e CAPI_CONFIG_FILE=/capi/config/config.yaml \ surisoft/capi-core
A Helm chart is available in helm/capi-core/.
helm install capi-core helm/capi-core
helm install capi-core helm/capi-core -f my-values.yaml
helm install capi-core helm/capi-core \ --set capi.ssl.enabled=true \ --set capi.ssl.keystoreBase64= \ --set capi.ssl.password=changeit
See helm/capi-core/values.yaml for all available configuration options.
| Port | Description | Config key |
|---|---|---|
| 8380 | REST API gateway | capi.rest.port |
| 8381 | Admin / metrics | capi.adminPort |
| 8382 | WebSocket gateway | capi.websocket.port |
| 8383 | MCP Gateway (experimental) | capi.mcp.port |
| 8384 | gRPC Gateway (experimental) | capi.grpc.port |
The runningMode field controls which types of services CAPI will proxy:
| Mode | Description |
|---|---|
full | Proxies REST, WebSocket, and SSE services (default) |
websocket | Only proxies WebSocket services |
sse | Only proxies SSE services |
| Document | Description |
|---|---|
| Service Registration | How to register services in Consul and configure routing, security, and throttling via metadata |
| Security | OAuth2/OIDC and OPA authorization configuration |
| Admin API | Admin endpoints reference (health, metrics, routes, OpenAPI) |
| Configuration Reference | Complete YAML configuration reference with all fields |
| MCP Gateway (Experimental) | MCP Gateway for LLM tool integration via JSON-RPC 2.0 |
| gRPC Gateway (Experimental) | Transparent gRPC reverse proxy with header-based routing |