DGAI with Claude (MCP)

Advanced. Beyond the chat app, DGAI ships an MCP server — it exposes the same privacy-protected data tools to any Model Context Protocol client, such as Claude Desktop or Claude Code. You chat in Claude, and Claude can query your GDAT data through DGAI — still fully tokenized.

Register the server with Claude Code

Run this once (replace the paths with your own):

claude mcp add dgai -- dotnet run --project <abs-path>/DGAI.Mcp -- --gdat "<path-to-your.db>"

Claude Desktop uses the same command in its MCP server configuration. On startup the server logs (to its error output) something like dgai-mcp: serving 1,234 persons from … (read-only, tokenized).

How privacy works over MCP

The MCP server is always fully tokenized. For safety it deliberately does not offer:

real-names mode,
the free-text opt-in, or
a token-reveal tool.

Every result is still checked by the outbound guard before it's returned. To translate a token back to a real name, use the chat app's Token lookup tab, or the command line: dgai reveal [M1234] --gdat "<db>".

Because the client (Claude) reasons only in tokens, it's told to resolve any name you type to a token first and to answer in tokens — DGAI restores the real names for you.

Beta & developer-oriented. The MCP server currently runs from source (dotnet run) and expects the DGAI/GDAT developer checkout and the .NET 10 SDK. If you just want to chat, the DGAI app needs none of that.