Guide8 mins

Using Twinfield with Claude via a read-only MCP server

Link selected Twinfield read-only data to Claude via DigiData MCP, without sharing a Twinfield password or OData API key.

Auke Westra

By Auke Westra

Founder of DigiData

Practical guide. This article covers the steps, checks, and common issues. View the Twinfield product page for supported data, operation and availability.

Short answer

You use Twinfield with Claude by first synchronizing Twinfield with DigiData and then authorizing a read-only DigiData MCP connector in Claude. An administrator selects the offices, tables and columns; Claude only gets that data back and cannot write anything to Twinfield.

Why Twinfield is not called directly from every conversation

The Twinfield integration synchronizes the selected financial data in advance to DigiData. The interactive Claude query therefore does not need to perform Twinfield authentication, source pagination and network routing. Claude uses a bounded MCP layer above the last synced tenant data.

Twinfield does not change this design. The MCP tools are read-only and do not include posting, modifying, sending, or approving actions.

Conditions

Check which Twinfield offices the linked user is allowed to open and which of them are selected in DigiData. You also need a DigiData administrator and a Claude plan with appropriate connector rights. Anthropic describes various management flows for individual and organizational plans; therefore follow the current Claude MCP setup.

Step 1: Choose the minimum data set

Start with a specific question. A financial overview may require transactions, accounts receivable, accounts payable and general ledger accounts. Project fields may be relevant for project analysis. Select only the tables and columns that the Claude connection needs for that purpose.

Check the last successful synchronization in advance. MCP reads synchronized data; a successful connector does not mean that Twinfield data from after the last sync is already available.

Step 2: Add the connector

Create an AI connection for Claude in DigiData and note the fixed MCP server URL. Add that URL in Claude as a custom connector according to the current Anthropic instructions. At an organization, an Owner may need to add the connector before members connect individually.

Choose Connect, complete DigiData OAuth and 2FA and read the permission screen. The permission should clearly show the tenant, read-only status and selected data.

Step 3: Check before analysis

Have Claude first show allowed resources, then the Twinfield synchronization status, and then the schema of the desired table. For a first data query, use a small limit, a defined period and only necessary columns.

For financial answers, ask for the source, period, filters and reference date used. A model answer remains an analysis that must be checked; compare important totals with Twinfield and your organization's definitions.

Move in and troubleshoot

A DigiData administrator can delete tables or columns and revoke the connection completely. In addition, remove the connector from Claude when it is no longer used. For 401, 403, 429, timeouts, or missing tables, follow MCP Troubleshooting without sharing tokens or result rows with support.

Privacy boundary

DigiData does not train on customer questions or company data. Once permitted Twinfield data is sent to Claude, Anthropic processes its own copy according to the chosen consumer or commercial product, organizational settings and contract. Assess that provider layer before releasing financial data.

For recurring dashboards you can use Twinfield via OData in Power BI. For centrally managed analytics, DigiData AI is the recommended route.

Sources

Auke Westra

About Auke Westra

Founder of DigiData

Auke Westra is Founder of DigiData and writes about data integrations, OData and Power BI.

View LinkedIn profile

Ready to start?

Try DigiData for free for 14 days. Connect your software, load your data into Power BI and discover the difference.

Please contact us

Related articles