> ## 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.

# Attach studies and reports

> Use authenticated MCP resources to bring saved research into a conversation.

Clients that support MCP resource attachments can add a saved study or its latest report to a conversation. The server lists the 20 most recently updated studies and the 20 most recently updated studies with reports that the current credential can access. Use a resource URI directly for an older study.

| Resource URI | Contents |
| - | - |
| `userintuition://study/{study_id}` | Saved study settings, plan, screeners, and targeting |
| `userintuition://report/{study_id}` | Latest report overview |
| `userintuition://report/{study_id}/{view}` | One named section of the latest report |
| `userintuition://events/{study_id}` | Recent `study.completed` and `report.ready` event envelopes, when live events are enabled |

For `{view}`, use `overview`, `study_findings`, `participant_profiles`, `participant_responses`, `evidence_coverage`, `recommended_next_steps`, or `references`. The `full` report view is not offered as an attachment. Use `get_study_report` when you need the entire report or when a section is too large to attach.

Resources use the same authorization and workspace checks as the public study and report endpoints. Hosted OAuth access requires the `read` scope. An unavailable or ungenerated report returns the public API error. Attachments are capped at 64 KiB; a larger response contains a `resource_too_large` pointer instead of partial research data.

If your client does not expose resource attachments, call `get_study` or `get_study_report` with the same study ID.

## Listen for study and report changes

Clients that support the MCP 2026-07-28 `subscriptions/listen` method can subscribe to a study, report, or events URI above. The hosted server checks access to the study before opening the stream. When a study completes or its report becomes ready, the server sends `notifications/resources/updated` for the affected study or report and for the events resource. Read `userintuition://events/{study_id}` to see the event ID, type, study ID, and data. The event envelope matches the webhook payload, so an integration can use webhooks while a chat client listens for the same milestones.

The events resource retains the latest 100 envelopes for 24 hours. A listen stream closes after 25 minutes by default; reconnect to keep receiving updates. Set `MCP_EVENT_REDIS_URL` on the backend to the same Redis instance as the MCP service's existing `REDIS_URL`. Webhooks continue to deliver independently. Clients without listen support can use the existing polling tools and webhooks.


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