Cursor + contextweaver gateway

Configure Cursor to expose a bounded contextweaver gateway instead of a large raw MCP tool set.

Validate the gateway

uvx contextweaver mcp serve \
  --config examples/recipes/gateway_config.yaml \
  --dry-run

The shipped config loads 11 tools and exposes three gateway meta-tools.

Project configuration

Add the shipped examples/recipes/cursor_mcp.json as .cursor/mcp.json:

{
  "mcpServers": {
    "contextweaver-gateway": {
      "command": "uvx",
      "args": [
        "contextweaver",
        "mcp",
        "serve",
        "--config",
        "${workspaceFolder}/examples/recipes/gateway_config.yaml"
      ]
    }
  }
}

For a global Cursor config, replace ${workspaceFolder} with an absolute path. Restart Cursor after changing MCP configuration.

Installed CLI alternative

"command": "contextweaver",
"args": ["mcp", "serve", "--config", "/absolute/path/to/gateway.yaml"]

What changes

	Direct upstream	With gateway
Advertised surface	Every full tool schema	Three meta-tools
Per-query choices	Entire catalog	At most `top_k` ChoiceCards
Selected schema	Already prompt-visible	Hydrated at execution
Large result	Raw content	Summary plus artifact handle

Agent instruction

Use contextweaver-gateway for large tool catalogs. Call tool_browse before
tool_execute. Use tool_view only for a narrow slice when the summary does not
answer the question. Keep normal authorization and approval checks.

Live upstream servers

Replace catalog: with an upstreams: block in the gateway config and mcp serve launches the listed MCP servers behind the gateway, discovers their tools, and executes selected calls live:

upstreams:
  filesystem:
    type: stdio
    command: npx
    args: ["-y", "@modelcontextprotocol/server-filesystem", "/workspace"]
    namespace: fs

An existing VS Code–style multi-server config migrates with contextweaver mcp import-vscode <config> --apply (dry-run by default).

Current limitations

Live upstream serving covers tools only; resources and prompts over live upstreams still require the static-catalog path.
A cold uvx environment can start slowly; install or pin contextweaver for daily use if the client startup budget is tight.
Cursor prompt caching behavior is client-controlled.
Stdout must contain only MCP wire messages; diagnostics go to stderr.