Model Context Protocol (MCP)
Also known as: MCP
The Model Context Protocol (MCP) is a standard way for an agent like Claude to call tools that live on your machine. An app exposes a small set of tools over MCP, and any MCP-capable agent can drive them without a custom integration.
Why it matters
MCP matters because it turns an app from something you click into something an agent can call. Before it, wiring a tool into an assistant meant a bespoke integration for each one. With a shared protocol, any MCP-capable agent can discover and use an app's tools, so the interesting workflows come from combining tools rather than building glue.
In practice
Register the app's MCP server with your agent client once, then ask for what you want in plain language and let the agent call the tools. Because the server can run locally over stdio, the whole exchange can stay on your machine.
How Vocast handles this
Vocast ships a local MCP server over stdio, so an agent like Claude can call its tools, including clone_voice and denoise, entirely on your Mac.