{
  "markdown": "# Hermai MCP\n\nDedicated Model Context Protocol server for Hermai.\n\nUse this package when an agent runtime supports MCP and should call Hermai as native tools. The Hermai CLI is a separate human/operator tool and is not required for MCP.\n\n## Install\n\nRun directly with `npx`:\n\n```bash\nnpx -y hermai-mcp\n```\n\nOr install globally:\n\n```bash\nnpm install -g hermai-mcp\nhermai-mcp\n```\n\n## MCP Client Config\n\n```json\n{\n  \"mcpServers\": {\n    \"hermai\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"hermai-mcp\"]\n    }\n  }\n}\n```\n\nOptional environment variables:\n\n- `HERMAI_API_BASE` or `HERMAI_PLATFORM_URL`: API base URL. Defaults to `https://api.hermai.ai`.\n- `HERMAI_API_KEY` or `HERMAI_PLATFORM_KEY`: API key for authenticated Hermai APIs. Public schema lookup and schema-request intake work without a key. Setting a key also unlocks the `fetch_schema` execution tool (see below).\n- `HERMAI_FETCH_TIMEOUT_MS`: request timeout for `fetch_schema`. Defaults to `120000` (hosted fetch lanes can run tens of seconds).\n\n## Claude Code workflow\n\nUse the local MCP server when you want Claude Code to discover a schema, inspect\nthe available workflow, and make an authenticated read request. Hermai MCP is a\nlocal stdio server. It is not a remote Claude connector.\n\nInstall Claude Code, then add Hermai to your personal Claude Code configuration:\n\n```bash\nexport HERMAI_API_KEY='hm_sk_...'\nclaude mcp add --scope user hermai -e HERMAI_API_KEY=\"$HERMAI_API_KEY\" -- npx -y hermai-mcp\nunset HERMAI_API_KEY\n```\n\nThe key is saved in your local Claude Code configuration. Do not put this command\nin a repository, shared shell history, or a project scoped MCP configuration.\n\nConfirm that Claude Code can see the server:\n\n```bash\nclaude mcp list\n```\n\nThen start Claude Code and use this two step request:\n\n```text\nUse lookup_schema to find a verified public Hermai schema for [the source and task].\nBefore making a fetch, show me the site, endpoint, required parameters, and whether\nthe result can be retrieved with fetch_schema.\n```\n\nAfter you approve the selected workflow:\n\n```text\nUse fetch_schema with the site, endpoint, and parameters we selected. Return a short\nsummary of the records, then show credits_used, credits_remaining, and cached from\nthe response metadata.\n```\n\n`lookup_schema` is safe to use without a key. `fetch_schema` appears only when the\nkey is configured. It reads data through Hermai Cloud and consumes credits for a\nsuccessful request. Do not give the server browser cookies, bearer tokens, or a\nrequest that changes data on another service.\n\nFor a full verification checklist and the expected failure paths, see\n[the Claude Code guide](docs/claude-code.md).\n\n## Tools\n\nAlways available (no key required):\n\n- `lookup_schema` — search Hermai schemas by domain, task, category, or verification state.\n- `list_public_schemas` — page through public schemas.\n- `submit_schema_request` — submit the six-field intake for a brittle browser/API workflow.\n- `classify_browser_workflow` — locally classify whether a workflow maps to direct API, hidden endpoint, browser-only, or owner/auth work.\n- `check_schema_request_status` — check a schema request status.\n\nAvailable only when `HERMAI_API_KEY` (or `HERMAI_PLATFORM_KEY`) is set:\n\n- `fetch_schema` — execute a registered schema through hosted `/v1/fetch` and return live data. **Read-only data retrieval, and it consumes Hermai credits: a standard call costs 1 credit and some higher cost sites cost 5; only successful calls are billed.** Inputs: `site`, `endpoint` (resolve both with `lookup_schema` first; `endpoint` is case-sensitive), and optional `params`. The result includes the upstream `data` plus a meta summary (`credits_used`, `credits_remaining`, `latency_ms`, `cached`); failures surface the API `code` and `message`, plus `upgrade_to` and `upgrade_url` when a credit 402 offers an upgrade path. Use it for read workflows only — write/owner-approved workflows go through the Hermai CLI's signed-write path, not this tool.\n\nNever submit cookies, bearer tokens, API keys, session IDs, or private session data through schema-request intake.\n",
  "bytes": 4104,
  "sha": "9194baf70d065092297c16ed32249094a7c31bfd57acdd8c199fb2079debf347",
  "repo_slug": "hermai-ai/hermai-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_hermai_ai_hermai_mcp_87d1a68d/readme"
}