Connect Brightpearl to Claude Code

Have Claude draft orders and update records in Brightpearl. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Brightpearl to Claude Code?

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

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

Full read-write Brightpearl access lets Claude create and update the records you work in: draft a sales order from an email, raise a purchase order against the right supplier, update a customer or product, or add a note to an order, then route it for your approval. The data entry that used to mean clicking through the back office happens where the records already live.

Draft a sales order from an email or quote you paste in
Raise a purchase order against the right supplier and products
Create or update customer, supplier, and product records
Update product pricing, stock details, or warehouse fields on a record
Add a note or update the status on an existing order
Search orders matching a filter and propose batched field edits

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

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

More on the Brightpearl connector

Brightpearl connector for claude.ai Dynamics 365 Business Central + Claude Code Acumatica + Claude Code Epicor + 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