Connect your agent in one line

One pull installs the skill and configures MCP. Same bearer token works for API and MCP. Revoking it ends both.

The one line

curl -sSL https://mintrr.app/install.sh | bash -s -- --token YOUR_TOKEN

It downloads the use-mintrr-well skill into your harness and prints the MCP config for Codex, Claude Code, Claude Desktop and Manus. It never asks for a private key and never sends your token anywhere except local config files.

1. Get a token

Ask the operator for a bearer token. It is shown once, so save it. read reads truth, dry-runs and reviews. write also generates and opens deploy sessions. Set an expiry. If a call returns 401 the token is bad, expired or revoked. If it returns 403 the scope is wrong for that route.

2. Pick your harness

One server, one header, every client. URL https://mintrr.app/mcp/, header Authorization: Bearer YOUR_TOKEN. The installer prints every block below for you.

Claude Code

claude mcp add mintrr --transport http https://mintrr.app/mcp/ --header "Authorization: Bearer YOUR_TOKEN"

Claude Desktop

"mintrr": {
  "command": "npx",
  "args": ["-y", "mcp-remote", "https://mintrr.app/mcp/",
    "--header", "Authorization: Bearer YOUR_TOKEN"]
}

Codex CLI

[mcp_servers.mintrr]
url = "https://mintrr.app/mcp/"
bearer = "YOUR_TOKEN"

Any harness, any coding agent, any AI tool

If it supports MCP and connectors, it works. Use the two lines at the top of this section: URL https://mintrr.app/mcp/, header Authorization: Bearer YOUR_TOKEN. That covers Cursor, Windsurf, Cline, Goose, Manus, Gemini and anything new.

ChatGPT web, Perplexity

These cannot attach an arbitrary remote MCP server, so there is no MCP block to paste. Use the same token against the API directly: curl https://mintrr.app/v1/templates -H "Authorization: Bearer YOUR_TOKEN". Full list at /docs and /llms.txt.

3. Skill inside MCP vs skill for MCP

Two different things with one name. The mintrr_skills tool lists modules bundled with the service for working on mintrr itself. The installed SKILL.md teaches your harness to use mintrr well: truth before design, dry-run before session, unsigned before signing. You need both. The installer sets up the second. The full text also lives at /skills/mcp-use.txt.

4. Sign in your wallet

No MCP tool signs. When a deploy is ready, open /sign.html. Proof signing is gas-free Yes or No. Deploy signing costs gas Yes or No. Your keys never leave your wallet.

Trouble

401 Invalid token: bad, expired or revoked. Ask for a fresh token.
403 read-only: that route needs a wider scope. Ask for write.
429: slow down, the token hit its per-minute limit.
Token leaked: tell the operator the label. They revoke by fingerprint and hand you a new one.