> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/integrations/mcp/mcp-claude.md). # Connect to Claude Connect Zigpoll to Claude (Claude Desktop and Claude Code) with MCP so you can analyze survey responses and build surveys in plain English. Connect your Zigpoll surveys to **Claude** using the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/). Once connected, Claude can read your survey responses, run analytics, and even create surveys — just ask in plain English. No coding required. This guide covers both **Claude Desktop** and **Claude Code (CLI)**. For other AI clients, see the [MCP overview](/integrations/mcp.md). {% hint style="info" %} **How authorization works:** there's no API key to copy or paste. When you connect, Claude opens a browser window to authorize with Zigpoll. If you're already logged into Zigpoll in that browser, authorization completes automatically — you'll briefly see a loading screen, then be returned to Claude. If you're not logged in, sign in with your email and password, Google, or Shopify. Claude then stores a secure token, so you only do this once. {% endhint %} {% hint style="warning" %} **Plan requirement:** MCP uses the Zigpoll API, which is included on the **Premium** plan and higher. {% endhint %} ## Claude Desktop (and claude.ai) Zigpoll is a remote MCP server, so you add it as a **custom connector**, not by editing `claude_desktop_config.json`. That file is for servers that run on your own computer, and a `url` entry there does not connect. 1. In Claude, open **Settings → Connectors**. 2. Click **Add custom connector**. 3. Name it `Zigpoll` and enter the server URL: ``` https://mcp.zigpoll.com/mcp ``` 4. Click **Add**, then **Connect**. A browser window opens to authorize with Zigpoll. Sign into Zigpoll if prompted — if you're already logged in, authorization completes automatically. 5. In a chat, make sure the Zigpoll connector is turned on in the tools menu. Connectors you add on claude.ai are also available in Claude Desktop when you're signed into the same Claude account. On Team and Enterprise plans, an owner may need to allow custom connectors first. Menu names can change as Claude updates. ## Claude Code (CLI) 1. Add the server from your terminal: ```bash claude mcp add --transport http zigpoll https://mcp.zigpoll.com/mcp ``` 2. Run `/mcp` inside Claude Code and select **zigpoll** to authenticate. 3. A browser window opens — sign into Zigpoll if prompted (authorization completes automatically if you're already logged in). {% hint style="info" %} **How authentication works:** `mcp.zigpoll.com` uses a standard browser-based OAuth login tied to your Zigpoll account. Setting a static `Authorization: Bearer ` header will not work — your login is exchanged for a secure token through the browser authorization flow. {% endhint %} ## Verify Your Connection Ask Claude: > "List my Zigpoll accounts" or > "Show me my recent surveys" Claude will use the Zigpoll tools automatically to fetch your data. ## Example prompts * "Summarize the responses for my NPS survey from the last 30 days" * "What devices and browsers are my respondents using?" * "How do NPS scores correlate with purchase type?" * "Create a new post-purchase survey for my account" For the full list of tools and more examples, see the [MCP overview](/integrations/mcp.md). For ideas on what to build, see [Ideas for Using Zigpoll MCP](/tutorials/zigpoll-mcp-use-cases.md). ## Troubleshooting * **I edited `claude_desktop_config.json` and nothing happens** — remove the Zigpoll entry from that file and add Zigpoll as a custom connector instead (see Claude Desktop above). * **No authorization window appears** — run `/mcp` in Claude Code, or click **Connect** on the Zigpoll connector in Claude's **Settings → Connectors**. * **"Authorization expired"** — the Zigpoll authorization page is valid for 10 minutes and works only once. Close it and click **Connect** again in Claude. * **"The requesting application is no longer registered"** or another redirect error — remove the Zigpoll connector (or run `claude mcp remove zigpoll` in Claude Code), add it again, and reconnect. * **"This account's plan does not include API access"** — the Zigpoll account is on a plan without API access. Upgrade to **Premium** or higher. * **Tools not appearing** — restart Claude after adding the server, and check that the connector is turned on for the chat. * **Connected to the wrong Zigpoll account** — authorization uses whichever Zigpoll login is signed in to your browser. Log in as the correct user at [app.zigpoll.com](https://app.zigpoll.com), then disconnect and reconnect the server. * **Authentication errors** — the connection authenticates with an API key labeled "MCP" that Zigpoll creates automatically. If it was revoked under **Integrations → API Keys**, disconnect and reconnect to issue a new one. If none of these help, email with the exact error and the client you're using. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.zigpoll.com/integrations/mcp/mcp-claude.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.