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

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

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

• Retain architectural decisions across assistant sessions.
• Build linked project context for retrieval-augmented assistance.

Before you start: Context Portal MCP (ConPort) in VS 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) VS Code configuration

1. Choose VS Code configuration scope

   For Context Portal MCP (ConPort), open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

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

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

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

   Context Portal MCP (ConPort): Start in VS Code’s MCP controls; inspect output and trust prompts.

{
  "servers": {
    "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 VS Code

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

get_conport_schema

Look for get_conport_schema among VS Code's agent-mode tools after starting Context Portal MCP (ConPort) through the MCP controls.

Discover exact ConPort tool names and parameter schemas dynamically.

Context Portal MCP (ConPort): full stored tool descriptions

Troubleshooting Context Portal MCP (ConPort) in VS Code

• Make uvx --from (from uv, for Python tools) available in the workspace, container, or remote environment hosting Context Portal MCP (ConPort). Start through VS Code's MCP controls; inspect output and trust prompts.
• Context Portal MCP (ConPort) uses stdio here: VS 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 VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions