How does authorizing Tempreon work in Zed?

When the server needs sign-in, Zed shows an Authenticate button for it, and the Add Remote Server form handles this step inline. Click it and a browser tab opens to Tempreon's consent screen; sign in and approve. Zed stores your tokens in the system keychain and refreshes them automatically, so you should not need to authorize again. Leaving any Authorization header out of your settings is what tells Zed to use this flow.

Where do I add the Tempreon server in Zed?

There are two paths. In the UI, open Settings then AI then MCP Servers (or run agent: open settings), click Add Server, and choose Add Remote Server. To edit JSON instead, run zed: open settings file and add a context_servers block with tempreon and just the url.

Zed Setup — Docs | Tempreon™

Q: Tempreon's tools appear in Zed's own agent but not in Claude Code running inside Zed. Why?

This is a known Zed issue, still open as of October 2026. When you drive an external agent inside Zed through ACP, such as Claude Code in the Agent Panel, tools from OAuth-authenticated servers like Tempreon may not appear, though Zed's own agent is unaffected. The fix is to connect Tempreon directly in that external tool instead.

Overview

Zed is a fast, free, open-source editor with a built-in AI agent. Add Tempreon as a context server and Zed's agent loads your Core Imprint, searches your Knowledge Vault, and remembers what it learns, across every tool you use.

Zed is one of the cleanest MCP setups around: one settings block, no headers, no keys. Zed handles the OAuth flow, stores your tokens in the system keychain, and refreshes them automatically. MCP isn't gated by any plan, and it works on macOS, Linux, and Windows.

Quick path: Settings → AI → MCP Servers → Add Server → Add Remote Server (or drop a context_servers block in your settings file) → Authenticate → approve in the browser.

Prerequisites

Zed v0.230.0 or later, the first stable release with OAuth for remote MCP servers (free and open source on macOS, Linux, and Windows). Current releases include later OAuth fixes, so update if sign-in fails
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

Two equivalent paths:

From the UI: open Settings → AI → MCP Servers (or run agent: open settings, also in the Agent Panel's top-right menu), click Add Server, and choose Add Remote Server. Enter tempreon as the name and the URL below.
From settings.json: open your settings file (Cmd+Alt+, / Ctrl+Alt+,, or the zed: open settings file command) and add:

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

Just the url — no headers, no tokens. Leaving the auth fields empty is what tells Zed to run the standard MCP OAuth flow.

2. Authorize the connection

When the server needs sign-in, Zed shows an Authenticate button for it (the Add Remote Server form runs this step inline). Click it and a browser tab opens to Tempreon's consent screen. Sign in to your Tempreon account, review the request, and approve. Zed stores the tokens in your system keychain and refreshes them automatically — you shouldn't need to re-authorize.

3. Confirm the tools are active

Settings hot-reload, so there's no restart. Open Settings → AI → MCP Servers and check the dot next to the server: green, with the tooltip "Server is active", means it's connected. Then ask the agent "What Tempreon tools do you have access to?" If it answers with a list, the Bridge is live.

Troubleshooting

Connection fails immediately. The URL must end in /mcp with no trailing slash: https://api.tempreon.com/functions/v1/tempreon-mcp/mcp.

Tools work in Zed's agent but not in an external agent. If you drive an external agent inside Zed via ACP (for example, Claude Code in the Agent Panel), tools from OAuth-authenticated servers may not appear — a known Zed issue, still open as of October 2026. Zed forwards its configured MCP servers to external agents over ACP, but OAuth-authenticated servers may not come through. Zed's own agent is unaffected; for the external agent, connect Tempreon in that tool directly (see Claude Code).

OAuth prompt never appears. Confirm the server entry has no configured Authorization header — Zed's docs scope the OAuth prompt to servers without one, so supplying it makes Zed skip the flow. Remove it, save, and reconnect.

Server shows an error state. Zed's settings hot-reload on save; fix the JSON (a stray comma is the usual cause) and the server reconnects on its own.

Also connect: VS Code · JetBrains IDEs · Cursor

Try saying...

"Start my session." — triggers session_start to load your Core Imprint
"Search my knowledge base for the error-handling conventions we agreed on." — exercises knowledge retrieval end-to-end
"Remember that I prefer small, single-purpose commits." — stores a preference for every future session