Cline Setup

Overview

Cline is a free, open-source coding agent that runs inside VS Code (and its forks). Connect Tempreon and Cline loads your Core Imprint, searches your Knowledge Vault, and remembers what it learns, across every tool you use.

Cline is bring-your-own-model — OpenRouter, Ollama, and most other providers work — so connecting Tempreon gives whatever model you run your full context, not just one vendor's.

Quick path: MCP Servers icon → Remote Servers tab → name + Tempreon URL + Transport: Streamable HTTP → Add Server → approve in the browser.

Prerequisites

• VS Code (or a compatible fork) with the Cline extension installed and a model provider configured
• A Tempreon account with at least one available Bridge slot
• The Tempreon server URL (also shown in your Bridges dashboard)

Step-by-Step Setup

1. Add the server from the UI

1. Click the MCP Servers icon in Cline's top bar
2. Open the Remote Servers tab
3. Enter tempreon as the server name
4. Paste the URL:

https://api.tempreon.com/functions/v1/tempreon-mcp/mcp

5. Set Transport to Streamable HTTP
6. Click Add Server

2. Or edit the config file directly

Cline's settings live in cline_mcp_settings.json. Current builds keep it under Cline's own directory:

~/.cline/data/settings/cline_mcp_settings.json

The Cline CLI reads a separate file, ~/.cline/mcp.json. Older builds kept the settings file under VS Code's global storage for the Cline extension, so if the path above doesn't exist, look there.

Add the server like this:

{
  "mcpServers": {
    "tempreon": {
      "type": "streamableHttp",
      "url": "https://api.tempreon.com/functions/v1/tempreon-mcp/mcp"
    }
  }
}

The type field is required. If you omit "type": "streamableHttp" (camelCase, exactly as written), Cline falls back to its legacy SSE transport — and the connection fails. This is the most common Cline setup error.

3. Authorize the connection

On first connect, Cline opens a browser tab to Tempreon's consent screen. Sign in to your Tempreon account, review the request, and approve. Back in Cline, the server shows as connected.

4. Confirm the tools are active

In the MCP Servers panel, expand the Tempreon entry to see its tools, or ask Cline "What Tempreon tools do you have access to?" If it answers with a list, the Bridge is live.

Troubleshooting

Connection fails immediately. Two usual causes: the URL must end in /mcp with no trailing slash, and the JSON config must include "type": "streamableHttp" — without it Cline tries legacy SSE and fails.

Worked before, now fails with an auth error. Older Cline builds had a quirk where re-authentication could fail after tokens expired. The fix: delete the Tempreon server and re-add it, which runs a fresh OAuth flow. Leave the headers field out entirely — Cline's docs show a Bearer header because that's the static-token pattern, but Tempreon has no static token and opens a browser for OAuth on first connect.

Re-adding doesn't help. Don't reach for the mcp-remote stdio proxy here — Cline has its own native Streamable HTTP transport and deliberately strips that proxy shape, so adding it duplicates the OAuth handling rather than fixing it. Update Cline to a current version instead: 4.1.7 and later carry OAuth fixes for remote servers, including surfacing authorization on a 401 rather than failing outright.

Tools listed but calls do nothing. Check for Cline's per-tool approval prompt — approve the first call (and optionally auto-approve the Tempreon tools you trust).

Also connect: VS Code · Cursor · Windsurf

Try saying...

• "Start my session." — triggers session_start to load your Core Imprint
• "Search my knowledge base for context on this repo before you start." — exercises knowledge retrieval end-to-end
• "Remember that we always run the linter before committing." — stores a working rule for every future session