# Prodege MCP connector

The Prodege connector brings your panelists, surveys, vendor surveys, screening questions, and eligibility checks into Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent, so your team can ask about panel activity in plain language and keep panelist records current.

Source: https://elaichi.ai/connectors/prodege/

## Facts

| | |
| --- | --- |
| Application | Prodege |
| Category | Survey |
| AI tools | 11 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Prodege is connected

- List Prodege surveys live in Germany this week.
- Check eligibility for panelist 48213 across open surveys.
- Which Prodege questions appear in our screener library?

## Connect Prodege in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Prodege.
2. Optionally set Share with, then press Connect.
3. Paste a Prodege API key. One person generates a token in Prodege and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Prodege tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Prodege MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Prodege MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Prodege MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Prodege MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Prodege MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Prodege to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Prodege tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Prodege through Elaichi

### Find surveys a panelist can take

Research. Ask which open surveys a specific panelist qualifies for before you reach out, so you only send invitations they can actually complete.

### Add a new panelist after recruitment

Panel operations. Create the panelist record as soon as someone joins the panel, with their country and profile details filled in from the start.

### Update a panelist profile after a change

Panel operations. When a panelist moves, changes email, or updates their household details, catch the record up without opening Prodege.

### Review the current survey inventory

Insights. Pull the list of live Prodege surveys and vendor surveys to see what fieldwork is running and what is available to fill.

### Check eligibility across many surveys

Insights. Run one eligibility check for a panelist against several surveys at once and see which ones they can be routed to.

### See which countries and questions are in use

Marketing. List the countries Prodege supports and the screening questions on file to plan a campaign for a new market or audience.

## Elaichi vs Zapier MCP vs Composio for Prodege

All three can connect Prodege to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Prodege tools | Allow or restrict single Prodege tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Prodege call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Prodege to Claude?

Connect Prodege in Elaichi first, where you paste your Prodege API key when prompted. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in as yourself and Prodege appears alongside your other connected applications.

### Does Prodege work with ChatGPT and Cursor as well as Claude?

Yes. Once Prodege is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Prodege once and every client your team uses can reach it.

### What can an AI agent actually do with my Prodege data?

With Prodege connected, an agent can look up panelists, add a new panelist, and update an existing panelist's details. It can list your surveys and vendor surveys, check whether a panelist is eligible for one survey or several at once, and show which surveys a given panelist has. It can also list the supported countries and the screening questions on file.

### Does connecting Prodege give the AI access to my whole panel?

No. Every call to Prodege runs under the API key and account of the person who connected it, so the agent sees only what that account can see in Prodege. Elaichi can narrow that further by restricting actions for certain roles, but it can never grant more than the underlying Prodege account already has.

### Can my team share one Prodege connection?

Yes. One person connects Prodege in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every Prodege action in the audit log is tied to the person who took it, not to a shared account.

### Can I stop an agent from changing panelist records in Prodege?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Prodege surveys and panelists while restricting the ability to create or update a panelist. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.

### What happens to a Prodege connection when someone leaves?

Offboarding a person in Elaichi ends their access to Prodege at once, across every client they used. If they had shared a Prodege connection with a team, it keeps working for everyone else. Disconnecting Prodege once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at the same time.

### Does the Prodege MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Prodege is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Prodege?

Yes. Both let Claude, ChatGPT or Cursor use Prodege. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Prodege call.

### How is Elaichi different from Composio for Prodege?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Prodege: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 11 Prodege tools

Every tool below is callable through https://api.elaichi.ai/mcp once Prodege is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Prodege request time offset** (List). Look up the time difference between your server and Prodege's server in milliseconds, used to validate authenticated requests. Returns: return_status, request_time_offset, result. Required: client_time.
- **List all Prodege countries** (List). List countries supported by Prodege. Returns country records with upstream-defined fields. Required: request_date, signature.
- **List all Prodege questions** (List). List Prodege qualification questions available for a supported country. Returns: question_id, question_type, question_name, question_text, options. Required: country_id, request_date.
- **List all Prodege panelists** (List). Look up a Prodege panelist's profile and demographic data by vpid. Returns: vpid, country_id, data, return_status. Required: vpid, request_date.
- **Create a Prodege panelist** (Create). Register a new panelist in Prodege for survey targeting. Should only be called once per panelist. Returns: return_status, surveys. Required: apik, request_date, signature, vpid, country_id, profile.
- **Update a Prodege panelist by ID** (Update). Update an existing Prodege panelist's profile. Only the supplied demographic data changes; other data remains unchanged. Returns: return_status, surveys. Required: apik, request_date, signature, vpid, country_id, profile.
- **List all Prodege vendor surveys** (List). List Prodege vendor surveys available to a supplier. Returns each survey's projectid, project_name, surveyurl, cpi, loi, country_code, quotas, and eligibility settings. Required: request_date, signature.
- **List all Prodege surveys** (List). Get all available details about a Prodege survey by project_id. Returns survey details including project_name, projectid, country_code, surveyurl, quotas, and available. Required: project_id, request_date.
- **Prodege surveys check eligibility** (Action). Check if a Prodege panelist is eligible for a specific survey. Returns: result, return_status. Required: ip, useragent, vpid, project_id, request_date.
- **Prodege surveys check multi eligibility** (Action). Check if a Prodege panelist is eligible for up to 100 surveys at once. Returns: invalid_project_ids, eligible_project_ids, not_eligible_project_ids, return_status. Required: ip, useragent, vpid, multi_project_ids, request_date.
- **List all Prodege panelist surveys** (List). List eligible Prodege surveys for a panelist. Returns survey objects with projectid, project_name, surveyurl, cpi, loi, max_completes, and max_clicks_settings. Required: vpid, useragent, ip, request_date, signature.
