MCP Agent Cloud is currently in open beta. Follow the instructions below to get started. For feedback, issues and feature requests, visit https://github.com/lastmile-ai/mcp-agent/issues or join our Discord at https://lmai.link/discord/mcp-agent.
Prerequisites
Before you begin, make sure you have:mcp-agent installed
A working agent
An mcp-agent project that runs locally
Quick Start
1
Authenticate
Log in to MCP Agent Cloud:This will direct you to the API keys page for obtaining credentials.
2
Prepare Your Project
Ensure your project has the required configuration files:
mcp_agent.config.yaml
[!IMPORTANT] Swap your api_key with !developer_secret to mark what keys will be saved as secrets within mcp-agent cloud.
mcp_agent.secrets.yaml
3
Deploy
Deploy your agent with a single command:The deployment process will:
- Check for existing app with this name or create a new one
- Process your secrets file (transforming !developer_secret tags to secure handles)
- Bundle and upload your code using Wrangler
- Deploy to MCP Agent Cloud’s managed infrastructure
4
Test Your Deployment
List your deployed agents:Test your agent:
The
cloud logger tail
command is your best friend for debugging deployments. Use --follow
to stream logs in real-time and --grep
to filter for specific patterns.Your First Cloud Workflow
Let’s create and deploy a simple agent that can fetch web content and summarize it.Create the Agent
Deploy to Cloud
Use Your Cloud Agent
Your agent is now available as an MCP server. Here’s how to use it:First configure the agent (this handles authentication and user secrets):Then add to your Claude Desktop config (Restart Claude Desktop and your agent will appear in the tools menu.
~/.claude-desktop/config.json
):Advanced Deployment Options
Deployment Configuration
Control your deployment with additional options:Environment Variables
Environment variables for the CLI:Secrets Management
MCP Agent Cloud securely handles secrets through themcp_agent.secrets.yaml
file:
!developer_secret
are:
- Prompted for if not already stored
- Securely uploaded to MCP Agent Cloud’s vault
- Referenced by handle in the deployed configuration
Testing with MCP Inspector
MCP Inspector is a powerful tool for testing and debugging your deployed MCP servers. It provides a web interface to interact with your agent’s tools and resources.
Using MCP Inspector
Test your deployed agent with the MCP Inspector:- Open MCP Inspector: Visit https://modelcontextprotocol.io/inspector
-
Connect to your server:
- Select “SSE” as the transport
- Enter your server URL, and append “/sse”
- Add the required authentication headers (
Bearer $MCP_AGENT_CLOUD_API_KEY
)
-
Test your tools:
- Browse available tools and resources
- Execute tool calls interactively
- View request/response payloads
- Debug workflow executions
MCP Inspector is especially useful for:
- Testing tool implementations before integrating with clients
- Debugging authentication issues
- Understanding the exact payloads your agent expects
- Verifying workflow execution flows
Managing Deployments
View Deployments
Monitor Workflows
View Logs
Update Deployment
Delete Deployment
Client Integration
Help users connect to your deployed agent:Best Practices
Use Temporal Execution Engine
Use Temporal Execution Engine
Always set
execution_engine: temporal
in your config for cloud deployments. This enables durable execution and workflow management.Implement Health Checks
Implement Health Checks
Add health check endpoints to your workflows for better monitoring:
Use Structured Logging
Use Structured Logging
Use the app logger for better observability:
Handle Secrets Properly
Handle Secrets Properly
Never hardcode secrets. Use environment variables or the secrets store:
Version Your Deployments
Version Your Deployments
Tag your deployments for easy rollback:
Troubleshooting
Deployment Fails
Deployment Fails
Check build logs:Common issues:
- Missing dependencies in requirements.txt
- Invalid configuration syntax
- Missing required secrets
Workflow Not Starting
Workflow Not Starting
Verify worker is running:Check for “Workers: Running” in the output.
Authentication Issues
Authentication Issues
Refresh your authentication:
Connection Timeouts
Connection Timeouts
Check your network and firewall settings. MCP Agent Cloud requires:
- HTTPS (port 443) for API access
- WebSocket support for real-time features
Example Projects
Explore complete examples:Basic Agent Examples
Simple agents with MCP servers
Workflow Patterns
All workflow pattern implementations
MCP Agent Server
Agent-as-server examples
Temporal Examples
Durable workflow examples