Skip to main content
USA-Based Digital Agency

Service · Updated

MCP Server Development. Connect your software to any AI assistant once.

An MCP server is a small service that exposes your software's data and actions to AI assistants through the open Model Context Protocol. Build it once and Claude, ChatGPT, Cursor or your own agent can use the same tools, with the permissions you set. We design, build, secure and host MCP servers for business systems.

By George Shvaya, founder of Webvello · Published

Key takeaways

  • MCP (Model Context Protocol) is an open standard, introduced by Anthropic in November 2024, for connecting AI assistants to tools and data.
  • An MCP server exposes three things: tools (actions), resources (data to read) and prompts (reusable instructions).
  • One MCP server can serve many AI clients, so you stop rebuilding the same integration for each assistant.
  • The MCP specification defines OAuth-based authorization for remote servers, so each user can sign in with their own permissions.
  • We built and run BalanceMCP, a hosted MCP server that lets an AI assistant work in a double-entry ledger.

What is an MCP server?

It is the adapter between an AI assistant and one of your systems.

An MCP server is a program that speaks the Model Context Protocol and wraps one system, such as your CRM, a database or a set of internal APIs. The AI assistant is the client. It asks the server what it can do, then calls those tools when a task needs them. For the full background, read our MCP guide.

MCP building blocks, with a field-service example
PrimitiveWhat it isExample for a contractor
ToolsActions the assistant can callcreate_lead, find_open_slots, draft_estimate
ResourcesData the assistant can readPrice book, service-area list, job history
PromptsReusable instruction templates"Summarize this site visit in our estimate format"

What do businesses build MCP servers for?

Anything your team already asks an AI to help with, but has to copy and paste data for.

CRM and job software

Look up a customer, check job status, log a note or draft a follow-up from inside the assistant your team already uses.

Reporting

Ask questions of your own data in plain English, such as last month’s closed jobs by city, with answers read from the source system.

Books and finance

Categorize transactions and reconcile statements against a real ledger, with a person reviewing every entry.

Marketing data

Connect search, analytics and ad data so an assistant can pull numbers and explain changes without exports.

Built by Webvello: BalanceMCP

BalanceMCP is a hosted MCP server and double-entry ledger we designed and built. You drop in a bank statement and the assistant categorizes, reconciles and produces financial statements. It is the same pattern we use for client systems: narrow tools, a real source of truth and a person reviewing the output.

Have a system your team keeps copying data out of?

Tell us which one. We will sketch the tools an MCP server would expose and what it would take to build.

How do you keep an MCP server secure?

An MCP server is a door into your system, so we build it like one.
  • Per-user authorization. Remote servers follow the specification's OAuth-based authorization, so each person acts with their own permissions.
  • Least privilege. Read-only tools by default. Write tools are narrow, named for what they do, and validated server-side.
  • Human approval. Tools that send, delete, pay or change prices require a confirmation step in the client.
  • Prompt-injection awareness. Text pulled from emails, forms or web pages is treated as data, never as instructions to run a tool.
  • Audit logs. Every tool call is logged with the user, the input and the result.
  • Rate limits and kill switch. Limits per user and a single setting to disable writes.

Local or remote: which kind do you need?

It depends on who uses it and where the data lives.
Local vs remote MCP servers
Local (stdio)Remote (HTTP)
Runs onThe user’s own computerA server you or we host
Best forOne technical user, developer toolsA team, or customers of a product
Sign-inUses local credentialsOAuth, per user
UpdatesEach user updates their copyDeploy once for everyone

How we build one

Small, well-named tools first. Coverage grows from real use.
  1. 1

    Tool design

    List the questions and actions people actually need, then name and describe each tool so the model picks the right one.
  2. 2

    Build with the official SDK

    TypeScript or Python SDKs, typed inputs, server-side validation.
  3. 3

    Auth and permissions

    OAuth for remote servers, scoped keys to your system, read-only first.
  4. 4

    Test with real clients

    We test in Claude and other MCP clients on real tasks, and fix where the model misuses a tool.
  5. 5

    Host and monitor

    Deploy, log, set limits and hand over the run-book.

Want to try it yourself first? Our walkthrough on how to build an MCP server covers the basics. If your team is adopting Claude Code, our Claude Code consulting covers MCP setup for developers.

Pages that go deeper on the pieces this one touches.

Common questions

Straight answers to what owners ask us first.

What is an MCP server?

An MCP server is a program that exposes a system’s data and actions to AI assistants using the open Model Context Protocol. It offers tools (actions), resources (readable data) and prompts (instruction templates). Any MCP-compatible client, such as Claude or other assistants that support the protocol, can then use it.

Which AI assistants can use an MCP server?

Claude (desktop, web and Claude Code) supports MCP, and support has spread to other assistants, IDEs and agent frameworks. Client support for specific features varies, so we test the server in the clients your team actually uses.

Does our data leave our systems?

Only the data a tool returns for a given request is sent to the AI assistant. The MCP server decides what each tool can read, and it can run inside your own infrastructure.

How long does it take to build an MCP server?

A focused server with a handful of read tools and one or two write tools typically takes two to three weeks, including authorization and testing. Larger systems are built in stages.

Is MCP the same as an API?

No. An API is how software talks to software. MCP sits on top: it describes your API’s actions in a way AI assistants understand, adds a standard way to sign in, and works across many assistants without custom code for each.

Build the connection once

We will scope the tools, the permissions and the hosting, and show you a working prototype early.