Where do I add the Tempreon server in Zed?

There are two equivalent paths. In the UI, open the Agent Panel and use its settings menu to add a remote MCP server, which is also reachable via Settings then AI then MCP Servers. From settings.json, open your settings with Cmd+comma or the zed: open settings command and add a context_servers block with tempreon and just the url.

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

This is a known Zed issue as of July 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.

Zed Setup — Docs | Tempreon™

Q: How does authorizing Tempreon work in Zed?

Zed starts the OAuth flow as soon as the server connects, opening a browser tab to Tempreon's consent screen where you sign in and approve. It then stores your tokens in the system keychain and refreshes them automatically, so you should not need to authorize again. Leaving the auth fields empty in your settings is what tells Zed to run this flow.

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: Agent Panel → add a remote MCP server (or drop a context_servers block in settings.json) → approve in the browser.

Prerequisites

Zed installed (any recent version; free and open source on macOS, Linux, and Windows)
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 the Agent Panel, then use its settings menu to add a remote MCP server (also reachable via Settings → AI → MCP Servers). Enter tempreon as the name and the URL below.
From settings.json: open your settings (Cmd+, / Ctrl+,, or the zed: open settings 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

Zed prompts the OAuth flow as soon as it connects: 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. Check the server's status in the Agent Panel (it should show as 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 as of July 2026. 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