Summary
Keeping actions and events as separate tools matches how Mina zkApps actually work, and merging them would have destroyed the distinction.
On Mina an action is an input a zkApp reduces over and an event is an output it emits, and a developer debugging a zkApp is almost always asking about one specifically. A generic 'query the chain' tool would force the caller to filter for the distinction that mattered most. Narrow surface aimed at people building on one chain, and it does not pretend otherwise — three tools, read-only, no wallet involved.
What it is
A three-tool client over a Mina Archive Node: filtered queries for actions and for events, plus the current network state.
What you get
- query-actions and query-events are separate because on Mina they are separate things — actions are the sequenced inputs a zkApp consumes, events are what it emits.
- Both accept filters, so a query narrows to a contract or a range rather than returning everything the archive holds.
- get-network-state returns the chain's current position, which is what makes an archive result interpretable.
Requirements
Nothing to supply — it reads a public archive node.
Setup effort
One command — npx mcp-mina-archive-node