# Prodege MCP connector

The Prodege connector brings your panelists, surveys, vendor surveys, screening questions, and eligibility checks into Claude, ChatGPT, Cursor, 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 |
| Needs your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | Yes |

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

## Connect Prodege to 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.

## Connect Prodege to 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 today. The plugin directory lives at chatgpt.com/plugins.

## Connect Prodege to 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.

## 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

Only Read is granted by default, which is not enough to call a Prodege tool. 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. Grant Read and Run tools. Think hard before granting Delete, which reaches into 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.

## 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, 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 hiding actions or restricting them to certain teams, 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 blocking the ability to create or update a panelist. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.

### 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, and every other client at the same time.

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