Cursor Feature Request – cq Integration

Ideas Feature Requests
, , ,
3

Hey, thanks for the feature request.

Good news, most of what you’re describing is already possible with Cursor’s current MCP support:

  1. MCP server in agent mode: this works today. You can register cq-mcp-server in .cursor/mcp.json using the standard stdio transport. The config would look like:
{
  "mcpServers": {
    "cq": {
      "command": "uv",
      "args": ["run", "--directory", "~/.cq/server", "cq-mcp-server"],
      "env": {
        "CQ_TEAM_ADDR": "http://your-team-api:8742",
        "CQ_TEAM_API_KEY": "your-key"
      }
    }
  }
}

Docs: Model Context Protocol (MCP) | Cursor Docs

  1. Post-error hooks: Cursor supports hooks that can trigger scripts on specific agent events. You could wire up a hook to call cq store after certain actions.

  2. Pre-task knowledge request: once the MCP server is registered, the agent can call cq tools during a session. You can also use project rules .cursor/rules to tell the agent to request cq before starting tasks.

  3. Team sync: env vars in mcp.json are passed through to the server, so CQ_TEAM_ADDR and CQ_TEAM_API_KEY should work as-is.

  4. Dynamic rules injection: this is the one part that doesn’t have a direct path today. You could approximate it by having the agent request cq and use the results manually, but automatic rule injection from MCP results isn’t a feature yet.

You might also find these community discussions useful, others are solving similar agent memory problems:

Have you tried running cq as a standard MCP server in Cursor? Curious if you ran into any specific blockers.