@@ -96,3 +96,97 @@ Run your MCP Agent app:
9696` ` ` bash
9797uv run main.py 
9898` ` ` 
99+ # # `4` [Beta] Deploy to MCP Agent Cloud
100+ 
101+ # ## Prerequisites
102+ Make sure your agent is cloud-compatible with the `@app.tool` decorator (already included in this example). 
103+ 
104+ # ## Step 1: Login to MCP Agent Cloud
105+ 
106+ ` ` ` bash
107+ uv run mcp-agent login 
108+ ` ` ` 
109+ 
110+ 
111+ # ## Step 2: Deploy your agent
112+ 
113+ ` ` ` bash
114+ uv run mcp-agent deploy basic-slack-agent 
115+ ` ` ` 
116+ 
117+ During deployment, you'll be prompted to configure secrets. You'll see two options for each secret :
118+ 
119+ # ### For OpenAI API Key:
120+ ``` 
121+ Select secret type for 'openai.api_key'
122+ 1: Deployment Secret: The secret value will be stored securely and accessible to the deployed application runtime.
123+ 2: User Secret: No secret value will be stored. The 'configure' command must be used to create a configured application with this secret.
124+ 
125+ ``` 
126+ Recommendation: 
127+ - Choose Option 1 if you're deploying for personal use and want immediate functionality 
128+ - Choose Option 2 if you're sharing this agent publicly and want users to provide their own OpenAI API keys 
129+ 
130+ #### For Slack Bot Token: 
131+ ``` 
132+ Select secret type for 'mcp.servers.slack.env.SLACK_BOT_TOKEN'
133+ 1: Deployment Secret: The secret value will be stored securely and accessible to the deployed application runtime.
134+ 2: User Secret: No secret value will be stored. The 'configure' command must be used to create a configured application with this secret.
135+ 
136+ ``` 
137+ Recommendation: 
138+ - Choose Option 1 if you're deploying for your own Slack workspace and want the agent to work immediately 
139+ - Choose Option 2 if you're sharing this agent publicly and want each user to connect their own Slack workspace 
140+ 
141+ ### Step 3: Connect to your deployed agent 
142+ 
143+ Once deployed, you'll receive a deployment URL like: `https://[your-agent-server-id].deployments.mcp-agent.com` 
144+ 
145+ #### Claude Desktop Integration 
146+ 
147+ Configure Claude Desktop to access your agent by updating your `~/.claude-desktop/config.json`: 
148+ 
149+ ```json 
150+ { 
151+   "mcpServers": { 
152+     "basic-slack-agent": { 
153+       "command": "/path/to/npx", 
154+       "args": [ 
155+         "mcp-remote", 
156+         "https://[your-agent-server-id].deployments.mcp-agent.com/sse", 
157+         "--header", 
158+         "Authorization: Bearer ${BEARER_TOKEN}" 
159+       ], 
160+       "env": { 
161+         "BEARER_TOKEN": "your-mcp-agent-cloud-api-token" 
162+       } 
163+     } 
164+   } 
165+ } 
166+ ``` 
167+ 
168+ #### MCP Inspector  
169+ 
170+ Test your deployed agent using MCP Inspector:
171+ 
172+ ``` bash 
173+ npx @modelcontextprotocol/inspector
174+ ``` 
175+ 
176+ Configure the inspector with these settings:
177+ 
178+ |  Setting |  Value | 
179+ | ---------| -------| 
180+ |  Transport Type |  SSE | 
181+ |  SSE URL |  ` https://[your-agent-server-id].deployments.mcp-agent.com/sse `  | 
182+ |  Header Name |  Authorization | 
183+ |  Bearer Token |  your-mcp-agent-cloud-api-token | 
184+ 
185+ ** Tip:**  Increase the request timeout in the Configuration since LLM calls take longer than simple API calls.
186+ 
187+ ### Available Tools  
188+ 
189+ Once deployed, your agent will expose the ` fetch_latest_slack_message `  tool, which:
190+ -  Fetches the latest message from the bot-commits channel
191+ -  Provides an AI-generated summary of the message content
192+ -  Returns both the original message and summary
0 commit comments