Connect kvCORE to Claude Code

Make Claude update leads and add notes in kvCORE. From the terminal, inside the sessions where you already work.

How do you connect kvCORE to Claude Code?

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

claude mcp add --transport http kvcore 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 kvCORE once connected?

Full read-write kvCORE access lets Claude update a lead's stage and details, add a note, log a follow-up note, add or change a tag, and assign a contact to an agent once you approve. The updates that used to mean clicking through tabs happen where the lead record already lives.

Update a lead's stage, status, and contact details on the record
Add a note to a contact's activity history
Log a follow-up note on a lead so next steps stay on the record
Add, change, or remove tags to segment your database
Assign or reassign a contact to the right agent or team
Search contacts matching a query and propose batched updates

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

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

More on the kvCORE connector

kvCORE connector for claude.ai MyCase + Claude Code PracticePanther + Claude Code Filevine + 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