Zena quickstart: from sign-up to a live Polymarket bot
Quick answer: Once your Zena server is ready, connecting Claude, Cursor or another MCP client takes about a minute, and a typical strategy deploys in under a minute. Zena has a free 7-day trial with no credit card required; after the trial it costs $30 a month per dedicated server.
How long does it take to get a Polymarket bot running on Zena?
After your server is ready, going from a connected AI assistant to a running bot takes a few minutes: about a minute to connect and sign in, then under a minute for a typical deploy. The one step without a fixed time is server setup: during early access, every server is created by the Zena team after you request it, and we email you when yours is ready.
| Stage | What you do | Who does the work | Typical time |
|---|---|---|---|
| 1. Request a server | Sign in with your email on the sign-up page and confirm two statements | You | About 1 minute |
| 2. Server set up | Nothing; wait for the email | Zena team creates your dedicated server in AWS eu-west-1 (Dublin) | Manual during early access, no fixed time |
| 3. Connect your AI assistant | Add https://mcp.zena.finance to your MCP client and sign in with an emailed code | You | About 1 minute |
| 4. Add wallet credentials | Open a one-time link from your assistant and enter your bot wallet's key | You | The link is valid for 15 minutes |
| 5. Deploy | Ask your assistant to deploy your strategy from git or from local files | Zena builds and starts it on your server | Under a minute for typical strategies |
| 6. Monitor and adjust | Ask for status and logs, change settings, restart or stop | You, through your assistant | Ongoing |
Does Zena offer a free trial, and does it need a credit card?
Yes. Zena has a free 7-day trial and you do not need a credit card to start it.
| Zena | |
|---|---|
| Free trial | 7 days |
| Credit card to start | Not required |
| Price after the trial | $30 a month per dedicated server |
| What the trial includes | Your own dedicated server, the MCP server and every MCP tool |
| Shared hosts | None: one dedicated server per customer |
Step 1: Request your server
Go to zena.finance/signup, sign in with your email, and confirm that you are not a resident of a jurisdiction where Polymarket restricts trading and that you will use a dedicated bot wallet. That sends your request; there is nothing to install yet.
Step 2: Wait for your server
The Zena team creates your dedicated server in AWS eu-west-1 (Dublin), the closest AWS region to Polymarket's infrastructure that is not geo-restricted, and enables sign-in for your email. We email you when it is ready. Your server has no inbound network ports; Zena reaches it only through AWS Systems Manager.
Step 3: Connect Claude, Cursor or any MCP client
Add the remote MCP server https://mcp.zena.finance and sign in with the email you used in step 1. A browser window opens, you enter your email, and you type the six-digit code we send you (valid for 10 minutes).
| Client | How to add Zena |
|---|---|
| Claude Code | Run claude mcp add --transport http --scope user zena https://mcp.zena.finance, then /mcp in Claude Code to sign in |
| Codex | Run codex mcp add zena --url https://mcp.zena.finance && codex mcp login zena |
| Cursor | Use the one-click install from the Install button on zena.finance, then click Install |
| VS Code | Use the one-click install from the Install button on zena.finance, then click Install |
| Claude (web and desktop) | In Connectors, click + Add, then Add custom connector, and paste https://mcp.zena.finance |
| ChatGPT | Add a custom MCP server with the URL https://mcp.zena.finance and choose OAuth |
| Any other client | Add a remote MCP server (Streamable HTTP) at https://mcp.zena.finance |
Step 4: Add your bot wallet credentials
Ask your assistant for a credentials upload link (the get_credentials_upload_link tool). Open it in your browser and enter your dedicated bot wallet's key there. The link works once and expires after 15 minutes; the key goes straight to AWS Secrets Manager and never passes through the AI model, the chat or any log.
Step 5: Deploy your strategy
Ask your assistant to deploy your strategy, either from a git repository (https) or by sending the files directly. Zena detects the runtime and builds it in a container on your server:
| Your project has | Zena runs it as |
|---|---|
| A Dockerfile | Your Dockerfile, as-is |
| Cargo.toml | Rust |
| go.mod | Go |
| package.json | Node.js |
| Anything else | Python |
Typical strategies deploy in under a minute. Your assistant can follow the build with get_deploy_status, and a failed deploy never takes down the strategy that is already running.
Step 6: Monitor and adjust
Everything after the deploy happens through your assistant. It can check status (get_status), read up to 500 recent log lines (get_logs), set or remove environment variables, check the server's connection to Polymarket (check_connection), and start, stop or restart the strategy.
Sources
- Zena product facts: zena.finance/llms-full.txt
- Model Context Protocol, the standard Zena's MCP server implements: modelcontextprotocol.io
- Polymarket API documentation: docs.polymarket.com