Connecting Letta to MCP Servers
Set up Model Context Protocol servers and configure agent connections.
Letta supports three MCP transport types depending on your deployment and use case.
Connection Methods
Section titled “Connection Methods”- ADE: Point-and-click server management via web interface
- API/SDK: Programmatic integration for production
Transport Types
Section titled “Transport Types”- Streamable HTTP (Recommended): Production-ready with auth support. Works on Cloud + self-hosted.
- SSE (Legacy): Deprecated but supported for compatibility.
- stdio (Self-hosted only): Local development and testing.
| Transport | Cloud | Self-hosted |
|---|---|---|
| Streamable HTTP | ✅ | ✅ |
| SSE | ✅ | ✅ |
| stdio | ❌ | ✅ |
Tool Execution Flow
Section titled “Tool Execution Flow”sequenceDiagram
participant A as Letta Agent
participant L as Letta Server
participant S as MCP Server
A->>L: Tool request
L->>S: MCP execute
S-->>L: Result
L-->>A: Response
Quick Start
Section titled “Quick Start”- Choose transport type based on your deployment
- Connect via ADE: Tool Manager → Add MCP Server
- Attach tools to agents
See remote servers or local servers for detailed setup.