How do I authorize Tempreon in Warp?

Warp uses browser-based OAuth that triggers lazily — the first time a Warp agent actually uses Tempreon, your browser opens the consent screen for you to sign in and approve. Credentials are stored on-device, so you authenticate once per machine. If you work across several machines, expect to sign in again on each one; that per-machine prompt is expected, not an error.

Where do Warp's MCP server settings live so I can add Tempreon?

Open Settings, go to Agents, then MCP servers, and click Add, then paste the Tempreon JSON config, whose root key is mcpServers. If you prefer files, the same JSON works in ~/.warp/.mcp.json for all projects or .warp/.mcp.json inside a project directory. Project-level configs need explicit approval before Warp loads them.

My Warp cloud agent can't reach Tempreon — what's going on?

Warp documents that a direct url MCP server which requires OAuth and has no Authorization header can't be used by cloud agents, and Tempreon has no static token to put in a header. Run the task with a local agent instead, which authenticates through the normal browser OAuth flow. This is the most common Warp-specific snag, and it is a current platform limitation rather than a configuration problem on your end.

Warp Setup — Docs | Tempreon™

Overview

Warp is an agentic terminal — its agents write code, run commands, and debug alongside you, powered by Claude, GPT, and Gemini models, or your own API keys. It supports MCP servers with browser-based OAuth, so Tempreon plugs in directly.

Once connected, your AI loads your Core Imprint, searches your Knowledge Vault, and remembers what it learns — across every tool. For Warp, that means agents that already know your stack, your conventions, and the decisions you made last week, in whichever project you open.

Quick path: Settings → Agents → MCP servers → + Add → paste the Tempreon JSON → approve the browser OAuth on first use.

Availability note (as of September 2026): Warp's MCP documentation names no plan restriction, and its pricing page doesn't list MCP as a tiered feature — so if you don't see MCP servers in Settings, check for an update before assuming your plan is the reason. Agent usage is metered by credits; bringing your own API key is free. One caveat: Warp's cloud agents can't use an OAuth MCP server that has no Authorization header, so Tempreon works with local agents.

Prerequisites

Warp installed (any plan)
A Tempreon account with at least one available Bridge slot
Your Tempreon MCP server URL (also shown in your Bridges dashboard)

Step-by-Step Setup

1. Open the MCP servers settings

Open Settings → Agents → MCP servers and click + Add.

2. Paste the configuration

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

Prefer file-based config? The same JSON works in ~/.warp/.mcp.json (global, all projects) or .warp/.mcp.json inside a project directory — project-level configs need explicit approval before Warp loads them.

3. Authorize the connection

The first time an agent uses Tempreon, your browser opens with the Tempreon consent screen. Sign in if prompted and approve. Credentials are stored on-device, so you authenticate once per machine.

4. Verify it's working

Ask a Warp agent to "start my session" — if it calls session_start and comes back with your context, the Bridge is live.

Troubleshooting

Cloud agents can't reach Tempreon. Warp's cloud agents don't support OAuth MCP servers as of July 2026. Run the task with a local agent instead.

A project-level .warp/.mcp.json isn't loading. Project configs require explicit approval — look for Warp's approval prompt, or move the entry to the global ~/.warp/.mcp.json.

Tempreon asks you to sign in again on another machine. Expected — credentials are stored on-device, so each machine authenticates separately.

The connection fails immediately. Confirm the URL ends in /mcp with no trailing slash: https://api.tempreon.com/functions/v1/tempreon-mcp/mcp.

Also connect: Raycast · Claude Code · Cursor

Try saying...

"Start my session." — triggers session_start to load your Core Imprint
"Check my knowledge base for how we set up [system] before you touch the config." — grounds the agent in your past decisions
"Remember that this repo deploys via [process]." — saves the convention for every future session