Context Portal MCP (ConPort) for Cursor: Setup & Config

What you can do with Context Portal MCP (ConPort) in Cursor

Choose it for persistent, linked project memory rather than a collection of unstructured context files.

• Build linked project context for retrieval-augmented assistance.
• Bootstrap product context from an approved project brief.

Before you start: Context Portal MCP (ConPort) in Cursor

• Python 3.8 or later recommended
• uv with uvx
• An MCP-compatible client that supplies workspace context

Uses the README's alternative without launch-time --workspace_id. Supply workspace_id on tool calls; database initialization then occurs on the first call. Absolute launch-time paths are another option. Some IDEs do not expand ${workspaceFolder}. No required environment variables are stated.

Context Portal MCP (ConPort) Cursor configuration

1. Choose Cursor configuration scope

   For Context Portal MCP (ConPort), open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

2. Add Context Portal MCP (ConPort) to Cursor

   Use the context-portal entry below in mcpServers. Keep Context Portal MCP (ConPort)'s documented stdio connection fields and your other Cursor entries.

3. Check Context Portal MCP (ConPort) in Cursor

   Context Portal MCP (ConPort): Enable in Cursor’s MCP settings; inspect tools.

{
  "mcpServers": {
    "context-portal": {
      "command": "uvx",
      "args": [
        "--from",
        "context-portal-mcp",
        "conport-mcp",
        "--mode",
        "stdio",
        "--log-file",
        "./logs/conport.log",
        "--log-level",
        "INFO"
      ],
      "env": {}
    }
  }
}

Context Portal MCP (ConPort) tools available to Cursor

Context Portal MCP (ConPort)'s stored tool list documents 1 tool; compare it with Cursor's connected tool list, because the stored list is not a live check.

get_conport_schema

Find get_conport_schema under Context Portal MCP (ConPort) in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Discover exact ConPort tool names and parameter schemas dynamically.

Context Portal MCP (ConPort): full stored tool descriptions

Troubleshooting Context Portal MCP (ConPort) in Cursor

• Cursor must find uvx --from (from uv, for Python tools) for Context Portal MCP (ConPort). Enable the project/user entry in MCP settings and inspect its tools.
• Context Portal MCP (ConPort) uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: Some IDEs do not expand workspace variables as expected.
• Known limitation: Reliable agent use benefits from initialization and custom-instruction setup.
• General Cursor troubleshooting lives in the /clients/cursor guide.

Frequently asked questions