# Using mintrr MCP well

This file is served at https://mintrr.app/skills/mcp-use.txt and installed as
SKILL.md by https://mintrr.app/install.sh. Single source: edit here, the
installer fetches this URL. It is not in skills/manifest.json and never should
be. That manifest indexes modules for developing mintrr itself. This file is
for anyone's harness to use mintrr well. Different readers, different index.

This skill is the client-side companion to the server-side tool list. The
server decides what exists. This file decides the order to use it in.

For a human-facing visual overview of the command line and optional terminal
workbench, see https://mintrr.app/cli.html. Its illustrated draft is not a live
session, a capability discovery response or permission to execute an action.

## Auth

One bearer token for API and MCP. Send it on every MCP request:

```
Authorization: Bearer <token>
```

No header means refusal, never a default identity. A token is shown once at
creation and revoked by fingerprint. Never paste a token into chat.

Scopes: `read` reads truth, dry-runs and reviews, but designs nothing.
`write` generates, compiles and opens deploy sessions. `agent` drafts plans
only. Admin never leaves the operator.

## Order of tools

Ask chain truth before designing. A refusal is a correct answer, not a failure.

1. `mintrr_suggest_pattern` for the intent, before anything else.
2. `mintrr_capabilities`, `mintrr_guardrails`, `mintrr_explain_limits` for the
   chain. Do not assume a chain supports something.
3. `mintrr_templates` to pick a first-party template.
4. `mintrr_dry_run` for gas, roles and address preview. Nothing signs here.
5. `mintrr_session_create` then `mintrr_session_step` with one of
   confirm-review, dry-run, unsigned, broadcast, verify, status. Unknown
   actions are refused with the valid verbs named.
6. `mintrr_plan_compose` and `mintrr_plan_refine` need an agent token. A write
   token gets 403 there, which is the service refusing an escalation. Compose
   also needs `owner_address`: the drafted plans are built for that deploy
   owner, so pass the real address rather than a placeholder.

## Signing

No MCP tool signs. A validated session can prepare an unsigned transaction and
relay externally signed bytes through an authorized broadcast step. The human signs in their own
wallet, on their own machine, then the signed bytes go back through
`broadcast`. For the wallet popup flow, point the human at `/sign.html`:
proof signing is gas-free Yes or No, deploy signing costs gas Yes or No.

## Facts that must stay true

- Say verified, never audited.
- Only `supported` chains appear in capability claims. Arc mainnet is live;
  TRON remains code-complete and pending mainnet proof.
- The gas payer never becomes the owner.
- A missing fact is a refusal with the reason named, not a guess.