Agents
What is MCP?
MCP, the Model Context Protocol, is a standard way for models and editors to call tools and read resources from a server.
Updated
How it works
- A server advertises tools and resources.
- The model or IDE calls a tool.
- The tool reads or writes your system and returns a result.
What it is not
It is not an agent framework, and it is not a database API that was never exposed as MCP.
MCP: this, and the thing it is confused with
| This | Not this | |
|---|---|---|
| Is | A protocol for tools | The agent loop itself |
| Carries | Tool calls and resources | Your whole database |
| Needs underneath | Something the tool can actually query | Nothing |
Where Pixeltable fits
Pixeltable can expose tables and queries as MCP tools. The protocol is how the editor reaches them; the tables are the memory.
Questions
- How does MCP work?
- A server advertises tools and resources. The model or IDE calls a tool. The tool reads or writes your system and returns a result.
- What is MCP often confused with?
- It is not an agent framework, and it is not a database API that was never exposed as MCP.