Connect On-prem application to Claude Code

Let Claude read and write live records in your on-prem application, inside your firewall. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect On-prem application to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect On-prem application, you add a On-prem application MCP server: a small hosted service that exposes On-prem application'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 On-prem application account. No API keys pasted into config files.

claude mcp add --transport http on-prem-app 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 On-prem application once connected?

Full read-write on-prem application access lets Claude pull a live record, update a field, change a status, and create an entry once you approve, all inside your network boundary. The lookups and routine data entry that meant remote-desktop sessions and re-keying now happen in plain language where the records already live.

Look up a live record and summarize its current state
Update fields or change the status on an existing entry
Create a new record from a draft you approve
Append a note or log an action against a record
Reconcile or correct values flagged during a review
Flag entries that fall outside a threshold for your attention

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 On-prem application 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 On-prem application API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when On-prem application 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 On-prem application 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 On-prem application 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 On-prem application 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 On-prem application'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 On-prem application?

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 On-prem application account it signs in with. Revoking access is one click in On-prem application.

More on the On-prem application connector

On-prem application connector for claude.ai Custom CRM + Claude Code Internal database + Claude Code Internal referral portal + 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