Support
DigiData MCP troubleshooting
Start with the error code, then check role and permission, and only then request data. Provider plan, workspace policy and DigiData permission must all be correct.
Last content checked: 27 juli 2026
MCP server URL
https://mcp.digi-data.nl/mcpUse one fixed Streamable HTTP URL; DigiData OAuth determines the tenant and allowed data.
Quick diagnosis
- Query list_sources without showing records
- Check if the desired source has a recent successful sync
- Check whether the table and all used columns are allowed
- If the session expires or is revoked, reconnect
- Narrow broad questions with a date filter, column selection and low limit
Errors and solutions
- 401: log in again; the session or access token may have expired or been revoked.
- 403: Check your DigiData role, workspace policy, and the tables and columns allowed for the connection.
- 429: wait briefly and reduce the demand; the connection protects tenant and database with limits.
- Timeout: request fewer records or columns and use a narrower date filter.
- Missing table: Verify that the source is synced and the table is explicitly allowed.
- Outdated data: first ask for the synchronization status and last successful synchronization.
- IP policy: the cloud provider does not use the customer's browser IP; a separate, explicit tenant policy applies to MCP.
Permission change or revocation
An administrator can adjust the selection or revoke the connection. The change applies immediately; an existing access token may not continue to use the old permission. Reconnect if the provider shows an old consent view.
What you share safely with support
- Provider and workspace plan
- Time and safe fault category
- Correlation or query ID
- Name of source and table, if allowed by your organizational policy
- Never share access tokens, API keys, customer data prompts, or result rows
Still stuck?
Contact DigiData and provide the secure diagnostic information. Provider buttons, plan permissions, or workspace policies may additionally require the ChatGPT or Claude administrator.
Check after recovery
- Start with list_sources and note the last sync time
- Use describe_table before querying a new table
- Request a maximum of a few records and compare them with the source
- Check whether withdrawn tables and columns are really no longer available
- Record the cause and solution if the same workspace is used by multiple teams
