> ## Documentation Index
> Fetch the complete documentation index at: https://docs.userintuition.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Resolve authentication, stale package, missing-tool, and backend-domain errors.

## 401 Unauthorized

For hosted Streamable HTTP, confirm the client is connected to `https://mcp.userintuition.ai/mcp`, then reconnect OAuth from the client.

For stdio, confirm `USERINTUITION_API_KEY` is visible to the process that launches the MCP server and starts with `ui_sk_`. Create or rotate keys under **Settings → API Keys** at [app.userintuition.ai](https://app.userintuition.ai). A valid credential can still receive `403` or `404` for a resource the account does not own.

## An older tool surface appears

The current server identifies itself as **User Intuition** and exposes 50 tools. Its queued study-design entry point is `queue_customize_study`, and its research entry points are `search_research` and `answer_research`. A connector is stale if it identifies itself as **User Intuition Human Signal**, reports 38 tools, offers `ask_humans` or retired direct-design tools such as `create_study_and_launch_panel`, `replace_study`, or `upload_concept_link`, or returns a tool-not-found error for a current name such as `list_targeting_attributes`.

In ChatGPT, remove the old custom connector, create it again with `https://mcp.userintuition.ai/mcp`, complete OAuth, and start a new chat. Confirm that `customize_study` is available and `ask_humans` is not before attempting a study. Reauthorizing without recreating the connector may leave its cached tools unchanged.

For local stdio clients, if you see legacy names such as `create_panel`, `create_invite`, or `list_calls`, restart the client and force a fresh package:

```bash theme={null}
npx -y @userintuition-ai/mcp@latest
```

Most clients load tool definitions only when a connector or session starts. Recreate the hosted connector when reauthorization alone leaves stale names, or restart the stdio client, then start a new chat or task. Do not ask for a removed tool to be restored: use the current tool named in the [tool reference](/mcp-server/tools/studies).

## A tool returns a domain error

Not every non-success response is an authentication problem. Examples include:

* report generation on a study with no usable interviews
* reward delivery for an ineligible or unknown participant
* direct Panel launch below 10% incidence
* editing a fielding Panel study before pausing or stopping it

Read the returned error and use the corresponding lifecycle or feasibility action. Do not reconnect OAuth or regenerate an API key for a valid `400`, `403`, `404`, or `409` domain response.

Invalid tool inputs return `validation_error` with a `correct_input` hint. If a report has not been generated, `no_report_yet` points to `generate_report`; if the study has no completed interviews, `no_completed_interviews` points to finishing interviews first. A `404` for an interview or study means that resource could not be found or accessed. Check its public ID and account access before retrying.

## A study plan change does not appear

Use `customize_study` for the plan, expected duration, audience, screeners, and concept material. Continue the conversation whenever it returns `response_type: "question"`, then call `get_study` to verify the persisted result. `update_study` is only for ordinary metadata. If a Panel study is actively fielding, call `pause_study` or `stop_study` before editing.

## Getting help

Email [support@userintuition.ai](mailto:support@userintuition.ai) with the tool name, timestamp, response status, and a redacted error message. Never send your API key or webhook signing secret.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.