Connect read-only corporate data to your own AI
DigiData MCP is the interoperability path for ChatGPT, Claude and other MCP clients. The connection only reads the sources, tables and columns that a DigiData administrator selects; the DigiData AI agent remains the recommended experience for recurring, controlled business analysis.
Last content checked: 27 juli 2026
Connect directly without API key
Use the fixed MCP server URL and complete the DigiData OAuth permission. You don't have to paste an OData API key into an external assistant. Availability in ChatGPT or Claude also depends on the provider plan, workspace permissions and current provider settings.
Why DigiData synchronizes first
DigiData collects source data in advance and stores it per customer in a protected PostgreSQL database. A question therefore does not have to be sent to Exact Online, Twinfield, Bouw7 or another source API again. This prevents interactive source authentication, network delay, rate limits and API pagination.
DigiData MCP uses a bounded, read-only layer on top of that synchronized data. DigiData AI can also use the richer permitted data model, approved metrics, relationships, channels and automations.
Small, controllable toolset
- list_sources: allowed sources and sync status
- list_tables and describe_table: allowed tables, columns and relationships
- query_table: bounded records with selection, filter, sort and cursor
- aggregate_table: approved counts, totals and groupings
- get_sync_status: freshness and secure source status
What read-only means
- No create, update, delete, send, execute or approve tools
- No arbitrary SQL and no tenant ID as model argument
- Tenant is derived from the validated user and connection
- Consent is per source, table and column and can be revoked
- Audit contains operational metadata, not prompts, filter values, or result rows
Check this before use
- Record the purpose and owner of the connection
- Select only the sources, tables, and columns needed for that purpose
- Test source and schema questions first without requesting records
- Check the reference date and compare a small result with the source system
- Determine who can change or withdraw permission and periodically assess unused connections
Demonstrable limits
DigiData does not publish any unproven speed, flawlessness or certification claim. Results remain dependent on source timeliness, chosen data access, demand and the policy of the external AI provider. Use sync status and citation to verify each business response.
View the public security overview for the controls applied, responsibilities, data flow and contact route for security questions.
Choose your route
Use DigiData AI if you want controlled definitions, recurring analytics, Teams, email, dashboards and a single point of contact. Choose MCP when you consciously want to use a remote assistant and have reviewed its workspace policies, storage, and privacy terms.
Data flow from source to external assistant
DigiData does not request the source API again for every AI query. The MCP layer only reads pre-synchronized data and applies connection permissions before a result reaches the chosen provider.
- Step 1
Source systems
Synchronize Exact Online, Twinfield, Bouw7 and other linked sources outside the interactive query path.
- Step 2
DigiData tenant database
Synchronized data remains separate per tenant and is read with the current connection rights.
- Step 3
Read-only MCP layer
OAuth, source, table, and column permissions, and bounded tools determine what the connection is allowed to return.
- Step 4
Chosen AI provider
Only the allowed result goes to ChatGPT, Claude or another client and is subject to provider policy.