Adding mcp-agent cloud deployment instructions

Author: andrew-lastmile

examples/mcp_agent_server/asyncio/README.md

@@ -152,6 +152,81 @@ uv run client.py
 uv run client.py --custom-fastmcp-settings
 ```
 
+### [Beta] Deploying to mcp-agent cloud
+
+You can deploy your MCP-Agent app as a hosted mcp-agent app in the Cloud.
+
+1. Update the *mcp_agent.secrets.yaml* file specifying deployed secrets:
+
+```
+openai:
+  api_key: !developer_secret
+
+anthropic:
+  api_key: !developer_secret
+```
+
+2. In your terminal, authenticate into mcp-agent cloud by running:
+```
+uv run mcp-agent login
+```
+
+3. You will be redirected to the login page, create an mcp-agent cloud account through Google or Github
+
+4. Set up your mcp-agent cloud API Key and copy & paste it into your terminal
+
+```
+andrew_lm@Mac sdk-cloud % uv run mcp-agent login
+INFO: Directing to MCP Agent Cloud API login...
+Please enter your API key 🔑: 
+```
+
+5. In your terminal, deploy the MCP app:
+```
+uv run mcp-agent deploy mcp_agent_server -c /absolute/path/to/your/project
+```
+
+6. In the terminal, ou will then be prompted to specify your OpenAI and/or Anthropic keys:
+
+Once the deployment is successful, you should see the following:
+```
+andrew_lm@Mac sdk-cloud % uv run mcp-agent deploy basic_agent_server -c /Users/andrew_lm/Documents/GitHub/mcp-agent/examples/mcp_agent_server/asyncio/
+╭─────────────────────────────────────────────────── MCP Agent Deployment ────────────────────────────────────────────────────╮
+│ Configuration: /Users/andrew_lm/Documents/GitHub/mcp-agent/examples/mcp_agent_server/asyncio/mcp_agent.config.yaml │
+│ Secrets file: /Users/andrew_lm/Documents/GitHub/mcp-agent/examples/mcp_agent_server/asyncio/mcp_agent.secrets.yaml │
+│ Mode: DEPLOY                                                                                                                │
+╰──────────────────────────────────────────────────────── LastMile AI ────────────────────────────────────────────────────────╯
+INFO: Using API at https://mcp-agent.com/api
+INFO: Checking for existing app ID for 'basic_agent_server'...
+SUCCESS: Found existing app with ID: app_dd3a033d-4f4b-4e33-b82c-aad9ec43c52f for name 'basic_agent_server'
+INFO: Processing secrets file...
+INFO: Found existing transformed secrets to use where applicable: 
+/Users/andrew_lm/Documents/GitHub/mcp-agent/examples/mcp_agent_server/asyncio/mcp_agent.deployed.secrets.yaml
+INFO: Loaded existing secrets configuration for reuse
+INFO: Reusing existing developer secret handle at 'openai.api_key': mcpac_sc_83d412fd-083e-4174-89b4-ecebb1e4cae9
+INFO: Transformed config written to /Users/andrew_lm/Documents/GitHub/mcp-agent/examples/mcp_agent_server/asyncio/mcp_agent.deployed.secrets.yaml
+
+                  Secrets Processing Summary                   
+┏━━━━━━━━━━━┳━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━┓
+┃   Type    ┃ Path           ┃ Handle/Status       ┃  Source  ┃
+┡━━━━━━━━━━━╇━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━┩
+│ Developer │ openai.api_key │ mcpac_sc...b1e4qwe9 │ ♻️ Reused │
+└───────────┴────────────────┴─────────────────────┴──────────┘
+
+Summary: 0 new secrets created, 1 existing secrets reused
+SUCCESS: Secrets file processed successfully
+INFO: Transformed secrets file written to /Users/andrew_lm/Documents/GitHub/mcp-agent/examples/mcp_agent_server/asyncio/mcp_agent.deployed.secrets.yaml
+╭───────────────────────────────────────── Deployment Ready ───────────────────────────────────────────────╮
+│ Ready to deploy MCP Agent with processed configuration                                                   │
+╰──────────────────────────────────────────────────────────────────────────────────────────────────────────╯
+WARNING: Found a __main__ entrypoint in main.py. This will be ignored in the deployment.
+▰▰▰▰▰▰▱ ✅ Bundled successfully
+▹▹▹▹▹ Deploying MCP App bundle...INFO: App ID: app_ddde033d-21as-fe3s-b82c-aaae4243c52f
+INFO: App URL: https://770xdsp22y321prwv9rasdfasd9l5zj5.deployments.mcp-agent-cloud.lastmileai.dev
+INFO: App Status: OFFLINE
+▹▹▹▹▹ ✅ MCP App deployed successfully!
+```
+
 ## Receiving Server Logs in the Client
 
 The server advertises the `logging` capability (via `logging/setLevel`) and forwards its structured logs upstream using `notifications/message`. To receive these logs in a client session, pass a `logging_callback` when constructing the client session and set the desired level: