Agent treasury automation with Cursor and Forge MCP

Cursor MCP deeplink install, first vault info call, approve/deposit calldata walkthrough, test amounts, and troubleshooting on Base mainnet.

Last updated: May 25, 2026 · Published 2026-05-25

This tutorial walks through agent treasury automation with Cursor and Forge MCP — from one-click MCP install to your first vault info call, deposit calldata, and test transaction on Base mainnet. You will use the agent EOA wallet (not CDP server keys) to sign. Forge contracts are unaudited; TVL is early-stage smoke testing (~$10 as of May 2026). Read Risks & Disclosures before depositing. Full integration reference lives on Docs.

Prerequisites

• Cursor with MCP support enabled.
• Base mainnet USDC at `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` in an agent-controlled wallet.
• Small ETH balance on Base for gas (chain ID `8453`).
• Acceptance of unaudited smart-contract risk — Risks & Disclosures.

Step 1 — Install Forge MCP via deeplink

Open Docs and click the Cursor MCP install deeplink (or paste the remote Streamable HTTP config manually). Cursor → Settings → MCP should show a server named `forge-treasury` pointing at `https://mcp.forgetreasury.com/mcp`. Confirm the health endpoint separately: mcp.forgetreasury.com/health returns JSON status — do not open `/mcp` in a browser tab; it expects MCP protocol clients.

1. Visit forgetreasury.com/docs.
2. Click the Cursor deeplink button to install Forge MCP.
3. Restart or refresh MCP in Cursor if tools do not appear.
4. Verify eight Forge tools in the tool picker: `deposit`, `withdraw`, `simulate_deposit`, `get_vault_stats`, `get_balance`, `get_current_apy`, `list_profiles`, `get_forge_rewards`, `claim_forge`.

Step 2 — First vault info call

In Cursor Agent chat, prompt: *"Call Forge MCP list_profiles and get_vault_stats for conservative profile on Base mainnet."* The model should invoke MCP tools and return Core vault metadata — address `0x2C9a3922b426005B979FDD1A8F43Eb61B309193B`, share price, adapter count, chain ID 8453. Cross-check on Basescan and Stats. If `balanced` profile shows not-live, that is expected until Middle timelock — see Balanced strategy.

Step 3 — Simulate a test deposit

Prompt: *"Simulate depositing 5 USDC with profile conservative for agent address 0xYourAddress."* Review the JSON: target allocation bps across Spark/Morpho/Aave, disclaimer strings, and `totalTargetApy` if present. Tell the agent explicitly: do not combine USDC yield and FORGE boost in user-facing summaries — see FORGE emissions vs vault yield. Simulation is mandatory policy before real calldata in production agents.

Step 4 — Approve USDC (wallet step)

Forge MCP `deposit` returns vault deposit calldata only — not the ERC-20 `approve`. In Cursor, pair Forge MCP with a wallet tool (MetaMask, Cast, or viem script) to approve USDC for spender `0x2C9a3922b426005B979FDD1A8F43Eb61B309193B`. Prompt example: *"Approve 5 USDC to Forge Core vault on Base, then show me the deposit calldata from Forge MCP deposit tool."* Approval must confirm before deposit or the vault pull reverts.

1. Confirm wallet network = Base (8453).
2. Approve USDC amount ≥ deposit (5 USDC for this tutorial).
3. Wait for approve tx confirmation.
4. Proceed to deposit calldata step.

Step 5 — Deposit calldata walkthrough

Prompt: *"Use Forge MCP deposit with amount 5, agentAddress 0xYourAddress, profile conservative. Return calldata only — I will sign locally."* MCP returns encoded `ForgeVault.deposit(assets, receiver)` data. Sign and broadcast from your agent EOA — not the Forge deployer (`0x2aAbb8…`). After confirmation, call `get_balance` with your address to verify fUSDC shares. View the transaction on Basescan. First multi-adapter deposits post-P2-C0 may need ~4M gas limit — increase in wallet if simulation succeeds but broadcast fails.

Step 6 — Verify and monitor

1. Call `get_balance` — confirm fUSDC > 0.
2. Open Stats — share price and allocation bars.
3. Optional: `get_forge_rewards` for separate emission eligibility.
4. Bookmark Risks & Disclosures for any user-facing agent you ship.

Step 7 — Withdraw (optional cleanup)

To unwind the smoke test, prompt: *"Forge MCP withdraw 5 USDC worth of shares for conservative profile."* Sign withdraw calldata locally. Verify USDC returns to your EOA minus gas. Withdrawals are ERC-4626 redeem — subject to underlying adapter liquidity.

Production vs local MCP profiles

Do not point production agent policies at local MCP unless you control deployment. Local stacks may expose CDP tools — forbidden custody path for vault deposits. See MCP-native treasury for Option A custody rules.

Example Cursor prompts (copy-paste)

• *"List Forge MCP tools and describe each in one sentence."*
• *"get_vault_stats for conservative — is Core vault live on Base mainnet?"*
• *"simulate_deposit 10 USDC conservative for 0x… — show target allocation and disclaimers only."*
• *"Build deposit calldata for 10 USDC conservative; do not sign — I use MetaMask on Base."*
• *"What is the difference between vault yield and FORGE emissions for this deposit?"*

Troubleshooting

• Tools missing — Reinstall deeplink from Docs; check Cursor MCP logs.
• STRATEGY_NOT_LIVE — Use `conservative` only; Balanced needs Middle timelock.
• Deposit reverts — Missing approve, wrong chain, insufficient gas limit, or insufficient USDC.
• Wrong USDC — Must be Base native `0x833589…`, not Ethereum L1 USDC.
• MCP down — Check health URL; vault still callable via Basescan write contract.

Local full-stack MCP (optional)

Engineers running `pnpm mcp:dev` from the monorepo get a local MCP server that may merge AgentKit tools with CDP wallet helpers. Do not follow this tutorial against local MCP for vault deposits unless you understand the three-wallet model: CDP wallets are for gas experiments, not production treasury routing. Production integrators should stay on `mcp.forgetreasury.com`. See Docs for env setup and CDP local-only guidance — AgentKit complements Forge calldata tools; it does not replace agent EOA signing for vault deposits.

Next steps

Automate the flow with agent policies: Automated USDC treasury on Base, Idle USDC management, and MCP vs REST. Read Conservative strategy for adapter weights. Ship user-facing agents only with Risks & Disclosures linked in every deposit UI.