AI and MCP

How to connect Zed to SpendixAI with MCP

Connect Zed to SpendixAI with a context_servers entry. Zed runs the OAuth sign-in itself; tool_permissions keep every call behind a confirmation.

Editorial illustration for How to connect Zed to SpendixAI with MCP

Zed's setup is a single block in its settings file. If a remote server entry has no Authorization header, Zed starts the standard MCP sign-in on its own, so SpendixAI needs no key or secret.

Requirements

  • Zed with its Agent Panel. The documentation we read states no plan requirement.
  • A SpendixAI account that signs in with Google. SpendixAI is the expense tracker we build, and this guide was checked against Zed's documentation in November 2026.
  • The server address from Developer → MCP connections in SpendixAI.

Two ways to add the server

Through the interface, open Zed's settings, go to AI, then MCP Servers, choose Add Server and then 'Add Remote Server'. You can also run the agent: open settings command and look for MCP Servers. Either way Zed writes the result into your settings file, which you can open with the zed: open settings file command.

By hand, add a context_servers object to settings.json. Inside it, create an entry named spendixai with one field, url, set to <your SpendixAI server address>. Do not add a headers field with a token. A bearer token is how Zed supports token-based servers, but for SpendixAI the browser sign-in is cleaner and can be revoked.

Signing in

  1. Save the entry. Zed starts the OAuth flow because there is no Authorization header.
  2. Your browser opens on a SpendixAI consent screen.
  3. Sign in with Google and choose the workspace.
  4. Pick the Read only preset, which SpendixAI recommends, and approve.
  5. Return to the Agent Panel and ask a first question.

Zed's documentation describes no static OAuth client option. SpendixAI does not need one, since clients register themselves through dynamic client registration.

Run a short trial first. Ask one read-only question, then look at the confirmation Zed shows before the call. Note which tool it wants to use. If a name suggests that something would be created or changed in your records, decline it and rephrase the question. Confirmations are the cheapest safety net you have, and they cost only a click.

Tool permissions: the setting that matters

Zed's agent.tool_permissions.default can be set to confirm, allow or deny, and confirm is the default. Keep it as confirm for a finance connection. Rules for individual tools use a key of the form mcp, then the server name, then the tool name, joined by colons. That lets you deny a write-type tool outright while leaving reads on confirm. The setting names apply from Zed 0.224.0; earlier versions used agent.always_allow_tool_actions instead.

Setting valueEffectOur suggestion
confirm (default)Zed asks before each tool callKeep for SpendixAI
allowTools run without askingAvoid with finance data
denyTools are refusedUse per tool for anything that writes

What SpendixAI limits on its own side

Read only lets an assistant view transactions and reports. Read and add can also create transactions and upload documents. Full access also touches categorisation rules and insights. Billing and member settings are never offered to an assistant, and what it can do is capped by your own workspace role, checked again on every call.

What to ask first

  • What did I spend last month?
  • Which category has the biggest share of my spending this year?
  • Show my largest transactions from the last thirty days.

Check any figure you plan to act on, tax numbers above all, against the matching SpendixAI report. The answer comes from whichever model you have configured in Zed, under that provider's terms, so SpendixAI cannot vouch for how it words or rounds a result.

Zed is an editor first, so it is easy to leave a finance question sitting in a thread that also contains source code. Start a fresh thread for spending questions and close it when you are done.

What we could not confirm

We could not confirm the minimum Zed version that supports remote MCP with OAuth. If the Add Remote Server option is missing, update Zed first. To end access later, disconnect Zed on the Developer → MCP connections page.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports