# Usercall [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/junetic/usercall-mcp  
**GitHub Stars:** 5  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/usercall

## Description
Give your AI agents the ability to ask real users why.

## Tools
Capabilities this server exposes over MCP:

- **get_trigger_capabilities** — Which in-product trigger conditions work. One event, exact property or trait, URL rule, page dwell. No counts, sequences, absence, time windows, or not-equals
- **get_trigger_sdk_setup** — Snippet for product events (failed action, onboarding, churn). `install_snippet`, `identify_snippet`, `allowlist_update_snippet`. No secret keys
- **list_trigger_events** — Product event names from the last 30 days. A trigger accepts only an observed name
- **get_trigger_event_schema** — Fields on one product event, with types and sample values. Exact, case-sensitive, type-sensitive
- **list_studies** — Existing interview studies: `study_id`, `interview_link`, `interview_mode`, `trigger_eligible
- **create_research_trigger** — Paused invite after a product moment (failed action, churn, onboarding). Returns `activation_url
- **list_research_triggers** — In-product triggers with status and `activation_url
- **get_research_trigger** — One trigger: who it invites, `activation_url`, invite and interview counts. No themes or quotes
- **update_research_trigger** — Who gets invited. `status: "active"` is rejected (409). Editing an active trigger pauses it
- **delete_research_trigger** — Permanently delete a trigger. Completed interviews stay on the study

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "usercall": {
    "command": "npx",
    "args": ["-y","@usercall/mcp"],
    "env": {
      "USERCALL_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `USERCALL_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Usercall does

The Usercall MCP server lets an agent arrange interviews with real users through Usercall. A study defines the research goal, optional business context, target number of interviews, languages, duration, interview mode, and optional visual material such as an image or Figma prototype. The study returns an interview link that can be shared with participants through external channels or product prompts.

Interview modes include voice, text, and voice-and-text. Results can include themes, summaries, insights, risks, and verbatim participant quotes. The server is suited to questions such as why users abandon onboarding, churn, misunderstand a feature, or fail a particular action.

## How it works

The Usercall MCP server can run as a hosted MCP connection or as a local stdio process. The hosted service is available at `https://mcp.usercall.co` and uses OAuth sign-in. The local package is run with `npx -y @usercall/mcp` and authenticates with a Usercall API key.

For targeted research, an agent can inspect the product events Usercall has received, examine the schema for one event, and create a paused Research Trigger tied to an existing study. After a human activates the trigger in Usercall, the SDK invites matching users after the configured product event. Trigger filters use exact matches on event properties or user traits, with optional sampling and daily invite limits.

The trigger workflow depends on the Usercall SDK being installed in the product. If no events are available, `get_trigger_sdk_setup` provides snippets for installing the SDK, identifying users, and updating an allowlist. An analytics system such as PostHog or Mixpanel can identify behavior, but the supplied tools handle the Usercall study and trigger steps.

## Setup and configuration

For local use, create an API key in Usercall under Home → Developer → Create API key, then provide it as `USERCALL_API_KEY`. Configure the MCP client to start `npx -y @usercall/mcp` over stdio. The README includes configurations for Claude Desktop and Cursor. Hosted connections should use the remote endpoint instead of the local JSON configuration.

A study requires `key_research_goal`. Optional fields include business context, target interviews, languages, duration, interview mode, voice gender, metadata, link variables, and study media. The research goal cannot be changed after creation. Creating a study does not itself run interviews or invite a participant; it returns an interview link for distribution.

## Tools and capabilities

The Usercall MCP server exposes capabilities for:

- Creating and listing interview studies and retrieving study results.
- Listing observed product events from the previous 30 days.
- Inspecting event fields, types, and sample values.
- Checking supported trigger conditions and obtaining SDK setup snippets.
- Creating, listing, inspecting, updating, and deleting Research Triggers.
- Returning trigger status, activation URLs, invite counts, and interview counts.

Trigger conditions support one event, an exact property or trait match, a URL rule, and page dwell. Counts, sequences, absence conditions, time windows, and not-equals filters are not supported. Only event names already observed by Usercall can be used, and event matching is case- and type-sensitive. New or edited triggers are paused for activation; setting an active status directly is rejected, and editing an active trigger pauses it. Deleting a trigger is permanent, although completed interviews remain on the study.

_Full upstream README: https://allmcps.com/mcp/usercall/readme_