# Zed: read your AI visibility by topic, from the Agent Panel > For the complete documentation index, see [llms.txt](https://attensira.com/llms.txt). > Every page on this site is also served as Markdown: append `.md` to any URL, or send `Accept: text/markdown`. > Add Attensira to Zed as a remote MCP server with one url entry, sign in through Zed's own OAuth prompt, and read your visibility by topic. - Canonical page: https://attensira.com/integrations/zed - Family: integrations - Last updated: 2026-10-04 - Author: Karl-Gustav Kallasmaa (https://x.com/kallasmaa) - Claims as data: https://attensira.com/claims.json?slug=zed **In short:** Add Attensira to Zed as a remote MCP server: one context_servers entry with the server URL, from Settings → AI → MCP Servers or the settings file. With no Authorization header, Zed runs the MCP OAuth sign-in itself. The Agent Panel can then read your AI visibility by topic, prompt and engine. Older builds need the mcp-remote bridge. ## What it showed on attensira.com (read 2026-10-04) Asked in Zed: "Which topics are we invisible on?" Call: `get_analytics area=topic days=30` On these four topics no answer named us in 30 days. Pricing is the odd one: never named, but our pages are cited in a fifth of its answers. | Row | Value | Note | | --- | --- | --- | | Product category searches | 0 of 769 | 7 prompts | | Audience and use case | 0 of 629 | 6 prompts | | Comparison and alternatives | 0 of 445 | 4 prompts | | Pricing and budget | 0 of 211 | named in none, cited in 43 | _Topics group the prompts a workspace tracks; each count is answers that named us._ ## What can Zed's Agent Panel read? - Read mention and citation rates by topic, prompt and engine, each with its n, from Zed's Agent Panel. - Find the topics where you are cited but never named, which usually means a page is used as a source while a rival gets the recommendation. - Approve or hand off the crew's work from the editor once signed in, like any other client. - Use a key instead, by adding an Authorization header to the entry, on a machine where nobody can open a browser. ## How do I connect Zed? 1. **Add a remote server** In Zed, open Settings → AI → MCP Servers, choose Add Server, then Add Remote Server, and enter https://mcp.attensira.com/mcp. Zed writes a context_servers entry with that url to your settings file. 2. **Sign in when Zed asks** With no Authorization header in the entry, Zed runs the standard MCP OAuth flow. A browser opens; sign in to Attensira and approve the access it asks for. 3. **Watch the indicator** Back in Settings → AI → MCP Servers, the dot next to the server turns green and its tooltip says the server is active. 4. **Check it with get_account** Ask the Agent Panel to call get_account. It lists your workspaces and the platforms really measured. If nothing answers, https://mcp.attensira.com/healthz tells you whether the server is reachable. ## What are the limits in Zed? - How reliably MCP tools get called varies from model to model. Naming the Attensira server in your prompt helps the model pick its tools. - A key in the entry's headers is a credential in your settings file. Keep that file out of shared dotfiles, or use OAuth and leave the headers out. - Topic rates are only as good as the prompts in each topic. A topic with a handful of prompts and few answers swings for reasons that are not yours. ### What did the topic view show on our own workspace? Pricing is the interesting row: never named, yet our pages are a source in about a fifth of its answers. A page models use as a source while recommending someone else is a different brief from a page they never read, and the topic view is where that shows up first. ### How does Zed connect without a bridge? Current Zed builds add remote MCP servers directly: Settings → AI → MCP Servers → Add Server → Add Remote Server, or a `context_servers` entry with a `url` in your settings file. Attensira's server speaks Streamable HTTP at `https://mcp.attensira.com/mcp`, so that one URL is the whole configuration. With no `Authorization` header, Zed runs the standard MCP OAuth flow itself: a browser opens, you sign in and approve, and the tools appear in the Agent Panel. To use a key instead, add `"headers": { "Authorization": "Bearer " }` to the entry. The key then sits in your settings file, so treat that file as a credential. ## FAQ ### Does Zed need the mcp-remote bridge? Not on current builds. Zed connects to remote MCP servers from a url entry. Only an older build that can launch local processes alone needs the bridge. ### How does sign-in work? With no Authorization header in the entry, Zed runs the standard MCP OAuth flow itself. A browser opens, you sign in to Attensira and approve, and the tools appear. ### Can I use an API key instead? Yes. Add "headers": { "Authorization": "Bearer " } to the entry. Leave the headers out and Zed signs you in with OAuth. ### What if my Zed build only offers local servers? Use the bridge, with command npx and args -y, mcp-remote and the server URL. It needs Node.js, runs OAuth itself and caches the token under your home directory. ### The tools are not being called. Is it broken? Check the indicator first; green means the server is active. If it is, name the Attensira server in your prompt, because how reliably tools get called varies by model. ## Sources Each entry below is one claim on this page. `retrieved` is the date the exporter or a human last saw the source say this, and nothing more: it is not a publication date and not a promise of re-verification. `cite` is the anchor on the canonical page where this claim is rendered. ### zed-remote-servers Zed's MCP documentation states that both local and remote MCP servers can be added from Settings → AI → MCP Servers, and shows a remote server configured with a url. - source: https://zed.dev/docs/ai/mcp (zed.dev) - retrieved: 2026-10-04 - cite: https://attensira.com/integrations/zed#claim-zed-remote-servers > You can connect both local and remote MCP servers ### zed-remote-oauth Zed's MCP documentation states that when a remote MCP server has no Authorization header configured, Zed prompts the user to authenticate with the standard MCP OAuth flow. - source: https://zed.dev/docs/ai/mcp (zed.dev) - retrieved: 2026-10-04 - cite: https://attensira.com/integrations/zed#claim-zed-remote-oauth > Zed will prompt you to authenticate yourself against the MCP server using the standard MCP OAuth flow ### zed-server-indicator Zed's MCP documentation states that a correctly running server shows a green indicator next to its name in Settings → AI → MCP Servers. - source: https://zed.dev/docs/ai/mcp (zed.dev) - retrieved: 2026-10-04 - cite: https://attensira.com/integrations/zed#claim-zed-server-indicator > If it’s running correctly, the indicator will be green ### mcp-remote-caches-token Attensira's connect documentation states that the mcp-remote bridge, the path for a client that can only launch local processes, runs the OAuth flow itself, caches the token under the user's home directory and needs Node.js. - source: https://docs.attensira.com/mcp/connect (docs.attensira.com) - retrieved: 2026-10-04 - cite: https://attensira.com/integrations/zed#claim-mcp-remote-caches-token > runs the OAuth flow itself and caches the token under your home directory ### mcp-healthz-check Attensira's MCP overview states that the server publishes an unauthenticated health path that answers without a key. - source: https://docs.attensira.com/mcp/overview (docs.attensira.com) - retrieved: 2026-10-04 - cite: https://attensira.com/integrations/zed#claim-mcp-healthz-check > is unauthenticated and answers without a key, which makes it a useful reachability check when a client is silent about why it failed