Connects GitHub Copilot and VS Code to Letta agents for enhanced development assistance
Enables cloud deployment and hosting of the Letta MCP server with auto-scaling, zero-downtime deploys, and built-in monitoring
Provides integration with Replit development environment through MCP-compatible endpoint configuration
🚂 Letta MCP Server Railway Edition
Cloud-optimized HTTP transport edition of Letta MCP Server - Deploy to Railway in 30 seconds.
Universal MCP server connecting any AI client to Letta.ai's powerful stateful agents via streamable HTTP for seamless cloud deployment.
🚀 Quick Deploy to Railway
Prerequisites
- Letta API key from api.letta.com (free tier available)
- Railway account (free tier includes 500 hours/month)
One-Click Deployment
- Click the deploy button above
- Connect your GitHub account to Railway
- Add environment variable:
LETTA_API_KEY=your_letta_api_key_here
- Deploy - your MCP server will be live in under 2 minutes!
Your MCP Server URL
⚡ Integration with AI Clients
Claude Desktop (ADE Integration)
Add to your Claude Desktop configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json
MCP Inspector Testing
Test your deployment with the MCP Inspector:
GitHub Copilot & VS Code
Other MCP Clients
- Cursor: Add server to MCP configuration
- Replit: Use MCP-compatible endpoint configuration
- Sourcegraph Cody: Configure via OpenCtx bridge
- Any MCP Client: Use streamable HTTP transport
🔧 Configuration
Environment Variables
Variable | Required | Default | Description |
---|---|---|---|
LETTA_API_KEY | ✅ Yes | - | Your Letta API key from api.letta.com |
LETTA_BASE_URL | No | https://api.letta.com | Letta API endpoint (for self-hosted) |
PORT | No | 8000 | Railway auto-assigns this |
LETTA_TIMEOUT | No | 60 | Request timeout in seconds |
LETTA_MAX_RETRIES | No | 3 | Max retry attempts for failed requests |
Letta Cloud Setup
- Sign up: Create account at letta.com
- Get API key: Visit api.letta.com → Settings → API Keys
- Create agent: Use the web interface to create your first agent
- Test connection: Use
letta_health_check
tool to verify
🛠️ Available Tools (20+ Letta Functions)
🤖 Agent Management
letta_list_agents
- List all agents with pagination and filteringletta_create_agent
- Create new agents with memory blocks and toolsletta_get_agent
- Get detailed agent informationletta_update_agent
- Update agent configuration (name, description, model)letta_delete_agent
- Safely delete agents with confirmation
💬 Conversations
letta_send_message
- Send messages to agents with streaming supportletta_get_conversation_history
- Retrieve chat history with paginationletta_export_conversation
- Export conversations (markdown, JSON, text)
🧠 Memory Management
letta_get_memory
- View all memory blocks for an agentletta_update_memory
- Update memory blocks (human, persona, custom)letta_create_memory_block
- Create custom memory blocksletta_search_memory
- Search through agent conversation memory
🔧 Tool Management
letta_list_tools
- List all available tools with filteringletta_get_agent_tools
- View tools attached to specific agentsletta_attach_tool
- Add tools to agentsletta_detach_tool
- Remove tools from agents
📊 Monitoring & Health
letta_health_check
- Verify API connection and service statusletta_get_usage_stats
- Get usage statistics and analytics
🏗️ Technical Architecture
Railway-Optimized Features
- Streamable HTTP Transport: Optimized for cloud deployment vs stdio
- Connection Pooling: Maintains persistent connections for performance
- Auto-scaling: Railway automatically scales based on demand
- Zero-downtime Deploys: Hot reloading without connection loss
- Built-in Monitoring: Railway dashboard shows metrics and logs
Performance Optimizations
Transport Comparison
Feature | stdio (local) | streamable-http (Railway) |
---|---|---|
Cloud deployment | ❌ No | ✅ Yes |
Load balancing | ❌ No | ✅ Auto |
Horizontal scaling | ❌ No | ✅ Yes |
Health monitoring | ❌ Limited | ✅ Full |
Zero-downtime deploys | ❌ No | ✅ Yes |
💻 Local Development
Quick Local Setup
Local Testing
Development Commands
🔍 Troubleshooting
Common Issues
1. "Connection refused" error
2. "Invalid API key" error
3. "Timeout" errors
4. Claude Desktop not connecting
- Restart Claude Desktop after configuration changes
- Check configuration file syntax with a JSON validator
- Verify the URL is accessible from your browser
Getting Help
- Check Railway logs: View deployment logs in Railway dashboard
- Test health endpoint: Visit
https://your-app.up.railway.app/health
- Verify MCP endpoint: Test with MCP Inspector
- Community support: Join Letta Discord
- Report issues: GitHub Issues
🚀 Production Deployment
Railway Deployment Best Practices
Environment Management
Health Monitoring
Railway provides built-in monitoring, but you can also:
- Set up custom health checks
- Monitor response times and error rates
- Configure alerts for downtime
Scaling Configuration
📖 Resources
Documentation
- Letta Documentation - Complete Letta platform guide
- MCP Specification - Model Context Protocol standard
- Railway Documentation - Railway platform guide
- FastMCP Documentation - HTTP transport framework
Community & Support
- Letta Discord - Active community support
- MCP Community - Protocol development
- Railway Community - Deployment support
- GitHub Issues - Bug reports and features
Examples & Tutorials
- Letta Agent Examples - Sample agent configurations
- MCP Client Integration - Client setup guides
- Railway Templates - Deployment templates
🤝 Contributing
We welcome contributions to make Letta MCP Server Railway even better!
Quick Contribution Guide
- Fork the repository
- Create a feature branch:
git checkout -b feature/amazing-feature
- Make your changes and add tests
- Test locally:
pytest tests/
- Commit with clear messages:
git commit -m "Add amazing feature"
- Push to your fork:
git push origin feature/amazing-feature
- Submit a Pull Request
Development Setup
Areas We Need Help
- 📖 Documentation improvements
- 🧪 Additional test coverage
- 🔧 Railway deployment optimizations
- 🌐 Multi-language client examples
- 🐛 Bug fixes and performance improvements
📜 License
MIT License - see LICENSE for details.
🙏 Acknowledgments
Built with ❤️ by the community for seamless AI agent deployment.
Special Thanks:
- Letta.ai for revolutionary stateful agents
- Railway for exceptional deployment platform
- Anthropic for MCP specification leadership
- FastMCP for HTTP transport framework
- All contributors making this project possible
This server cannot be installed
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
Enables AI clients to interact with Letta.ai's stateful agents via cloud deployment on Railway. Provides 20+ tools for agent management, conversations, memory operations, and tool configuration through a streamable HTTP transport optimized for production use.
Related MCP Servers
- AsecurityAlicenseAqualityEnables AI agents to manage issues, projects, and teams on the Linear platform programmatically.Last updated -783MIT License
- -securityFlicense-qualityIntegrates with the AgentCraft framework to enable secure communication and data exchange between AI agents, supporting both premade and custom enterprise AI agents.Last updated -1
- -securityFlicense-qualityA production-ready server that connects LLMs and AI agents (Claude, ChatGPT) to Amazon Redshift databases with configurable access controls and zero code changes.Last updated -3
Railway MCP Serverofficial
AsecurityAlicenseAqualityEnables interaction with Railway cloud platform through the CLI to manage projects, services, deployments, and environments. Supports creating projects, deploying templates, managing environment variables, and monitoring logs through natural language commands.Last updated -1343944MIT License