Skip to main content

Connect Cline

OAuth browser sign-in​

  1. Open MCP Servers in Cline. In Cline 4.1.23, use Customize → MCP → Installed → Add Remote Server.
  2. Name the server reconstruct, enter https://reconstruct.dev/mcp, and select Streamable HTTP.
  3. Add the server with no Authorization header. Select Authenticate when prompted.
  4. Allow VS Code to open the Reconstruct sign-in page. Sign in and approve access, then return to Cline.

Cline registers its OAuth client automatically and stores credentials after consent. No client secret or manually copied token is needed. The Reconstruct scopes are openid aud-mcp.

Alternatively, open Edit Configuration and merge this entry into mcpServers:

{
  "mcpServers": {
    "reconstruct": {
      "type": "streamableHttp",
      "url": "https://reconstruct.dev/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Set type explicitly; the legacy SSE default does not match Reconstruct. Let Cline manage the generated oauth fields.

Personal access token​

Create an MCP token. Add this field to the server entry instead of OAuth:

"headers": {
  "Authorization": "Bearer <your MCP token>"
}

Replace the placeholder locally. Keep the configuration private. Remove this header when switching to OAuth.

Check the connection​

Expand reconstruct in the MCP panel and confirm its connected status and discovered tools, resources and prompts. Start an agent task and ask:

Use Reconstruct MCP to call list_products. Do not create or update captures.

Connection discovery was verified with Cline 4.1.23. The free step-5-preview model used in that test did not expose MCP invocation tools to the agent, although the server connected. If your model cannot call MCP tools, choose a model/provider that exposes them and start a new task; reconnecting alone does not verify a tool call.

See Cline's MCP documentation, troubleshooting and Reconstruct skills.