Skip to content

Zed monity.ai get_recent_changes

How to: Zed monity.ai get_recent_changes

client:Zed transport:streamable-http tool:get_recent_changes

Add monity.ai to Zed

  1. 01

    Open ~/.config/zed/settings.json and merge this in. Keep any servers already there.

{
  "context_servers": {
    "monity": {
      "url": "https://api.monity.ai/plugins/mcp"
    }
  }
}
  1. 02

    Save the file and restart Zed.

  2. 03

    Ask for something get_recent_changes does. Zed lists the server's tools on connect and calls get_recent_changes itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that monity.ai's identifier in your config matches the one above exactly.

Merge this into your existing settings object — do not replace the file. Zed docs

Set these first

monity.ai will not start until these are set, so get_recent_changes never becomes available.

  • MONITY_API_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 8 November 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.