Connect Internal database to Claude Code

Let Claude run scoped reads and writes against your internal database. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Internal database to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Internal database, you add a Internal database MCP server: a small hosted service that exposes Internal database's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Internal database account. No API keys pasted into config files.

claude mcp add --transport http internal-database https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Internal database once connected?

Full read-write internal database access lets Claude run a parameterized query, insert a new record, update a status, and correct a bad field once you approve, all against your own schema. The lookups and routine data entry that meant hand-written SQL or copy-paste now happen in plain language where the data lives.

Run a parameterized read query and summarize the result set
Insert a new record into a specified table with validated fields
Update a status or field on an existing row after you confirm
Correct or normalize values flagged during a data review
Look up related records across tables and propose the change set
Soft-delete or archive a record behind a confirmation step

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Internal database access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Internal database API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Internal database changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Internal database connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Internal database connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Internal database account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Internal database's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Internal database?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Internal database account it signs in with. Revoking access is one click in Internal database.

More on the Internal database connector

Internal database connector for claude.ai Custom CRM + Claude Code Internal referral portal + Claude Code Proprietary ERP + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us