Rally MCP connector
The Rally connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, or any MCP client search your studies, build screeners, check recruiting, and manage participants in Rally, with each person's own access and every action logged.
- Connects over OAuth
- Free 14-day trial
- No credit card
Check recruiting feasibility for 12 enterprise admins in our onboarding study
Working in Rally with Elaichi
-
Search survey connectors
-
Search properties
-
Get consent forms
How to connect Rally to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Rally MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Rally MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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.
Rally MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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.
Rally MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Rally MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Rally to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Rally through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Rally is logged.
-
UX Research
Set up a study before the kickoff
Describe what you want to learn and have a study, screener, and survey drafted in Rally from one of your templates. You review it before anything goes out to participants.
-
Research Ops
Check feasibility before promising a date
Ask whether Rally can recruit enough participants who match your criteria before you commit to a timeline. Once the numbers look right, start recruiting from the same conversation.
-
Product
Reuse past participants for a new question
Search people in Rally by what they took part in before and add the right ones to the new study, without rebuilding a list by hand.
-
Design
Build an external panel audience
Say who you need to hear from and have the external panel targeting options in Rally searched, the audience built, and the launch review handed to you to sign off.
-
Marketing
Import a customer list for a survey
Hand over a list of customers and have them imported into Rally as people, then added to the right study ready for the screener.
-
Customer Insights
Prepare for an interview in one ask
Before a session, pull the participant's record from Rally, which studies they have joined, and the consent forms attached, so nothing is missed on the call.
Try asking
- “Check recruiting feasibility for 12 enterprise admins in our onboarding study”
- “Add past participants who mentioned pricing to the checkout study”
- “Draft a screener for the mobile navigation study from our usual template”
What connecting Rally gets you
6 screens from Elaichi, each doing one job for your Rally account.
Ask Elaichi to work across your apps.
Check recruiting feasibility for 12 enterprise admins in our onboarding study
Add past participants who mentioned pricing to the checkout study
Draft a screener for the mobile navigation study from our usual template
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about studies and get live answers.
Three starter prompts pull real studies, participants, and recruiting status from Rally.
Copy the endpoint
AI apps
One Rally endpoint works in every MCP client.
Claude, ChatGPT, Cursor, Microsoft Copilot, and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.
Tool catalog
68 Rally tools, ready without any code.
Studies, screeners, surveys, recruiting, panels, and people, covered before anyone writes a line.
Toolboxes
Every team gets its own Rally toolbox.
Research Ops recruits, Design builds screeners, Marketing imports people, each from a scoped toolbox.
Shared connections
Share one Rally connection, never a credential.
One researcher connects Rally once, then teammates work through it without seeing a secret.
Audit log
Every Rally action names who did it.
When, who, what happened, and which study or participant, in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Rally digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch studies
Rally
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Rally
Queued
Workflows
A schedule starts recruiting work, you approve it.
New Rally participants are fetched, grouped, drafted into a digest, approved, then posted back.
Rally health
Refreshed 4 minutes ago · every 15 minutes · from the studies collection
Studies
1,284 ↓ 12%
Participants
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Studies created
Last 14 days
By team
Share of activity
UX Research 34%
Research Ops 27%
Product 21%
Design 18%
Collections and dashboards
Rally recruiting numbers, computed without a model.
Four metrics, fourteen days of studies created, and a breakdown by team, refreshed on schedule.
Why connect Rally's MCP server through Elaichi
Rally builds and runs this MCP server. Elaichi sits in front of it, so Rally's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Rally's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Rally's tools at the same Elaichi address as every other connected app. Nobody adds Rally's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Rally sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Rally's server. By default, a tool Rally does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Rally
Rally builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Rally team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Rally
All three can connect Rally 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.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Rally tools | Allow or restrict single Rally 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 Rally 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Rally tools for your AI agents
68 tools are ready to call through Elaichi's MCP endpoint the moment you connect Rally, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Rally builds and runs these tools.
No tools match your search.
Questions, answered
How do I connect Rally to Claude?
Connect Rally in Elaichi first: pick Rally from the catalog and sign in to your Rally account over OAuth, with no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and Rally is available in your next conversation.
Does Rally work with ChatGPT and Cursor as well as Claude?
Yes. Rally is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent. There is nothing to set up again for each client.
What can an AI agent actually do with my Rally data?
An agent can search your Rally studies and templates, draft a study, screener, or survey, check whether a recruit is feasible, start recruiting, and build an external panel audience for you to review. It can also search people and participants, add or remove them from a study, import a list, and pull up consent forms. Short, specific asks such as "find participants from the checkout study" work better in Rally than long paragraphs.
Does connecting Rally give the AI access to every study and participant?
No. Every call into Rally runs as the person who signed in, so the agent sees the studies, participants, and people that person already has access to in Rally. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what Rally itself allows.
Can I stop an agent from removing participants or changing studies in Rally?
Yes. Restrictions in Elaichi work per action, so you can allow searching studies and people in Rally while restricting removing participants, starting recruiting, or importing lists. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, or any other client cannot run it, whatever the prompt says.
What happens to a Rally connection when someone leaves?
Offboarding a person in Elaichi ends their access to Rally through every client at once. A Rally connection shared with a team keeps working for everyone else. If you disconnect Rally in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client in one step.
Does the Rally MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Rally 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 Rally?
Yes. Both let Claude, ChatGPT or Cursor use Rally. 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 Rally call.
How is Elaichi different from Composio for Rally?
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 Rally: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Rally in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot