Agentdocs

agentdocs

agentdocs answers questions about the IMBA agent platform from its published documentation: the canonical agent facts, the use-case playbook, the tier policy, where each MCP belongs in catalogs, the list of public doc URLs, and the contents of individual allowlisted public doc URLs.

It is a forwarding client, not a wallet. The documented product behind the docs is a prepaid-card / crypto agent wallet, but this package exposes documentation retrieval only — the same six read-only tools the original docs server exposes — and no operational, registration, deposit, purchase or withdrawal capability of any kind. Every captured tool description repeats that the surface moves no money. get_public_url is forwarded like the others; its allowlist is enforced upstream.

Tools

• get_agent_facts — canonical prepaid-agent policy and catalog: Visa prepaid, eSIM, gift cards, KYT address screen, USDT TRC-20, forbidden rails, tiers. No arguments.
• get_agent_use_cases — the playbook for what agents can buy, with the MCP tools per job. No arguments.
• get_tier_policy — Tier 0 vs 1+: convert and withdraw policy. No arguments.
• get_catalog_placement — which directories take the docs MCP vs the spend MCP. No arguments.
• get_public_url — fetch one allowlisted public docs URL. Required: url (an absolute https://imbawallet.com URL from the allowlist).
• list_docs_urls — list the public agent URLs: HowTo, use cases, tiers, discovery, OpenAPI, MCP endpoints. No arguments.

tools/list is served locally from the tool literals captured verbatim from the published remote. A tools/call is forwarded upstream and the result — content, structuredContent and any isError flag — comes back verbatim, so an upstream refusal (for example a get_public_url allowlist error) passes through unchanged.

Configuration

• IMBA_DOCS_MCP_URL (optional, labelled reconstruction) — override the docs endpoint. Defaults to https://imbawallet.com/mcp/docs.

Failures surface as this rebuild's own error text (labelled reconstruction): agentdocs error: ... — a JSON-RPC error carries the upstream message, an HTTP failure carries the status, and an unparseable response is reported as a malformed response.

Forwarding mechanics

On the first forwarded call the client POSTs an initialize request (protocolVersion 2025-03-26, clientInfo name agentdocs, version 0.1.0), captures the Mcp-Session-Id response header when one is returned, POSTs notifications/initialized, then POSTs the tools/call request with the session header attached when captured. The session is reused for the life of the process. Every POST carries Content-Type: application/json and Accept: application/json, text/event-stream, and responses may be plain JSON or SSE (data: lines).

CLI

Each tool is a subcommand taking one JSON argument string:

npx @reneturcios/agentdocs get_agent_facts '{}'npx @reneturcios/agentdocs get_public_url '{"url":"https://imbawallet.com/agent/howto"}'npx @reneturcios/agentdocs list_docs_urls '{}'npx @reneturcios/agentdocs --version

Output is the forwarded result content as JSON. Exit codes: 0 on success, 1 on an isError result, 2 on a usage error.

MCP server

npx -y @reneturcios/agentdocs mcp

MCP client config:

{  "mcpServers": {    "agentdocs": {      "command": "npx",      "args": ["-y", "@reneturcios/agentdocs", "mcp"]    }  }}

Docker

docker run -i ghcr.io/cloudcorprecords/agentdocsdocker run --rm ghcr.io/cloudcorprecords/agentdocs list_docs_urls '{}'

Development

npm installnpm run build   # tsc -> dist/npm test        # tsx --test test/*.test.ts (fake fetch only, no network)npm run dev     # run the CLI from source

License

MIT — Copyright (c) 2026 Rene Turcios