VS Code setup

Connect ziptie.ai to VS Code (with GitHub Copilot or another MCP-capable extension) so the AI can query your project data while you code.

Prerequisites

VS Code 1.102 or newer (MCP support is generally available in Copilot Chat's agent mode). Third-party MCP-capable extensions (Continue, Cline, etc.) read their own config and are not covered here.
A ziptie.ai API token with at least read scope. Create one under Project Settings > API & MCP access. The workspace needs the paid API & MCP access add-on active first - without it the create button is disabled and existing tokens are rejected with API_ADDON_INACTIVE. See authentication.

Configuration

VS Code reads MCP servers from a dedicated mcp.json file (not from settings.json) under the top-level key servers. Create one of:

Workspace scope - .vscode/mcp.json in the project root. Shared with collaborators; keep the token out of source control. If one is committed by accident, revoke it and issue a replacement - the MCP overview covers expiry choices, revocation, and the 10-active-token cap (per project for project tokens, per workspace for workspace tokens).
User scope - run MCP: Open User Configuration from the command palette (Ctrl+Shift+P) to open mcp.json in your user profile.

Paste:

{
  "servers": {
    "ziptie": {
      "type": "http",
      "url": "https://api.ziptie.ai/mcp",
      "headers": {
        "Authorization": "Bearer zt_live_<your-token>"
      }
    }
  }
}

Replace zt_live_<your-token> with your actual token value. To avoid committing the token, use an input prompt:

{
  "inputs": [
    {"id": "ziptie_token", "type": "promptString", "password": true,
     "description": "ziptie.ai API token"}
  ],
  "servers": {
    "ziptie": {
      "type": "http",
      "url": "https://api.ziptie.ai/mcp",
      "headers": {"Authorization": "Bearer ${input:ziptie_token}"}
    }
  }
}

Start the server

After saving mcp.json, VS Code surfaces a Start code lens above the server entry. Click it (or run MCP: List Servers > ziptie > Start) to register the server. The ziptie.ai tools become available to Copilot Chat in agent mode.

Verify the connection

Open the Copilot Chat panel (or your MCP extension's interface) and ask:

"List my ziptie.ai prompts for project PROJECT_ID"

The extension will call the list_prompts tool and stream the results.

Troubleshooting

-32001 Unauthorized The token is expired or revoked. Create a new token and update the Authorization header in your settings. Read error.data.code for which of those it is; the HTTP status is 200 either way.

-32004 with data.code API_ADDON_INACTIVE or PAYMENT_REQUIRED The token is valid; the workspace is not entitled. API_ADDON_INACTIVE means the API & MCP access add-on is off - it lapsed, or the subscription was cancelled - and PAYMENT_REQUIRED means the subscription payment is overdue. Entitlement is checked before any tool runs, so the server fails to start and no tools reach Copilot Chat. Fix it in workspace billing settings; the token does not need replacing. See MCP overview.

Server not connecting Confirm the file is named mcp.json (not settings.json) and the root key is servers (not mcpServers). Third-party MCP-capable extensions (Continue, etc.) read their own config; check that extension's docs if you are not using Copilot Chat's built-in MCP client.

Tools visible but calls error The token scope may be insufficient for the requested tool. Write operations require write scope; delete operations require admin scope.