Use NeetoCal in VS Code

Check requirements

• VS Code installed on your computer.
• A NeetoCal account.

Connect NeetoCal to VS Code

You need VS Code 1.99 or later, with GitHub Copilot in Agent mode. Create .vscode/mcp.json in your workspace. Use servers, not mcpServers:

{
  "servers": {
    "neetocal": {
      "type": "http",
      "url": "https://connect.neetocal.com/mcp/messages"
    }
  }
}

Sign in to NeetoCal when VS Code asks.

Then ask in Copilot Chat. VS Code asks before it runs a command, but not before it calls a NeetoCal tool:

Connect with an API key

An API key is not tied to a person. Every tool call reaches the whole workspace, and role checks do not run. Use a key for automation that must see every booking. Do not use one on a machine where the person should see only their own bookings.

It is the same key the REST API uses. Learn how to generate your API key. Create it in the workspace you want the assistant to reach. Every client sends it in this header:

Authorization: Bearer YOUR_API_KEY

Create .vscode/mcp.json in your workspace. VS Code asks for the key the first time the server is used. Never paste the key into this file, because it lives in your project and can end up in a commit.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "neetocal-api-key",
      "description": "NeetoCal API key",
      "password": true
    }
  ],
  "servers": {
    "neetocal": {
      "type": "http",
      "url": "https://connect.neetocal.com/mcp/messages",
      "headers": {
        "Authorization": "Bearer ${input:neetocal-api-key}"
      }
    }
  }
}

VS Code's Copilot agent does not read servers that use ${input:...}. To use the key there, put the server in .mcp.json at the root of your workspace and read the key from an environment variable:

{
  "mcpServers": {
    "neetocal": {
      "type": "http",
      "url": "https://connect.neetocal.com/mcp/messages",
      "headers": {
        "Authorization": "Bearer ${NEETOCAL_API_KEY}"
      }
    }
  }
}

Set NEETOCAL_API_KEY in the environment that starts VS Code. The sign-in setup above works in both the Local and Copilot agents.

Try these prompts

Look things up:

What NeetoCal bookings do I have this week?

Show me open slots for my Product Demo meeting on May 15 in America/New_York.

List the meetings I host.

Book outside your working hours. Only a host of the meeting or an admin can do this:

Book Oliver Smith into my demo meeting on May 15 at 8pm America/New_York, even though it's outside my hours.

Set up a meeting and your calendar:

Create a 30-minute meeting called Product Demo, hosted by me, over Zoom.

Add bookings of my Product Demo meeting to my Work Google calendar, and check only that calendar for conflicts.

Troubleshooting

VS Code never offers the tools

MCP needs VS Code 1.99 or later with GitHub Copilot in Agent mode. It is not available in Ask or Edit mode. Check the version, switch to Agent mode, and confirm .vscode/mcp.json is in the workspace you have open. With an API key, VS Code asks for the key the first time you use the server.

Your AI assistant shows no NeetoCal tools

Restart the client first. Every client reads its MCP config at startup. On Claude or ChatGPT, confirm that you added the connector and finished the sign-in. In ChatGPT, the plugin is created only after you tick I understand and want to continue.

On clients that read a config file, check these:

1. The config key. Claude Code, Cursor, Devin, Antigravity, and Antigravity CLI use mcpServers. VS Code uses servers. Codex uses a [mcp_servers.<name>] section in TOML. A server under the wrong key is ignored silently.
2. The URL key. Antigravity and Antigravity CLI expect serverUrl. Claude Code, Codex, Cursor, Devin, and VS Code expect url.
3. The endpoint. It is https://connect.neetocal.com/mcp/messages, with no trailing slash.
4. The syntax. In JSON, a trailing comma or an unclosed brace makes the whole file unreadable.

The connection is refused or unauthorized

With an API key, the header must read Bearer YOUR_API_KEY, with the word Bearer and one space before the key. Check that the key is not revoked and belongs to the workspace you expect. A key from one workspace does not work in another. With OAuth, remove the connector and add it again to start the sign-in over.

More fixes are in the NeetoCal MCP troubleshooting guide.

Use NeetoCal in other AI assistants

Prefer the terminal? The NeetoCal CLI reaches the same data from your shell, your scripts and your coding agent.