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

# FAQ

> Common questions, current limitations, and what to do when something fails.

<AccordionGroup>
  <Accordion title="Does the MCP server cost anything?">
    No. It's included with your Research Desk account at no additional charge. Sample costs remain the same within your Research Desk account, and any AI assistant subscription costs are between you and that provider.
  </Accordion>

  <Accordion title="Can my assistant change things without me approving?">
    Every write tool returns a preview first and executes only on an explicitly confirmed second call that's enforced by the server. See [Tools](/mcp/tools).
  </Accordion>

  <Accordion title="Is my data safe? Who can see what?">
    The MCP server adds no new access rights. You sign in as yourself, every request runs with exactly the permissions your Research Desk role already has, and all activity is attributable to your user.
  </Accordion>

  <Accordion title="Which AI assistants work with it?">
    We've verified that it works with Claude and ChatGPT, but any MCP client with standard OAuth support should work.
  </Accordion>

  <Accordion title="Should I use the MCP server or the Demand API?">
    Use the MCP server for conversational, ad-hoc, human-in-the-loop work. Use the [Demand API](/demand/overview/00-getting-started) for systematic integration, automation, and high-volume or scheduled operations (see its [rate limits](/demand/overview/02-rate-limits)). Many teams will use both, and feel free to contact your Research Desk account manager.
  </Accordion>
</AccordionGroup>

## Troubleshooting

Validation happens before anything is written, so a rejected change leaves Research Desk untouched. If your assistant reports an error it can't resolve, ask it to **show the raw error response** — it usually names the field or record at fault.

| Symptom                                                         | What to do                                                                                                                                                                                |
| --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Assistant can't see the Research Desk tools                     | The connector is added but not signed in. Complete the sign-in step in your assistant's connector settings                                                                                |
| `401` / authentication errors on a connection that used to work | Your token expired. Disconnect and reconnect the connector to force a fresh sign-in. Contact us with persistent issues.                                                                   |
| `403` / permission denied — reads work but writes fail          | Your Research Desk role likely doesn't permit that change. If you *can* do it in the UI, report it to us.                                                                                 |
| "Record not found" or missing data                              | Confirm you can see that record in the Research Desk UI as the same user                                                                                                                  |
| Invalid country, language, or qualification ID                  | Valid values come from `list_definitions` and `list_qualifications`, and qualification IDs are country-specific. Ask your assistant to look them up rather than reuse them across markets |
| Missing required field / wrong type                             | The error names the exact field (e.g., `project_data.project_number: Field required`). Ask your assistant to fix and retry                                                                |
| Duplicate `project_number`                                      | Project numbers must be unique within an account                                                                                                                                          |
| Sign-in never opens or fails immediately                        | Check the URL is exactly `https://mcp.researchdesk.com/mcp`                                                                                                                               |

## Support

Contact your Rep Data account manager or [clientsuccess@repdata.com](mailto:clientsuccess@repdata.com) with any issues. Include the AI assistant you're using, the tool that failed, and the error message your assistant received.