Claude Code setup

Connect ziptie.ai to Claude Code (the Anthropic CLI) so Claude can query your project data while helping you build automations.

Prerequisites

• Claude Code installed and authenticated.
• 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

Add the ziptie.ai MCP server to Claude Code via the CLI. The URL is the positional argument after the server name:

claude mcp add --transport http ziptie https://api.ziptie.ai/mcp \
  --header "Authorization: Bearer zt_live_<your-token>"

Replace zt_live_<your-token> with your actual token value. Pass --scope user to register the server for every project, --scope project to commit it to the repo's .mcp.json, or omit --scope for the default local-to-this-project registration.

To configure it as a project-scoped server by editing the file directly, create or edit .mcp.json in the repo root:

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

.mcp.json is checked in to the repo when you want the whole team to share the same server set; keep the token out of it (use an env var indirection or the CLI form above with --scope user). If a token does get committed, revoke it and issue a replacement rather than rewriting history; the MCP overview covers expiry choices, revocation, and the 10-active-token cap (per project for project tokens, per workspace for workspace tokens).

Verify the connection

Start a Claude Code session and run:

claude

Then ask:

"List my ziptie.ai prompts for project PROJECT_ID"

Claude will call the list_prompts tool and display the results inline.

Using in agent mode

Claude Code's agent mode can chain multiple ziptie.ai tool calls. For example:

"Get the dashboard overview for project PROJECT_ID, then list the URLs sorted by citation rate ascending so I can see which pages are cited least."

Troubleshooting

-32001 with data.code TOKEN_EXPIRED or TOKEN_REVOKED The token is expired or revoked. Create a new one under Project Settings (or Workspace Settings > API & MCP access for a workspace token) and update the Authorization header value. The reply arrives at HTTP 200 like every MCP error, so a client that only logs status codes will show this as a successful call with no tools.

-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. Both are decided before any tool runs, so even initialize fails and the server never registers. Fix it in workspace billing settings; the token itself does not need replacing. See MCP overview.

Tool not found Ensure the MCP server URL is exactly https://api.ziptie.ai/mcp with no trailing slash. Run claude mcp list to confirm the server is registered.