What Is MCP? The Protocol That Lets AI Use Any Tool
Until recently, AI assistants were islands. They could generate text, answer questions, write code — but they couldn't actually reach into your tools. They couldn't read your Figma files, query your database, or interact with the apps you use every day.
MCP changes that. Model Context Protocol is an open standard, created by Anthropic and now adopted across the industry, that defines exactly how an AI talks to an external tool server. It's become the USB-C of AI integrations — one standard, everything connects.
How MCP works
An MCP server is a small program that exposes a list of tools. Each tool has a name, a description, and a schema for its inputs. When an AI connects to the server, it discovers those tools and can call them by name — passing arguments, getting results.
Three transports are supported:
Local process
The AI spawns the server as a child process and communicates over stdin/stdout. Fastest for local tools — no network needed.
Remote streaming
Server-Sent Events over HTTP. Good for remote servers where the AI needs to receive streamed updates from long-running tools.
Remote stateless
Standard REST over HTTP. Simplest to host and scale. Each tool call is an independent POST request.
Why it matters
Before MCP, every AI integration was custom. If you wanted ChatGPT to read your Notion docs, someone had to build a Notion-specific plugin. Figma plugin. Jira plugin. Linear plugin. Each one different, each one maintained separately.
MCP means any tool that implements the protocol works with any AI that speaks it. Build it once, connect it anywhere. The ecosystem is growing fast — Figma, Notion, GitHub, Postgres, Slack, and dozens of others already have MCP servers.
MCP servers exist for Figma, Notion, GitHub, Postgres, Brave Search, Puppeteer, and many more. The full list is at modelcontextprotocol/servers.
How Vox uses MCP
Vox has native MCP support built in. You connect a server once from the Tools panel, hit Sync, and its tools are imported into Vox's tool library. From that point, Vox finds and uses them automatically — no prompting required.
When you say "Computer, export the icons from my Figma file," Vox searches its tool library for the right capability, finds the Figma MCP tools, calls them, and returns the result. You never had to specify which tool to use.
Put Vox to work on your computer.
Download Vox for Mac and start with the local setup flow.
macOS · Apple Silicon & Intel