Schema | minter-mcp

minter-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`WOC_BASE`	No	WhatsOnChain base URL	mainnet WOC
`MINTER_WIF`	No	Use an existing minter key instead of the generated file
`WALLET_URL`	No	BSV Desktop apps API URL	http://127.0.0.1:3321
`MINTER_HOME`	No	Where the minter's key lives	~/.stas-minter
`WALLET_ORIGIN`	No	Origin sent to the wallet. Must be non-admin so the spending prompt appears.	http://localhost:8080
`ALLOW_UNCONFIRMED`	No	Let a mint spend the funding tx's change without waiting a confirmation	true

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
minter_statusA	Check whether the minter can mint: its funding address and spendable balance, and whether BSV Desktop is running, signed in, and on which network. Read-only, spends nothing. Call this first.
minter_fundA	Top up the minter from the user's own BSV Desktop wallet. The wallet will show a spending-authorization prompt that the user must approve by hand. Waits for the funding to become spendable.
mint_tokenA	Mint one token into the wallet and register it so it appears in Assets within seconds (no Refresh needed). Requires the minter to be funded — check minter_status first.
mint_activate_bsv21A	Activate a BSV-21 token id with GorillaPool so WOC and overlay indexers surface it. Only needed for external discovery — the wallet already shows the token without this. Polls for the fee address, then pays it 2000 sats.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MatiasJF/minter-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server