Skip to main content
Agents act through tools served by two MCP (Model Context Protocol) servers. Condor starts both for every session and decides which tools each one registers, based on who is in the seat.

The two servers

If no Hummingbot API server is available to the session, Condor starts the agent with the Condor tools only.

Which tools a seat gets

Each session runs on a profile. The profile depends on who is in the seat:
  • Trading tools cover everything a tick needs: portfolio, market data, executors, swaps, bots and controllers.
  • Liquidity tools (manage_amm, manage_clmm) move liquidity directly, outside an executor. A tick doesn’t get them.
  • Admin tools (configure_server, manage_gateway_config) are operator actions. If you don’t own the server the chat is pointed at, the chat drops to the agent profile and loses them.
  • Orchestration tools (manage_agents, manage_loops, control_agent, get_available_models) create agents and start loops. A tick doesn’t get them, because it is running inside the loop they control.
On the tick and agent profiles, manage_controllers refuses to upload controller code. Agents manage controller code with manage_agent_controllers instead. Saved configs still work.

Narrowing an agent’s tools

Two things can remove tools from the profile. Neither can add a tool the profile doesn’t have.
  • The tools: allowlist in AGENT.md. When the list has entries, every tool it doesn’t name is removed. Leave it empty for the whole profile. Names can be plain (get_prices) or namespaced (mcp__condor__delegate). Condor only compares the part after the last __.
  • Operator mutes. Tools you switch off for an agent, saved in .condor/agents/<slug>/mutes.yml.
Removed tools are never registered, so the model isn’t told they exist. A name that matches no tool is silently ignored, so check the spelling of every name in an allowlist. The old name manage_strategies still counts as manage_loops. Architecture shows where the tools: list goes in AGENT.md.

Tools that move money

Some calls need approval before they run: creating or stopping an executor, changing leverage, execute_swap, manage_clmm and manage_amm actions that move liquidity, manage_bots deploy, stop, start and config-update actions, and control_agent start. In a chat, Condor asks you to confirm them. In a loop, the risk gate checks each one against the session’s limits. There is no place_order tool. The risk gate refuses that name outright, as it does an upload of raw controller code through manage_controllers.

Hummingbot API tools

Portfolio and history

Market data

There is no order book or funding rate tool. For anything you need to compute on, such as indicators or cross-venue comparisons, agents use client.market_data.* inside run_code.

Executors

Each create_*_executor tool takes an optional controller_id, the tag that owns the executor (default main). In a loop, the risk gate only allows creates that carry the session’s own ID.

Held and orphaned positions

DEX swaps

Bots and controllers

Direct liquidity

Admin

When Condor starts the server, configure_server can only show the current connection. Condor passes in the server owner’s credentials, so the tool refuses to change the connection. Add or switch servers in the Workspace under Settings → Servers.

Condor tools

Skills, memory and journal

Code, routines and controllers

run_code and manage_routines run Python in the Condor process with an unrestricted API client. A dry run refuses both.

Agents and loops

Servers and notifications

Configuration

When Condor starts mcp-hummingbot, it passes the server’s URL and the owner’s credentials itself. You don’t need to configure anything. When you run the server on its own, for example from another MCP host, it reads its connection in this order:
  1. ~/.hummingbot_mcp/server.yml, if the file exists. configure_server writes this file. When it exists, the connection variables below are ignored.
  2. Otherwise, these environment variables:
These variables apply either way: A standalone server runs the full profile unless you pass --profile tick or --profile agent.

Running the servers by hand

Condor starts both servers for each session. To run one yourself from the Condor folder: