<strong>Run all your MCP servers behind one endpoint</strong>
Mcpjungle mcp server lets Claude, Cursor and other MCP clients work with MCPJungle directly. Run all your MCP servers behind one endpoint.
Run all your MCP servers behind one endpoint
Once connected, the assistant can call these 4 tools directly:
Database — The mcpjungle server relies on a database and by default, creates a SQLite DB file mcpjungle.db in the current working directoryClaude — The Claude tool exposed by this serverCursor — You can watch a quick video on How to connect Cursor to MCPJungleCopilot — Follow Copilot's doc on [configuraing a MCP server manually](https://docs.github.com/en/copilot/how-tos/provide-context/use-mcp/extend-copilot-chat-with-mcp#conThe server is distributed via a container image as ghcr.io/mcpjungle/mcpjungle, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
Before the server will start you need to supply 8 environment variables: API_TOKEN, SQLITE_DB_PATH, DATABASE_URL, POSTGRES_HOST, POSTGRES_PORT, POSTGRES_USER, POSTGRES_USER_FILE, POSTGRES_PASSWORD. Keep credentials in your client's env block or a secrets manager rather than committing them.
Database servers turn schema archaeology and ad-hoc reporting into conversation, which is why they tend to be the second or third server people install. MCPJungle sits in that group, and the shape of its toolset — Database, Claude, Cursor among others — tells you what it is really for. Worth comparing against the other databases servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| Database | The mcpjungle server relies on a database and by default, creates a SQLite DB file mcpjungle.db in the current working directory. |
| Claude | The Claude tool exposed by this server. |
| Cursor | You can watch a quick video on [How to connect Cursor to MCPJungle](https://youtu.be/SaUqj-eLPnw). |
| Copilot | Follow Copilot's doc on [configuraing a MCP server manually](https://docs.github.com/en/copilot/how-tos/provide-context/use-mcp/extend-copilot-chat-with-mcp#configuring-mcp-servers-manually-1). |
### Cursor
```json
{
"mcpServers": {
"mcpjungle": {
"url": "http://localhost:8080/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| API_TOKEN | Credential the server authenticates with. | Yes |
| SQLITE_DB_PATH | Filesystem location the server is allowed to use. | Optional |
| DATABASE_URL | Endpoint or connection string the server talks to. | Yes |
| POSTGRES_HOST | Endpoint or connection string the server talks to. | Optional |
| POSTGRES_PORT | Configuration value read at startup. | Optional |
| POSTGRES_USER | Configuration value read at startup. | Optional |
| POSTGRES_USER_FILE | Configuration value read at startup. | Optional |
| POSTGRES_PASSWORD | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.