MCPInstall

grimoire-morpho-blue

by franalgabaDevOps & Cloud

Fetches Morpho Blue public deployment metadata using the Grimoire venue CLI. Use when you need contract addresses or adapter info.

Installs
1.1K
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/franalgaba/grimoire --skill grimoire-morpho-blue
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads grimoire-morpho-blue automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Grimoire Morpho Blue Skill

Use this skill to query Morpho Blue deployment metadata and vault snapshots for spell params.

Preferred invocations:

  • grimoire venue morpho-blue ...
  • npx -y @grimoirelabs/cli venue morpho-blue ... (no-install)
  • bun run packages/cli/src/index.ts venue morpho-blue ... (repo-local)
  • grimoire-morpho-blue ... (direct binary from @grimoirelabs/venues)

Recommended preflight:

  • grimoire venue doctor --adapter morpho-blue --chain 8453 --rpc-url <rpc> --json

Use --format spell to emit a params: snapshot block.

The snapshot includes provenance fields (snapshot_at, snapshot_source) and APY data.

Use vault-liquidity for Morpho Vault V2 vault-wide withdrawal liquidity. It reads onchain Vault V2 fields, caps Morpho Market V1 liquidity-adapter assets by available underlying market cash, and does not use ERC-4626 maxWithdraw / maxRedeem, which Vault V2 intentionally returns as 0.

APY semantics:

  • apy / net_apy are decimal rates (for example 0.0408 = 4.08%).
  • When reporting, include both decimal and percent display when possible.

Commands

  • grimoire venue morpho-blue info — adapter metadata
  • grimoire venue morpho-blue addresses [--chain <id>] — contract addresses per chain
  • grimoire venue morpho-blue vaults [--chain <id>] [--asset <symbol>] [--min-tvl <usd>] [--min-apy <decimal>] [--min-net-apy <decimal>] [--sort <netApy|apy|tvl|totalAssetsUsd|name>] [--order <asc|desc>] [--limit <n>] — list and filter vaults
  • grimoire venue morpho-blue vaults-snapshot [--chain <id>] [--asset <symbol>] [--min-tvl <usd>] [--min-apy <decimal>] [--min-net-apy <decimal>] [--sort <netApy|apy|tvl|totalAssetsUsd|name>] [--order <asc|desc>] [--limit <n>] — generate spell params: block for vaults (agent-only)
  • grimoire venue morpho-blue vault-liquidity [--chain <id>] --vault <address> [--rpc-url <url>] [--format json|table|spell] — read Morpho Vault V2 withdrawable liquidity in asset units and integer bps

Examples

grimoire venue morpho-blue info --format table
grimoire venue morpho-blue addresses --chain 1
grimoire venue morpho-blue addresses --chain 8453
grimoire venue morpho-blue vaults --chain 8453 --asset USDC --min-tvl 5000000 --format table
grimoire venue morpho-blue vaults --chain 8453 --asset USDC --min-tvl 5000000 --format spell
grimoire venue morpho-blue vaults-snapshot --chain 8453 --asset USDC --min-tvl 5000000
grimoire venue morpho-blue vault-liquidity --chain 8453 --vault 0xbeef0e0834849aCC03f0089F01f4F1Eeb06873C9 --format json
grimoire venue morpho-blue vault-liquidity --chain 8453 --vault 0xbeef0e0834849aCC03f0089F01f4F1Eeb06873C9 --format spell

Use vaults-snapshot to emit a params: block for spell inputs. This is an agent-only command (output suppressed in interactive mode).

vault-liquidity --format spell emits payload-ready JSON params for protocol: morpho-vault-v2, metric: withdrawable_liquidity_bps, withdrawable_liquidity_assets, total_assets, idle_assets, liquidity_adapter, and liquidity_adapter_assets.

Example provenance output fields to preserve:

  • snapshot_at
  • snapshot_source
  • units (for example net_apy=decimal, net_apy_pct=percent, tvl_usd=usd)

Metric Surface (Spell Comparisons)

Morpho exposes the apy metric surface and supports selector-based market targeting:

morpho_apy_default = apy(morpho, USDC)
morpho_apy_market = apy(morpho, USDC, "weth-usdc-86")
morpho_apy_market_id = apy(morpho, USDC, "0x...")
morpho_apy_generic = metric("apy", morpho, USDC, "wbtc-usdc-86")
morpho_utilization_bps = metric("utilization_bps", morpho, USDC, "wbtc-usdc-86")
vault_apy = metric("vault_apy", morpho, USDC, "vault=0xVaultAddress")
vault_net_apy = metric("vault_net_apy", morpho, USDC, "vault=0xVaultAddress")
vault_withdrawable_liquidity_bps = metric("withdrawable_liquidity_bps", morpho, USDC, "vault=0xVaultAddress")

Use apy(morpho, asset[, selector]) for Morpho Blue market APY comparisons. Use metric("utilization_bps", morpho, asset[, selector]) for Morpho Blue market utilization checks. Use metric("vault_apy", morpho, asset, selector) or metric("vault_net_apy", morpho, asset, selector) for MetaMorpho vault comparisons. Use metric("withdrawable_liquidity_bps", morpho, asset, selector) for Morpho Vault V2 live withdrawal liquidity checks.

Selector behavior:

  • market no selector (apy): resolves by asset on the active chain and picks the highest-TVL match
  • config market selector: use known market ids from adapter config (for example weth-usdc-86)
  • onchain market id selector: use raw market id (0x...)
  • vault selectors (vault_apy / vault_net_apy): vault=<address|name|symbol> or bare vault address/name/symbol
  • vault_apy / vault_net_apy require explicit selector (no implicit fallback)

When multiple vaults/markets exist for one asset, pass an explicit selector for deterministic comparisons.

Spell Constraints

Morpho Blue actions do not support runtime constraints (max_slippage, etc.). Value-moving actions require an explicit market_id.

morpho_blue.lend(USDC, params.amount, "cbbtc-usdc-86")
morpho_blue.withdraw(USDC, params.amount, "cbbtc-usdc-86")
morpho_blue.borrow(USDC, params.amount) with (
  market_id="cbbtc-usdc-86",
)
morpho_blue.supply_collateral(cbBTC, params.amount, "cbbtc-usdc-86")
morpho_blue.withdraw_collateral(cbBTC, params.amount, "cbbtc-usdc-86")

Use with (market_id=...) when positional args are not convenient:

morpho_blue.lend(USDC, params.amount) with (
  market_id="0x1234...abcd",
)

Use grimoire venue morpho-blue vaults to discover available market IDs.

Action Selection Guide

Choose actions by strategy intent:

  • Supply-only strategy (no borrowing planned): prefer vault_deposit / vault_withdraw.
  • Borrowing strategy (or future borrow/repay/collateral management): use market actions with explicit market_id.

Hard rules:

  • vault_deposit / vault_withdraw require explicit vault address and do not use market_id.
  • lend, withdraw, borrow, repay, supply_collateral, withdraw_collateral require explicit market_id.
  • If vault address is missing for a vault action, do not guess: list candidate vaults and require user selection before authoring/executing.

Action Semantics

  • lend(asset, amount, market_id): lend the market loan asset (lender side).
  • withdraw(asset, amount, market_id): withdraw previously lent loan asset.
  • supply_collateral(asset, amount, market_id): post collateral for borrowing (borrower side).
  • withdraw_collateral(asset, amount, market_id): remove posted collateral.
  • borrow(asset, amount, collateral?, market_id): borrow the market loan asset.
  • repay(asset, amount, market_id): repay borrowed loan asset.
  • vault_deposit(asset, amount, vault_address): deposit into MetaMorpho vault.
  • vault_withdraw(asset, amount, vault_address): withdraw from MetaMorpho vault.

lend and supply_collateral are not interchangeable:

  • lend targets lender yield on loan asset.
  • supply_collateral is collateral management for borrowing capacity.

APY expectations:

  • lend accrues market supply APY (plus possible incentives).
  • supply_collateral does not earn market lender APY; it is risk buffer for borrow.
  • Collateral token may have its own native yield behavior (for example wstETH), separate from Morpho supply APY.

Workflow Patterns

Supply-only via vault:

