DEBYKO for AI agents

An AI client connected to DEBYKO’s MCP server reads market data from perpetual-futures venues, each value as the venue published it, and sets up Agent alerts with you: it links your Telegram, writes the condition with you, creates the rule, shows what the rule answers right now and how to turn it off.

What the AI can do

• Read: the venues, the instruments, the latest values, history, candles, a DQL screen across venues, the state of your Agent rules, and your plan with what is left of it today. Every tool is in MCP tools.
• Alerts: connect Telegram or a webhook, create, pause, resume, edit and delete rules, and turn Agent off and on, as in Alerts. These tools are turned on account by account; until they are on for yours, the AI gives you the steps to do the same by hand at https://agent.debyko.com.
• Explain: the server carries its own guides (docs://getting-started, docs://agent, docs://plans, docs://dql, docs://layers), so the AI answers “how do I…” from them, with the pages and buttons as they are.

Connect your client

The MCP server is https://mcp.debyko.com/mcp (Streamable HTTP).

• claude.ai, Claude Desktop: Customize → Connectors → + Add → Add custom connector, paste the URL, then Continue → Add → Connect. The client sends you to studio.debyko.com: sign in, check the request and press Allow.
• ChatGPT (chatgpt.com on a computer only): Plugins → + → Add custom MCP server, paste the URL, choose OAuth, then Create; it signs in the same way (Allow). Developer mode, if ChatGPT asks for it, is under Settings → Apps → Advanced settings.
• Claude Code: claude mcp add --transport http debyko https://mcp.debyko.com/mcp, then run /mcp and authenticate. With a key instead: add --header "Authorization: Bearer <key>".
• Cursor: in .cursor/mcp.json, {"mcpServers": {"debyko": {"url": "https://mcp.debyko.com/mcp"}}} signs in with OAuth; add "headers": {"Authorization": "Bearer <key>"} to use a key.
• Any MCP client that sets a header: the URL and Authorization: Bearer <key>. A new account shows its API key once, on the page Your account is open: press Copy. For another key later, open https://studio.debyko.com/account and under API key press Issue a key (or Revoke and issue new on the key you have; the old one stops working within 30 seconds).

A connection is ended under Connected applications at https://studio.debyko.com/account (End).

You need a DEBYKO account for the data that needs a key, and for alerts: Open https://studio.debyko.com/account/signin, enter your email and press Send the code, then enter the code from the email and press Sign in. The Free plan is free and needs no card. The rest is in Getting started.

A prompt to start with

Clients that show MCP prompts offer it as setup; anywhere else, paste it:

Set up DEBYKO for me. Call account to check my account and plan (if it fails because I am not signed in, give me the steps from the error’s next). Then call agent_channels: if Telegram is not linked, call agent_channel_connect with kind telegram, give me its steps, and check again after I press Start. Then help me create a first alert: make the condition concrete on a venue my plan includes, ask me for its label, create it with agent_rule_create, and show me the dry run and how to turn it off.

Limits

Every tool call counts as one request on your key, except venues and instruments (free), account (not counted against the day) and the Agent tools that set up alerts (not counted on the key: Agent’s own limits apply). What each plan allows — requests a day, venues, history, Agent rules, the shortest check interval, checks a minute, webhooks and Telegram chats — is on https://debyko.com/#pricing, and for the AI in docs://plans; both are read from the plan table the API and Agent enforce. A call refused for a limit says which one and what to do: see Errors.