Context Portal MCP (ConPort) for Claude Code: Setup & Config

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

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

• Retain architectural decisions across assistant sessions.
• Bootstrap product context from an approved project brief.

Before you start: Context Portal MCP (ConPort) in Claude Code

• 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) Claude Code configuration

1. Choose Claude Code configuration scope

   For Context Portal MCP (ConPort), open Project scope: .mcp.json at the repository root. Project JSON: merge into mcpServers; user scope: use the CLI.

2. Add Context Portal MCP (ConPort) to Claude Code

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

3. Check Context Portal MCP (ConPort) in Claude Code

   Context Portal MCP (ConPort): Inspect claude mcp list and /mcp status.

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

claude mcp add-json --scope project 'context-portal' '{"type":"stdio","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 Claude Code

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

get_conport_schema

For Context Portal MCP (ConPort)'s get_conport_schema, review the permission request and arguments in Claude Code before approval.

Discover exact ConPort tool names and parameter schemas dynamically.

Context Portal MCP (ConPort): full stored tool descriptions

Troubleshooting Context Portal MCP (ConPort) in Claude Code

• If Context Portal MCP (ConPort) fails to start, check uvx --from (from uv, for Python tools), the working directory, and Claude Code's selected scope; inspect claude mcp list and /mcp.
• Context Portal MCP (ConPort) uses stdio here: Claude Code 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 Claude Code troubleshooting lives in the /clients/claude-code guide.

Frequently asked questions