db_mcpphoebe-ai.de/tools
DE EN

Tool · Databases for Claude

Ask your database.
In plain language.

db_mcp connects Claude – using your own Claude subscription – to your company's databases: ERP, accounting, document management, custom applications. Claude finds the right tables, calculates, compares and explains. You ask the way you would ask a colleague.

How setup works What Claude may do – and what not
Examples

What you can ask

  • “Which items sold best over the last 30 days – and how is their stock looking?”ERP
  • “Which customers haven't ordered for a year but used to spend more than €5,000 a year?”Sales
  • “How did monthly revenue develop compared to last year? As a table, please.”Reporting
  • “Which open items are older than 60 days, sorted by amount?”Accounting
  • “Compare the stock levels in the ERP with those in the warehouse system and show me the differences.”across two databases
  • “Which documents from supplier Miller have come in since March?”Document management
How it works

A small program on your side, Claude as usual

The database bridge runs as a Windows service on a computer in your network. It knows your databases, checks every query Claude wants to run and passes on only the result.

Claude reaches the bridge in one of two ways:

Way 1: the connector (recommended)

It is set up once in claude.ai and is then available in all Claude applications of your account: in the browser, in Claude Desktop and in the Claude app on your phone, also on the road. This means:

  • The bridge opens an encrypted connection to our server in Germany. It only passes the queries and their results through – contents are neither stored nor analysed there.
  • You sign in with a password and a second factor (authenticator app).

Way 2: the extension for Claude Desktop

This is the local way: Claude Desktop on the bridge's computer talks to it directly. This means:

  • The queries run on your computer and do not travel through our server.
  • It runs through Claude Desktop on that computer; for your phone and other computers the connector is the way. (While Claude Desktop is running, the extension may currently also show up in the browser – that is up to Anthropic and can change.)

For both ways

  • Claude itself runs at Anthropic: the results Claude needs for an answer go to Claude – like everything you type into Claude. Whatever Claude should not see, you lock in the bridge.
  • The computer with the bridge has to be running – after all, the data stays on your side.
  • The bridge connects outwards by itself – you do not need to open any port.

Claude gets to know your database over time: what it learns about tables and relationships, it notes for later conversations – marked as “confirmed”, “derived” or “assumption”. For well-known systems such as JTL-Wawi it comes with basic knowledge already.

Databases

Not just ERP

db_mcp is not tied to a particular program. It talks to the database underneath – so it works with standard software as well as with custom applications. Several databases at once are no problem; Claude can also compare them with each other.

MS SQL Server

Microsoft SQL Server

E.g. JTL-Wawi, many industry solutions and document management systems – on premises or hosted.

MariaDB / MySQL

MariaDB and MySQL

E.g. Sage 50 (German edition), online shops, web applications and your own databases.

Firebird · in trial

Firebird

Common in older and specialised ERP and point-of-sale systems. Support is built in and currently being tried out with first users – get in touch.

On request

Other databases

Your database is not listed? Ask us – further connections are possible.

Security

What Claude may do – honestly explained

  • Claude only reads. The bridge works with a database user of its own that may only read. Even if everything else failed, the database itself would not allow any change.
  • Every query is checked. Read queries only, one at a time, with time and size limits – so Claude does not slow down your ERP.
  • Locked areas stay locked. Tables and columns with passwords, credentials or bank details are locked with one click. If Claude comes across something like that, it locks the area itself and tells you – only you can unlock it.
  • You decide who gets to which database. For each database you choose whether it can be reached through claude.ai, only on your computer, or both. For especially sensitive data, every single Claude session also needs your approval: Claude asks and gives you a name for the request, you approve it in the bridge – other chats or colleagues on the same subscription stay out. You can revoke approvals at any time.
  • Changes only when you explicitly want them. Writing is off by default. Who needs it enables it for individual databases, with a separate write user; Claude then shows every change first and carries it out only after your approval.
  • Your data stays where it is. Our server only checks the sign-in and passes requests through; it stores no content of your database. Intermediate results of large analyses stay on the bridge's computer and are deleted after 24 hours.
  • What Claude reads goes to Anthropic. Like everything you type into Claude, query results are processed by Anthropic (the maker of Claude) under its terms. So lock what Claude should not see beforehand.
Requirements

What you need

  • A Windows computer that is running most of the time and can reach the database – often the database server itself or a server next to it.
  • A paid Claude subscription (Pro, Max, Team or Enterprise).
  • For the setup: administrator rights on that computer and someone who can create a read-only user on the database.

How setup works, how long it takes and whether you can do it yourself – find out with a short self-check.

How setup works

The bridge's user interface and the manual are currently available in German.