> 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 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="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 %}

## Prerequisite: get your Zigpoll API key

1. Log into your [Zigpoll dashboard](https://app.zigpoll.com).
2. Go to **Settings → Manage Integrations**.
3. Scroll to **API Key**, click **Add Key** under **Private Keys**, label it "Manus", and copy it.

{% hint style="info" %}
You won't paste this key into the Manus connection form. When Manus first uses a Zigpoll tool, it opens a browser window to authorize with Zigpoll, and you paste the key on the Zigpoll authorization page. 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 paste your API key into the authentication or custom-header field. `mcp.zigpoll.com` uses a browser-based OAuth login, and a static API-key or `Authorization: Bearer` header is not accepted — the key is exchanged for a token through the authorization page 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 the Zigpoll authorization page — paste the API key from the prerequisite step and click **Authorize**. 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**.
* **Authentication errors** — a static API-key header is not supported; the key must be entered on the browser authorization page. Make sure the key hasn't been revoked — you can regenerate one from **Settings → Manage Integrations → API Key**.


---

# 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=<question>&goal=<endgoal>
```

`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.