Skip to content

MCP server development. Claude connected to your systems, safely.

Custom MCP servers that connect Claude to your CRM, ERP, document stores and internal tools, with access control, audit logging and the right approval for every action.

30 minutes with a solution architect.

In short

What is an MCP server, and when do you need a custom one?

An MCP server exposes a system’s data and actions to AI applications through the Model Context Protocol, the open standard that Anthropic donated to the Agentic AI Foundation of the Linux Foundation in December 2025. Claude then uses that system as a connector. A custom MCP server makes sense when a system has no ready-made connector, runs inside your network, or needs tighter scopes, approvals and logging.

Written and reviewed by Solorai

MCP donated to the Linux Foundation
Dec 2025
per tool: always allow, needs approval, blocked
3 levels
for chat, Cowork and Claude Code
1 server

What does MCP server development include?

A connector your security team can sign off and your people can use.

  • Tool design

    The actions and data Claude may use, defined with the system owner, with reading and writing kept separate.

  • Authentication

    Each user signs in with their own account, so Claude sees only what that person may see.

  • Access control

    Scopes per tool, least privilege by default and sensitive actions behind approval.

  • Audit logging

    Every tool call logged with who, what and when, ready for your security monitoring.

  • Deployment

    Hosted in your environment and added to Claude as a custom connector by an organisation owner.

  • Rollout

    Tool permissions set, teams shown how to use the connector, usage reviewed.

How we build

From system to connector

Six steps. Your Claude owner decides when the connector goes live and what each tool may do.

  1. Scope

    Solorai with the system owner

    Which system, which users, which actions and which data.

  2. Design

    Solorai

    Tools, inputs, outputs and permissions, with reading and writing separated.

  3. Build

    Solorai

    The server, its authentication and its audit log.

  4. Test

    Solorai with your team

    Real tasks in Claude, plus security tests against misuse.

  5. Connect

    Your Claude owner

    Added as a custom connector, with permissions set for each tool.

  6. Operate

    Solorai with your team

    Monitoring, updates and new tools as needs grow.

Where to start

How do we start an integration?

Fixed formats with a clear scope. Prices are agreed in a written proposal.

  • Claude Enterprise

    Foundations

    Single sign-on, roles, data policies, connectors, a library of skills and basic training.

    Duration
    About 3 weeks
    Group
    Up to 50 people
  • Start

    AI readiness assessment

    An analysis of your use cases and the data available for them, ending with a plan and its costs.

    Duration
    About 2 weeks

FAQ

MCP servers, in short

What is an MCP server?

A service that exposes a system’s data and actions to AI applications through the Model Context Protocol, so a model such as Claude can search, read and act in that system within set permissions.

What is the Model Context Protocol?

An open standard for connecting AI applications to tools and data, introduced by Anthropic in 2024 and donated to the Agentic AI Foundation of the Linux Foundation in December 2025.

When do we need a custom MCP server?

When a system has no connector in the directory, when it runs inside your network, or when you need narrower scopes, approvals and logging than an existing connector offers.

How is access controlled?

Each user signs in with their own account, tools are scoped to what they need, and in Claude each tool can be set to always allow, needs approval or blocked.

Does the same connector work in Claude Code?

Yes. Connectors added in Claude are available in Claude Code when developers sign in with their Claude account.

Who can add a custom connector?

On Team and Enterprise plans, an organisation owner adds it, using the server’s URL.

Claude, connected to your systems. Start with a 30-minute briefing.

Tell us which systems Claude should work with. We will reply with a clear next step.