Herd
Give the Sazabi agent tools to research contracts, wallets, transactions, and on-chain workflows through Herd.
All Herd integration capabilities
About
Herd is an MCP connector that gives the Sazabi agent tools to research crypto contracts, wallets, and transactions. Herd hosts an MCP server at https://mcp.herd.eco/v1 that authenticates via OAuth, so Herd controls access using your account permissions. Write operations are governed by the per-connection read-only toggle.
What the agent can do:
- Inspect contract metadata, source, deployments, and roles
- Decode transactions and review wallet activity
- Analyze wallet balances, tokens, and deployments
- Build, search, and simulate Herd HAL actions
Prerequisites
- An active Herd account
- Permission to authorize third-party OAuth applications in Herd
Set up in the dashboard
Configure connectors in the dashboard under Settings > MCP connectors.
Open the connector
Find Herd in Settings > MCP connectors.
Authorize
Start the connection; Sazabi redirects you to Herd to authorize, then back.
Set up with the CLI
You can also connect Herd with the Sazabi CLI (installed and authenticated — see sazabi mcp-connectors reference).
Herd authenticates over OAuth, so the CLI opens a browser to complete authorization:
sazabi mcp-connectors connect herdAdd --read-only to restrict the connector to read-only tools, or --project-id <project> to target a specific project. In --json mode the command prints an authorization URL to open, then polls until the connection completes. Confirm the result with sazabi mcp-connectors list.
Verify
Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools (for example, decode a transaction) and confirm it runs. If no tools appear, confirm the connection is authorized.
Troubleshooting
No tools discovered — Disconnect and reconnect from Settings > MCP connectors to restart the OAuth flow.
Connection shows needs attention — The authorization may have expired or been revoked; reconnect from Settings > MCP connectors.
Missing data or tools — The connector uses your Herd permissions. If specific resources or actions are unavailable, ask a Herd administrator to review your access.