TL;DR
mcp-agent workflow, FastMCP server, or ChatGPT App backend—online. Deployments automatically run on the managed Temporal cluster; you do not need to configure Temporal hosts or queues yourself.
The sections below add a little context and point to deeper guides when you are ready.
1. Authenticate (one time)
~/.mcp-agent/credentials.json. In CI, set the MCP_API_KEY environment variable instead.
2. Confirm your project layout
Minimal structure:mcp_agent.config.yaml just needs to describe your app. You can keep execution_engine: temporal if you already use it locally, but the cloud service will always launch your code on Temporal automatically.
Example:
mcp_agent.config.yaml
mcp_agent.secrets.yaml (details in Manage secrets).
3. Deploy
--config-dir <path>– deploy from another directory.--non-interactive– reuse stored secrets (CI/CD).--dry-run– validate without uploading.
4. Check status & logs
describe prints the endpoint, auth mode, and worker status. logger tail streams application logs; add --since 30m or --grep "ERROR" as needed. All other operational commands are listed on the cloud overview.
5. Configure clients
Most deployments need per-user credentials. Prompt users (or your CI job) with:- Claude Desktop / Cursor / VS Code / ChatGPT –
uvx mcp-agent install --client <client> https://app_abc123xyz.deployments.mcp-agent.com/sse - ChatGPT Apps – deploy with
--no-authand register the SSE endpoint in the Apps dashboard. - Python – add the server endpoint to your MCP client config (see guide).
Going further
- Cloud overview – architecture, auth, observability.
- Long-running tools – design durable workflows.
- Manage secrets – developer vs. user secrets.
- Use a deployed server – client setup recipes.
