Claude integrations and MCP connectors for business software
Claude can work inside your software, or your software can be reachable from Claude, so a person asks for an action in plain words and a connector carries it out.
Reviewed by: Rahul Jaiswar, founder
What Anthropic and Claude are
Anthropic builds the Claude models and sells access through an API. It also created the Model Context Protocol (MCP), an open standard that lets Claude and other AI apps call tools inside other software. MCP is now governed under the Linux Foundation’s Agentic AI Foundation.
How we use it
- We use Claude in internal tooling.
- Microsive Dialer’s Claude connector, built on MCP, lets a rep place calls from Claude Desktop (Microsive Dialer).
When it fits
- The job has steps with tools. Look something up, act on it, then report back, with each step calling your software.
- Your staff already work in an MCP-capable app such as Claude Desktop, and the actions they want already exist in your software’s API. A connector then adds a new way in without a new screen.
- The action can be confirmed or reversed. Placing a call suits a connector. Moving money needs far tighter controls first.
- Your approved cloud account may already offer Claude. Check whether Claude is available through the cloud account you’ve approved (Amazon Bedrock, Google Vertex AI or Microsoft Foundry) before starting a new vendor review.
When it doesn’t
- Thousands of short, repeated tasks where cost per call matters more than quality, such as tagging one-line messages. Price a month of the job on a smaller hosted model or an open model you run (hosted against self-hosted).
Five questions for your build team
- Which actions can the connector take alone, and which need a person to confirm?
- How does the connector identify the user and limit them to their own data?
- Where is the record of what the AI did through the connector?
- What data leaves our systems during a tool call?
- What happens when the model calls the wrong tool?
Pitfalls
- Tool names and descriptions steer the model. Vague ones lead to wrong calls, so write and test them like any other instruction.
- One shared key. A remote connector should use OAuth sign-in, so each person authorises it with their own account and it acts with their permissions, not with a key everyone shares.
- No trail. Without a log, nobody can answer “who did this?”. Keep an audit log of actions an agent takes.
See also
Want your team to run your software from Claude?
Name the system and the three or four actions people ask for most.