morpho_blue.vault_deposit(USDC, params.amount, "0xVaultAddress")

If vault is not provided, run discovery first and ask user to pick:

grimoire venue morpho-blue vaults --chain <id> --asset <symbol> --sort netApy --order desc --limit 5 --format table

Then use the selected vault address in vault_deposit / vault_withdraw.

Borrow workflow (market):

morpho_blue.supply_collateral(WETH, params.collateral_amount, "weth-usdc-86")
morpho_blue.borrow(USDC, params.borrow_amount, WETH, "weth-usdc-86")

Unwind borrow workflow:

morpho_blue.repay(USDC, params.repay_amount, "weth-usdc-86")
morpho_blue.withdraw_collateral(WETH, params.collateral_out, "weth-usdc-86")

Lend-only via market (when explicit market control is desired):

morpho_blue.lend(USDC, params.amount, "cbbtc-usdc-86")

Default Markets

The adapter ships with pre-configured markets for Ethereum (chain 1) and Base (chain 8453):

Ethereum (chain 1)

MarketLoanCollateralLLTV
cbbtc-usdc-1USDCcbBTC86%
wbtc-usdc-1USDCWBTC86%
wsteth-weth-1WETHwstETH96.5%

Base (chain 8453)

MarketLoanCollateralLLTV
cbbtc-usdc-86USDCcbBTC86%
weth-usdc-86USDCWETH86%

Notes

  • Outputs JSON/table; vaults also supports --format spell.
  • Uses the SDK's chain address registry.
  • Prefer --format json in automation and --format table for quick triage.

FAQ

What does the grimoire-morpho-blue skill do?

Fetches Morpho Blue public deployment metadata using the Grimoire venue CLI. Use when you need contract addresses or adapter info.

How do I install grimoire-morpho-blue?

Run npx skills add https://github.com/franalgaba/grimoire --skill grimoire-morpho-blue in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/grimoire-morpho-blue/ (personal) or .claude/skills/grimoire-morpho-blue/ (project).

Which AI agents can use grimoire-morpho-blue?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is grimoire-morpho-blue safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains grimoire-morpho-blue?

It is published by franalgaba in franalgaba/grimoire. It has 1,050 recorded installs.

More from franalgaba/grimoire

View all →

grimoire-polymarket

franalgaba/grimoire

Queries Polymarket market data and CLOB state, and manages CLOB orders via the Grimoire venue CLI wrapper backed by the official Polymarket CLI.

11.9K installs

grimoire-hyperliquid

franalgaba/grimoire

Queries Hyperliquid market data using the Grimoire venue CLI. Use when you need mids, books, metadata, open orders, or a withdrawal call.

1.1K installs

grimoire

franalgaba/grimoire

Install and operate Grimoire, author .spell files with full syntax coverage (including advisory decision logic), and run compile/validate/simulate/cast safely. Use when users ask to create, edit, debug, validate, simulate, execute, or explain Grimoire strategies.

Testing & QA1.1K installs

grimoire-aave

franalgaba/grimoire

Fetches Aave V3 public market data using the Grimoire venue CLI. Use when you need Aave health checks, chain listings, market metadata, or reserve info.

Education & Science1.1K installs

grimoire-uniswap

franalgaba/grimoire

Retrieves Uniswap router metadata using the Grimoire venue CLI. Use when you need router addresses, adapter information, or Uniswap V3/V4 details.

1.1K installs

grimoire-pendle

franalgaba/grimoire

Fetches Pendle Hosted SDK metadata using the Grimoire venue CLI. Use when you need supported chains, aggregators, markets, assets, or market token details.

1K installs

Popular devops & cloud skills

View category →

microsoft-foundry

microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure

OfficialDevOps & Cloud579.1K installs

azure-diagnostics

microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.

OfficialDevOps & Cloud569.8K installs

azure-prepare

microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

OfficialDevOps & Cloud569K installs

azure-ai

microsoft/azure-skills

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.

OfficialDevOps & Cloud568.8K installs

azure-deploy

microsoft/azure-skills

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.

OfficialDevOps & Cloud568.6K installs

azure-validate

microsoft/azure-skills

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.

OfficialDevOps & Cloud568K installs