Skip to content

VS Code appointment next_event

How to: VS Code appointment next_event

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

Add appointment to VS Code

  1. 01

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

{
  "servers": {
    "appointment": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/appointment"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that appointment'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

appointment will not start until these are set, so next_event never becomes available.

  • MCP_LICENSE_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.