> 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-manus.md). # Connect to Manus Connect Zigpoll to Manus as a custom MCP server so the agent can analyze your survey data and create surveys in natural language. Connect your Zigpoll surveys to **Manus** as a custom MCP server using the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/). Once connected, Manus can read your survey responses, run analytics, and create surveys — just ask in plain English. For other AI clients, see the [MCP overview](/integrations/mcp.md). {% hint style="warning" %} **Plan requirement:** MCP uses the Zigpoll API, which is included on the **Premium** plan and higher. {% endhint %} {% hint style="info" %} Manus connects to Zigpoll through its **Custom MCP Servers** feature. Menu labels evolve as Manus updates — "Integrations", "Connectors", and "Custom MCP Servers" refer to the same area. {% endhint %} {% hint style="info" %} **How authorization works:** there's no API key to copy or paste. When Manus first uses a Zigpoll tool, it opens a browser window to authorize with Zigpoll. If you're already logged into Zigpoll in that browser, authorization completes automatically; if not, sign in with your email and password, Google, or Shopify. Manus then stores a secure token, so you only do this once. {% endhint %} ## Step 1: Open Custom MCP Servers 1. In Manus, open **Settings → Integrations → Custom MCP Servers**. 2. Click **Add Server**. ## Step 2: Add the Zigpoll server Enter the server details: * **Server name:** `Zigpoll` * **Server URL:** `https://mcp.zigpoll.com/mcp` * **Authentication:** leave blank (or choose **OAuth** if offered) Save. Manus verifies the connection and loads Zigpoll's available tools. {% hint style="warning" %} Don't enter an API key into the authentication or custom-header field. `mcp.zigpoll.com` uses a browser-based OAuth login tied to your Zigpoll account and does not accept a static API-key or `Authorization: Bearer` header. Your login is exchanged for a secure token in the next step. {% endhint %} ## Step 3: Authorize with Zigpoll The first time Manus uses a Zigpoll tool, it pauses and prompts you to log in. A browser window opens to authorize with Zigpoll. If you're already logged into Zigpoll, authorization completes automatically after a brief loading screen. Otherwise, sign in with your email and password, Google, or Shopify. Manus stays connected for future sessions. ## Step 4: Use it Ask Manus to work with your survey data. Being explicit helps it pick the right tool, e.g.: > "Use Zigpoll to list my accounts" > "Use Zigpoll to summarize the responses from my NPS survey" ## Example prompts * "List all my surveys and their response counts" * "Where are my survey respondents located?" * "Compare order values for each answer on my attribution question" * "Create a new customer satisfaction survey" 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 * **Server won't verify or no tools load** — confirm the URL is exactly `https://mcp.zigpoll.com/mcp` and that the authentication field is left blank so Manus uses the OAuth login flow. * **No authorization window appears** — trigger a Zigpoll tool in a chat to start the login, or reconnect the server from **Settings → Integrations → Custom MCP Servers**. * **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 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**, reconnect the server to issue a new one. A static API-key header is not supported; authentication must go through the browser login flow. * **"This account's plan does not include API access"** — the Zigpoll account is on a plan without API access. Upgrade to **Premium** or higher. --- # 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-manus.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.