Skip to main content
Glama
CTRLabs

CTRL MCP

Official
by CTRLabs

ctrl-mcp

the mcp for on-chain automation. sign once, agent does the rest, forever.

ctrl is workflow automation for on-chain actions on base. you compose trigger → action → condition graphs in plain english, sign one batch to deploy a vault + spending caps, and a keeper runs your workflow under those caps forever.

this is the mcp surface. agents talk to it. users sign in their wallet.

$ claude mcp add ctrl https://ctrl.build/api/mcp

or paste into your client's mcp config:

{
  "mcpServers": {
    "ctrl": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://ctrl.build/api/mcp",
               "--header", "Authorization:Bearer ${CTRL_API_KEY}"],
      "env": { "CTRL_API_KEY": "sk_ctrl_..." }
    }
  }
}

mint a key at ctrl.build/settings/api-keys.

prompt your agent. that's it.

Related MCP server: agentshield-mcp

what your agent gets

seven tools. that's it.

tool

what it does

ctrl_get_vault_status

read user's vault address, balance, active rules

ctrl_get_block_catalog

live list of every block + field schema

ctrl_create_workflow

assemble + save a workflow draft from a prompt

ctrl_activate

encode the eip-5792 batch the user signs to deploy

ctrl_withdraw

encode the batch to pull funds out of the vault back to the user's wallet (eth, weth, or any erc-20)

ctrl_fire_manual

fire a workflow once for testing — no waiting

ctrl_get_execution_logs

basescan tx hashes, gas, status — keeper history

24 blocks under the hood

triggerstime.interval, trigger.manual, price.above/below/change, pool.created (clanker / flaunch / zora / bankr), watch.whale, event.transfer, event.balance, trending.token

actionscypher.swap, read.balance, notify.telegram, notify.discord, util.webhook

conditionscond.price, cond.balance, cond.allowed_weekdays, cond.time_window

utilitiesutil.delay, util.note, util.log, util.stop, util.snapshot

the agent calls ctrl_get_block_catalog first to see the live shape. every block id maps 1:1 to keeper execution.

example prompts

drop these into your agent and watch:

  • "dca $50 eth into usdc every monday at 14:00 utc"

  • "snipe new flaunch launches with milady in the name, 0.005 eth each, auto-sell at 2x"

  • "watch wallet 0x6cc5...c01b. when they buy anything over $10k, copy with 0.01 eth"

  • "sell 50% of my pepe if price drops 20% in an hour"

  • "every monday noon, check moonwell usdc apy. if lower than morpho by 1%, move 80%"

security

vault-direct model. agent never holds keys.

  • on-chain caps: every rule signs immutable maxPerSwap + maxPerDay. enforced by the vault contract.

  • kill switches: pauseVault() halts everything; revokeRule(id) kills one workflow. both 1-tx, user-callable.

  • safety primitives: pool.created runs goplus honeypot + tax + score checks before any swap.

  • keeper bounded: the keeper fleet can only call methods the vault permits. compromised keeper costs at most one tick's per-swap cap.

verified contracts on base:

ecosystem

works with any mcp client. tested with:


mit

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    AI-to-AI economic marketplace with on-chain USDC escrow on Base L2. Agents browse skills, hire each other, manage jobs, release payments, and handle disputes via AI Judge. 15 MCP tools, reputation scoring.
    15
    3
    MIT
  • F
    license
    A
    quality
    Not graded
    maintenance
    Trust infrastructure for AI agents on Base. DEX Spread Oracle (live Uniswap V3 prices), on-chain escrow, insurance pool, and collective knowledge base. 7 smart contracts. Pay-per-query via x402 micropayments in USDC.
    6
    -
  • F
    license
    Not graded
    quality
    B
    maintenance
    Settlement rails for AI labor — USDC escrow on Base Mainnet, 1% protocol fee, designed for autonomous agents. 10 MCP tools covering the full escrow lifecycle: * Quoting calldata for create-intent, submit-proof, release-funds (broadcast gated) * Single-call x402 payment binding (replaces the 5-step x402 dance with one HMAC-signed POST) * Server-side reputation from on-chain event scan * Li
    -