How-to · Agents
Bridging the Gap: MCP tools and Agent Protocols
Learn how to choose between real-time MCP toolcalls and manual memory exchange blocks.
Two ways to talk to vem
vem now supports two distinct ways for agents to interact with project memory: the Model Context Protocol (MCP) for real-time tool access, and Agent Protocols (vem_pack/vem_update) for manual exchange.
MCP is ideal for interactive clients like Claude Desktop or Cursor, where the agent can call tools on its own. Agent Protocols are perfect for web-based LLMs where you paste context manually.
Universal memory exchange
By standardizing on `vem_pack` and `vem_update` blocks, we ensure that you can take your project memory to any model, regardless of its built-in tool support.
This keeps your project memory portable and gives you full control over when and how memory is updated.
- MCP for real-time, tool-enabled clients
- Agent Protocols for manual, portable context
- Unified task schema across both methods