MCP Gateway for Cursor: Setup & Config

What you can do with MCP Gateway in Cursor

Pick it to apply shared security plugins and visibility across otherwise separate MCP servers.

• Trace tool calls through the optional Xetrack plugin
• Scan server reputation and tool descriptions before loading

Before you start: MCP Gateway in Cursor

• Python and pip
• The mcp-gateway package
• Xetrack installed for this example
• An MCP configuration containing nested server definitions

Install with pip install mcp-gateway and pip install xetrack. Replace the configuration path if needed. This example enables basic masking and tracing; Lasso API credentials and Presidio extras are needed only for those plugins.

MCP Gateway Cursor configuration

1. Choose Cursor configuration scope

   For MCP Gateway, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

2. Add MCP Gateway to Cursor

   Use the mcp-gateway-lasso-security entry below in mcpServers. Keep MCP Gateway's documented stdio connection fields and your other Cursor entries.

3. Check MCP Gateway in Cursor

   MCP Gateway: Enable in Cursor’s MCP settings; inspect tools.

{
  "mcpServers": {
    "mcp-gateway-lasso-security": {
      "command": "mcp-gateway",
      "args": [
        "--mcp-json-path",
        "~/.cursor/mcp.json",
        "-p",
        "basic",
        "-p",
        "xetrack"
      ],
      "env": {}
    }
  }
}

MCP Gateway tools available to Cursor

MCP Gateway's stored tool list documents 2 tools; compare it with Cursor's connected tool list, because the stored list is not a live check.

get_metadata

Find get_metadata under MCP Gateway in Cursor's MCP settings; inspect its arguments when the agent requests a call.

run_tool

Find run_tool under MCP Gateway in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Invoke a downstream capability with configured request and response filtering.

MCP Gateway: full stored tool descriptions

Troubleshooting MCP Gateway in Cursor

• Cursor must find mcp-gateway for MCP Gateway. Enable the project/user entry in MCP settings and inspect its tools.
• MCP Gateway uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: Presidio and Xetrack require additional dependencies
• Known limitation: Advanced Lasso guardrails need an API key and external API checks
• Known limitation: Scanner results can be manually overridden
• General Cursor troubleshooting lives in the /clients/cursor guide.

Frequently asked questions