Skip to content

VS Code Chronary update_agent

How to: VS Code Chronary update_agent

client:VS Code transport:streamable-http tool:update_agent

Add Chronary to VS Code

  1. 01

    Open .vscode/mcp.json and merge this in. Keep any servers already there.

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://api.chronary.ai/mcp"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

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

  3. 04

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

Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs

Set these first

Chronary will not start until these are set, so update_agent never becomes available.

  • CHRONARY_API_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.