usercall-mcp
Health Uyari
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 5 GitHub stars
Code Uyari
- process.env — Environment variable access in scripts/smoke.ts
- network request — Outbound network request in scripts/smoke.ts
- process.env — Environment variable access in src/index.ts
- network request — Outbound network request in src/index.ts
Permissions Gecti
- Permissions — No dangerous permissions requested
Bu listing icin henuz AI raporu yok.
MCP server that lets AI agents run real user interviews and retrieve themes and quotes.
Usercall MCP - AI agents that run real user interviews
AI can build products. But it still doesn't talk to users.
Usercall MCP lets AI agents run user interviews via voice or text and return structured insights with themes and verbatim quotes.
Why this exists
AI agents can now build and ship products extremely quickly.
But most agents still rely on synthetic feedback or assumptions about users.
Usercall MCP lets agents gather real qualitative feedback directly from users.
Choose a connection
Recommended: hosted MCP (Claude, ChatGPT, Cursor)
Add https://mcp.usercall.co as a remote MCP connector / custom connector.
- OAuth sign-in (no API key, no
npx) - Same five tools as this package
- Docs: app.usercall.co/docs/mcp
This package: local / API-key / machine-to-machine
Use @usercall/mcp over stdio when you want a Bearer API key (scripts, local clients, M2M).
- Sign in at app.usercall.co → Home → Developer → Create API key
- Run
npx -y @usercall/mcpwithUSERCALL_API_KEY
Example workflow
Agent: "Why are users confused about onboarding?"
→ create_study
→ share interview_link with users
→ get_study_results
The returned interview_link can be shared with participants through email, Slack, Discord, or in-product prompts.
Example result:
{
"themes": [
{
"name": "Onboarding confusion",
"summary": "Users struggled to understand the second step.",
"quotes": [
"I wasn't sure what the app was asking me to do.",
"I didn't know I had to verify my email before continuing."
]
},
{
"name": "Pricing confusion",
"summary": "Free plan limits were not clearly communicated.",
"quotes": ["I wasn't sure if the free plan included analytics."]
}
]
}
How it works
AI Agent
↓
Usercall MCP (hosted OAuth or this stdio package)
↓
Usercall Agent API
↓
Real user interviews
↓
Themes and verbatim quotes returned to the agent
Local install (API key)
1. Get an API key
Sign in at app.usercall.co → Home → Developer → Create API key
2. Add to your MCP client
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"usercall": {
"command": "npx",
"args": ["-y", "@usercall/mcp"],
"env": {
"USERCALL_API_KEY": "your_key_here"
}
}
}
}
Cursor (.cursor/mcp.json):
{
"mcpServers": {
"usercall": {
"command": "npx",
"args": ["-y", "@usercall/mcp"],
"env": {
"USERCALL_API_KEY": "your_key_here"
}
}
}
}
For Claude, ChatGPT, or Cursor remote connectors, prefer https://mcp.usercall.co instead of this JSON config.
Restart your MCP client.
3. Ask your agent
Run user interviews to understand why users drop off during onboarding.
Context:
- B2B SaaS product
- 3-step signup flow
Goal:
Identify confusion points and friction.
Target interviews: 5
Language: ko
Interview mode: voice
Show participants this prototype during the interview:
https://www.figma.com/proto/abcd1234/onboarding-flow
The agent will:
- create a study
- return an interview link
- collect responses
- return themes and verbatim quotes
Structured tool example
Equivalent create_study tool call:
create_study
key_research_goal: "Understand why users drop off during onboarding"
business_context: "B2B SaaS signup flow"
target_interviews: 5
language: "en"
interview_mode: "voice"
study_media:
type: "prototype"
url: "https://www.figma.com/proto/abcd1234/onboarding-flow"
description: "New onboarding flow concept"
Tools
create_study
Creates an interview study and returns study_id plus an interview_link to share with participants.
One active agent study is allowed per personal account. If credits are insufficient, the API returns 402 with checkout_url.
| Field | Type | Required | Default |
|---|---|---|---|
key_research_goal |
string (5–2000) | yes | |
business_context |
string (5–2000) | yes | |
additional_context_prompt |
string | no | |
target_interviews |
number (1–200) | no | 1 |
language |
auto | en | ko |
no | auto |
duration_minutes |
number (5–65) | no | 12 |
interview_mode |
voice | text | voice_and_text |
no | voice |
metadata |
object | no | |
study_media |
object | no |
Research goal cannot be changed after create.
study_media (optional) — visual stimulus shown during all interview questions:
| Field | Type | Required |
|---|---|---|
type |
image | prototype |
yes |
url |
string (URL) | yes |
description |
string (max 500 chars) | no |
image: Direct image URL (.png,.jpg,.gif,.webp)prototype: Figma prototype URL (converted to interactive embed)- Media is only visible to web participants; phone callers won't see it
update_study
Updates an existing study. Use this to change interview slots, interview mode, guide copy, questions, or media. Research goal cannot be changed.
| Field | Type | Required |
|---|---|---|
study_id |
uuid string | yes |
target_interviews |
number (1–200) | no |
is_link_disabled |
boolean | no |
ai_agent_intro_message |
string | no |
key_learning_goals |
string | no |
workflow_end_message |
string | no |
workflow_questions |
string[] | no |
interview_mode |
voice | text | voice_and_text |
no |
study_media |
object or null |
no |
Pass study_media: null to clear media. The study_media object follows the same schema as in create_study.
get_study_status
Returns the current lifecycle status of a study.
| Field | Type |
|---|---|
study_id |
uuid string |
Status values: running · analyzing · complete
Response includes interview progress fields, includingcompleted_interviews and target_interviews.
get_study_results
Returns analysis output once the study is complete.
| Field | Type | Required |
|---|---|---|
study_id |
uuid string | yes |
format |
summary | full |
no |
Summary/full responses include study progress fields and analysis output.
delete_study
Permanently deletes a study and all associated data (recordings, transcripts). Releases unused reserved credits.
| Field | Type | Required |
|---|---|---|
study_id |
uuid string | yes |
Example workflow
1. create_study
key_research_goal: "Why do users drop off during onboarding?"
business_context: "B2B SaaS, 3-step signup flow"
target_interviews: 5
language: "ko"
interview_mode: "voice"
→ returns { study_id, interview_link }
2. Share interview_link with participants
(email, Slack, in-product prompt, etc.)
3. get_study_status
→ "analyzing"
4. get_study_results
→ themes + verbatim quotes returned to the agent
With visual stimulus
1. create_study
key_research_goal: "Get feedback on new dashboard design"
business_context: "Redesigning analytics dashboard for power users"
study_media:
type: "image"
url: "https://example.com/dashboard-mockup.png"
description: "New dashboard design concept"
→ returns { study_id, interview_link }
2. Share interview_link — participants see the mockup during interview
For Figma prototypes, use type: "prototype" with a Figma proto URL.
Requirements
- Node.js 18+
- A valid Usercall API key (local / API-key path only)
Self-hosting / development
pnpm install
pnpm build
USERCALL_API_KEY="your_key_here" pnpm start
Smoke test:
USERCALL_API_KEY="your_key_here" pnpm smoke
Troubleshooting
| Error | Fix |
|---|---|
Missing USERCALL_API_KEY |
Set the env var before starting this stdio package |
401 Unauthorized |
Invalid or revoked API key |
402 Insufficient credits |
Open the returned checkout_url, or add credits at app.usercall.co |
500 on create |
Verify your key has access to Agent API v1 |
Remote Claude / ChatGPT / Cursor connectors should use https://mcp.usercall.co (OAuth). This package is the API-key stdio path.
License
MIT
Yorumlar (0)
Yorum birakmak icin giris yap.
Yorum birakSonuc bulunamadi