Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mcpjungle.com/llms.txt

Use this file to discover all available pages before exploring further.

Cursor supports the streamable HTTP MCP transport natively, so you can point it directly at the Mcpjungle gateway. Once configured, Cursor’s AI agent can discover and invoke every tool registered in Mcpjungle.

​
Prerequisites

  • Mcpjungle running at http://localhost:8080 (or your deployment URL)
  • Cursor installed

​
Configure Cursor

1

Open MCP settings in Cursor

In Cursor, open Settings and navigate to the MCP section.Cursor stores MCP server configuration in a JSON file. You can edit it directly from the settings panel or open the file in your editor.
2

Add Mcpjungle as an MCP server

Add the following entry to your Cursor MCP configuration:
{
  "mcpServers": {
    "mcpjungle": {
      "url": "http://localhost:8080/mcp"
    }
  }
}
Unlike Claude Desktop, Cursor connects over HTTP directly — no mcp-remote bridge is needed.
3

Save and reload

Save the configuration. Cursor will connect to Mcpjungle and load the available tools automatically.
4

Test the connection

Open Cursor’s agent chat and ask it to list the tools it has access to, or invoke a tool directly:
What MCP tools are available?
The agent will query Mcpjungle and return all tools from your registered servers.

​
Enterprise mode (authentication)

If your Mcpjungle instance runs in enterprise mode, create a dedicated MCP client for Cursor and include its access token in the request headers. Create the client with the Mcpjungle CLI: 
mcpjungle create mcp-client cursor-local --allow "server1, server2"
Then update your Cursor MCP configuration to send the token: 
{
  "mcpServers": {
    "mcpjungle": {
      "url": "http://localhost:8080/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ACCESS_TOKEN"
      }
    }
  }
}
Replace YOUR_ACCESS_TOKEN with the token printed by mcpjungle create mcp-client.
In enterprise mode, a client can only access the servers listed in its --allow flag. If Cursor reports no tools, verify the client was created with the correct server names.

​
Limit tools with Tool Groups

When many MCP servers are registered, the full tool list can be long. Use Tool Groups to expose only the tools relevant to your Cursor workflow. Create a group and point Cursor at its dedicated endpoint: 
{
  "mcpServers": {
    "mcpjungle": {
      "url": "http://localhost:8080/v0/groups/cursor-tools/mcp"
    }
  }
}
Create a separate Tool Group for each agent or workflow. This keeps the tool list focused and improves the agent’s decision-making.