What is MCP server?

An MCP server is a process that exposes tools, resources, and prompts to LLM clients over the Model Context Protocol — an open standard (introduced by Anthropic, widely adopted across the industry by 2026) for connecting AI assistants to external systems without bespoke per-vendor integrations.

Also known as: Model Context Protocol server, MCP, MCP integration

The problem MCP solves

Before MCP, every tool integration was bespoke per LLM provider: write OpenAI function definitions for ChatGPT, Anthropic tool definitions for Claude, custom schemas for everyone else. MCP replaces this with one server interface that any compliant LLM client can connect to — the same way HTTP replaced bespoke protocols between web clients and servers.

What an MCP server exposes

Three things: (1) Tools — functions the LLM can invoke (read a file, query a database, call an API). (2) Resources — content the LLM can read (file contents, search results, sensor data). (3) Prompts — reusable prompt templates the user or LLM can invoke. The MCP client negotiates available capabilities at connection time.

Where MCP servers run

Locally (stdio transport) — common for filesystem, git, IDE integrations. Remotely (HTTP/SSE or WebSocket transport) — common for SaaS integrations (Linear, Slack, Notion, Stripe). The protocol is transport-agnostic; what matters is the JSON-RPC message shape.

Adoption in 2026

Claude Code, Cursor, Continue, and most major IDE-AI integrations support MCP natively. OpenAI added MCP support in 2025. There are hundreds of community-maintained MCP servers for popular SaaS tools. For developers, writing an MCP server is a more durable investment than writing per-vendor integrations because the same server works across every compliant client.

Last updated · First published

Related terms

Try MCP server in vMira

Open the workspace and explore — no credit card required.

Open vMira