Cookiy MCP Server for Claude
Cookiy hosted MCP server and cookiy-mcp bootstrap CLI for AI-moderated user research—studies, interviews, recruitment, reports, and quantitative surveys over OAuth streamable HTTP.
Open the source and read safety notes before installing.
Safety notes
- cookiy_create_cue and recruitment tools can incur charges; confirm budgets before approving calls.
- Use cookiy_introduce and cookiy_help to understand workflow state machines before destructive actions.
- OAuth tokens grant persistent Cookiy access until revoked.
- Quantitative and recruitment flows may contact real participants; review scripts before launch.
Privacy notes
- Interview transcripts, participant responses, and billing metadata are processed by Cookiy.
- OAuth credentials remain in the MCP host; do not paste tokens into chat or public issues.
- Research studies may contain PII from participants; follow your organization's data-handling policy.
Prerequisites
- Cookiy account with billing enabled when running paid interviews or recruitment.
- Node.js 18+ for the cookiy-mcp bootstrap CLI from the cookiy-ai/cookiy-skill repository.
- Claude Code, Cursor, Codex, Windsurf, Cline, OpenClaw, or another MCP host with HTTP and OAuth support.
- Network egress allowed to s-api.cookiy.ai, including OAuth discovery endpoints.
Schema details
- Install type
- cli
- Reading time
- 4 min
- Difficulty score
- 35
- Troubleshooting
- Yes
- Breaking changes
- No
- Estimated setup
- 10 minutes
- Difficulty
- intermediate
- Website
- https://cookiy.ai
Full copyable content
{
"mcpServers": {
"cookiy": {
"url": "https://s-api.cookiy.ai/mcp",
"type": "http"
}
}
}About this resource
Overview
Cookiy provides a workflow-aware Model Context Protocol server for AI-moderated user research. Agents create studies, run simulated or live interviews, edit discussion guides, recruit participants, generate insight reports, and optionally launch quantitative surveys through official cookiy_* MCP tools.
The production endpoint is https://s-api.cookiy.ai/mcp, registered as ai.cookiy/cookiy. Installation assets live in cookiy-ai/cookiy-skill with the cookiy-mcp bootstrap CLI.
Features
- Study creation and listing through structured MCP tools.
- AI-moderated interviews with guide editing workflows.
- Participant recruitment and billing-aware checkout tools.
- Report generation, sharing, and balance inspection.
- OAuth 2.1 authentication with resumable headless flows for some clients.
- One-command installer that adds both local skill copies and MCP config.
Use Cases
- Spin up a concept-testing study from a product brief in Claude Code.
- Run simulated interviews before spending recruitment credits.
- Recruit participants matching a screening questionnaire.
- Check account balance before launching a paid study wave.
- Generate and share an insight report link with stakeholders.
Installation
Recommended bootstrap CLI
npx cookiy-mcp --client claudeCode -y
Supported --client values include claudeCode, cursor, vscode, codex, windsurf, cline, openclaw, and manus.
Manual HTTP connector
{
"mcpServers": {
"cookiy": {
"url": "https://s-api.cookiy.ai/mcp",
"type": "http"
}
}
}
OAuth discovery is at https://s-api.cookiy.ai/.well-known/oauth-authorization-server.
Verify connection
After install, ask the agent to call cookiy_introduce to confirm authentication and tool access.
Configuration
{
"mcpServers": {
"cookiy": {
"url": "https://s-api.cookiy.ai/mcp",
"type": "http"
}
}
}
Examples
Create a study
Create a Cookiy study to test onboarding confusion for our mobile banking app.
Run simulated interviews
Run three AI-moderated interviews using the current discussion guide and summarize top friction points.
Recruitment
Recruit five participants who match our screening criteria for a 30-minute remote session.
Security
- Confirm credit costs with
cookiy_balance_getbefore paid recruitment or checkout tools. - Review discussion guides and consent language before contacting real participants.
- Revoke Cookiy OAuth access when offboarding contractors with MCP access.
Troubleshooting
OAuth fails on first connect
Allow network egress to s-api.cookiy.ai and complete the browser or headless OAuth flow your host requires.
Installer did not detect client
Pass --client explicitly, for example npx cookiy-mcp --client cursor -y.
Tool contract errors
Use documented cookiy_* tools only; Cookiy is not a raw REST passthrough.
Claude Cowork network blocks
Enable outbound network access and allow s-api.cookiy.ai in the domain allowlist.
Source citations
Add this badge to your README
How it compares
Cookiy MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Cookiy MCP Server for Claude Cookiy hosted MCP server and cookiy-mcp bootstrap CLI for AI-moderated user research—studies, interviews, recruitment, reports, and quantitative surveys over OAuth streamable HTTP. Open dossier | Conveo MCP Server for Claude Official Conveo remote MCP server for AI-led qualitative research—design studies, manage questions and stimuli, run analyses, and handle recruitment via OAuth at app.conveo.ai. Open dossier | Tandem Docs MCP Server for Claude Public streamable HTTP MCP server for Tandem documentation—install guides, SDK references, workflow docs, headless deployment, and docs-grounded setup help for the Tandem governed runtime. Open dossier | AdAdvisor MCP Server for Claude Hosted AdAdvisor MCP server with curated Meta Ads workflows for browsing creatives, launching campaigns, building audiences, and optimizing performance from Claude via streamable HTTP. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | Cookiy | Conveo | Frumu AI | AdAdvisor |
| Added | 2026-06-14 | 2026-06-14 | 2026-06-14 | 2026-06-14 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓cookiy_create_cue and recruitment tools can incur charges; confirm budgets before approving calls. Use cookiy_introduce and cookiy_help to understand workflow state machines before destructive actions. OAuth tokens grant persistent Cookiy access until revoked. Quantitative and recruitment flows may contact real participants; review scripts before launch. | ✓Study, question, and quota tools can modify active research configurations. Recruitment and participant-reporting tools may expose respondent metadata; handle under your privacy policy. OAuth grants persistent Conveo access until revoked in the MCP client or Conveo account. Review AI-generated study changes before launching participant-facing interviews. | ✓Makes outbound HTTPS requests to tandem.ac and published Tandem documentation sources. Cache-management tools such as invalidate_docs_cache and warmup_docs_cache can affect server-side docs cache state. Docs answers are informational; verify runtime behavior against your installed Tandem version before production changes. Do not treat documentation guidance as a substitute for your own security review of governed agent workflows. | ✓Workflow tools can create or modify Meta Ads campaigns, ad sets, creatives, and audiences when your token has write scope. Bearer tokens grant persistent account access until revoked in AdAdvisor or Meta Business settings. Treat returned spend, conversion, and audience data as business-sensitive before sharing in chat exports. Verify AI-proposed budget or targeting changes before approving tool calls on live ad accounts. |
| Privacy notes | ✓Interview transcripts, participant responses, and billing metadata are processed by Cookiy. OAuth credentials remain in the MCP host; do not paste tokens into chat or public issues. Research studies may contain PII from participants; follow your organization's data-handling policy. | ✓Interview transcripts, clips, and participant data are processed under Conveo's trust center policies. OAuth tokens should remain in the MCP host configuration, not in chat or shared documents. Quote reels and analysis outputs may include voice, video, and behavioral signals from participants. | ✓Search queries, doc paths, and how-to tasks you send are processed by the Tandem docs MCP service. The public docs server does not require credentials; avoid pasting secrets into doc search prompts. Fetched documentation may reference tenant, approval, or connector patterns that do not apply to your deployment mode. | ✓Account IDs, campaign names, creative assets, and performance metrics are sent to AdAdvisor and Meta APIs. Store adv_sk_ API keys in connector headers or secrets managers, not in chat logs or source control. AdAdvisor may retain usage telemetry under its platform terms; review privacy policy before connecting production accounts. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.