Mcp Server
Let an AI agent on Base query DeFi yield, simulate treasury splits, and optionally manage Clicks Protocol treasury with guarded write keys.
Overview
Clicks Protocol MCP is an MCP server for the Build phase that gives AI agents on Base tools to query DeFi yield, simulate splits, and manage treasury via Clicks Protocol.
What is this MCP server?
- npm @clicks-protocol/mcp-server (package version 0.1.4 in metadata) for stdio MCP
- Read tools: query APY and simulate splits on Base; writes need CLICKS_PRIVATE_KEY
- CLICKS_RPC_URL optional, defaults to https://mainnet.base.org
- Positioned as autonomous DeFi yield for AI agents with treasury management
- Catalog server version 1.0.0 from clicks-protocol GitHub subfolder mcp-server
- Catalog server version 1.0.0 with npm package version 0.1.4 in packages array
- Default RPC URL https://mainnet.base.org when CLICKS_RPC_URL unset
- npm identifier @clicks-protocol/mcp-server
Community signal: 1 GitHub stars.
What problem does it solve?
Agent builders on Base lack a safe, structured way to expose yield and treasury actions to coding agents without custom web3 scripting every session.
Who is it for?
Indie agent developers experimenting with autonomous treasury on Base who accept on-chain risk and key hygiene.
Skip if: Builders avoiding cryptocurrency entirely, or teams that need regulated custody without self-managed private keys.
What do I get? / Deliverables
After MCP registration, agents can run read-only APY and simulation tools immediately and opt into write operations when you supply CLICKS_PRIVATE_KEY and RPC settings.
- Agent-accessible APY and split simulation results on Base
- Optional treasury register, deposit, and withdraw flows via MCP when keyed
- Documented RPC and key configuration for repeatable agent DeFi workflows
Recommended MCP Servers
Journey fit
Treasury and on-chain integration for agent products are built while defining how your agent holds and routes funds, not during initial idea research alone. Integrations fits because the MCP wraps Clicks Protocol on Base—APY reads, simulations, and wallet writes—rather than generic frontend or support tooling.
How it compares
Base DeFi treasury MCP, not traditional payment-gateway documentation or schema codegen.
Common Questions / FAQ
Who is Clicks Protocol MCP for?
Solo builders creating AI agents that need programmatic DeFi yield visibility and optional treasury actions on Base through MCP.
When should I use Clicks Protocol MCP?
Use it during build while designing how your agent queries APY, simulates allocations, and connects wallet write paths before production hardening.
How do I add Clicks Protocol MCP to my agent?
Install npm @clicks-protocol/mcp-server, configure stdio MCP, set CLICKS_RPC_URL if needed, and add CLICKS_PRIVATE_KEY only when you require write tools.