Agent Utilities MCP

A hosted Streamable HTTP connection is also available at https://agent-utilities.agent-utilities.workers.dev/mcp/remote. It provides free resources and call preparation, plus paid execution with existing credits and a private Authorization header. No local Node process is required for that connection. Read the hosted MCP guide; its wrapped tool arguments differ from this local adapter. No OAuth or wallet signing is provided.

Connect a local stdio MCP client to the current catalog of paid utility APIs for HTML extraction, JSON validation, agent configuration checks and product data. This MIT-licensed adapter runs locally; the hosted API is a paid service.

Tool catalog · Installation guide · Pricing · Policies and support

VS Code users: open the setup link and private-key configuration. Detailed instructions are included in this source repository.

Connect the hosted MCP in Cursor or VS Code

No local Node.js process is needed. These setup links contain only the server name and public endpoint, with no API key or payment authorization:

• Set up hosted Agent Utilities in Cursor
• Set up hosted Agent Utilities in VS Code

Review the configuration in your installed, MCP-capable application before accepting it. Inspect the installation scope and keep tool approvals enabled. These links configure the hosted connection, not the local adapter described elsewhere in this README.

Endpoint: https://agent-utilities.agent-utilities.workers.dev/mcp/remote (Streamable HTTP). The separate legacy /mcp JSON-RPC endpoint has different behavior and is not the endpoint used by these setups.

Free versus paid: discovery, supplied-data previews and agent_utilities_seo_audit need no Agent Utilities account or API key. The free SEO audit operates on supplied snapshots; it does not crawl arbitrary URLs. The 49 paid catalog tools require existing service credits and a private Authorization: Bearer API-key header, plus the prepared input, request ID and price ceiling described in the hosted MCP guide. This setup does not create an account, buy credits or grant approval to spend. No OAuth is provided. Never put an API key in an install link, shared configuration or chat.

Manual setup if a link does not open

Merge the appropriate server entry into your existing configuration; preserve other servers.

Cursor: use .cursor/mcp.json for this project, or ~/.cursor/mcp.json for your user-wide configuration.

{
  "mcpServers": {
    "agent-utilities-hosted": {
      "url": "https://agent-utilities.agent-utilities.workers.dev/mcp/remote"
    }
  }
}

VS Code: run MCP: Open User Configuration for the current user profile and merge this native VS Code format. For a workspace-only native configuration, use .vscode/mcp.json. Current VS Code also supports portable .mcp.json; consult its documentation before choosing a format.

{
  "servers": {
    "agent-utilities-hosted": {
      "type": "http",
      "url": "https://agent-utilities.agent-utilities.workers.dev/mcp/remote"
    }
  }
}

After reviewing and enabling the connection, inspect its discovered tools. Start with a free supplied-data preview or the free SEO example and contract. Installation scope, organization policies and agent-session support depend on your client.

Verification: install-link payloads were decoded and checked against these configurations on October 4, 2026. Focused server tests passed using the official MCP SDK's Streamable HTTP client, including free SEO behavior. Actual Cursor/VS Code application installation and model-driven execution have not been tested; no marketplace listing or endorsement is claimed.

References: Cursor installation links, Cursor MCP configuration, VS Code installation URLs, Microsoft's remote-HTTP install-link example, VS Code configuration and scope.

Turn supplied HTML into compact research inputs

Page Pack extracts bounded readable content from HTML you already have, with its source URL, truncation flags and size estimates. Use it to prepare captured documentation or page content for an agent, then inspect the output and retain the original source.

• Free preview: no account, card or API key; entire JSON request up to 32,768 UTF-8 bytes and output up to 3,000 characters.
• Paid web.page-pack: HTML up to 100,000 characters within a 131,072-byte request, with output up to 12,000 characters. The current experimental price is $0.0005 per call.
• Credits: $1 and $5 prepaid packs are available. At the current Page Pack price, $1 covers 2,000 calls before credits are used on other tools; service-wide daily capacity limits below still apply. There is no automatic paid fallback or top-up.

Prefer publisher-provided Markdown or an official API when available. Page Pack does not fetch arbitrary URLs, render JavaScript, verify facts or guarantee token savings. Source text remains untrusted; small inputs can grow after JSON metadata. Token estimates use UTF-8 bytes divided by four, not a model tokenizer.

Try a free HTTP preview

Save this synthetic example as page.json:

{"html":"<html><head><title>Retry guide</title></head><body><nav>Home Account Ads</nav><main><h1>Retry guide</h1><p>Requests time out after 30 seconds. Retry only idempotent requests.</p><pre>GET /v1/items</pre></main></body></html>","sourceUrl":"https://example.com/retry-guide","maxChars":3000}

curl --fail-with-body 'https://agent-utilities.agent-utilities.workers.dev/v1/preview/web.page-pack' \
  -H 'Content-Type: application/json' --data-binary @page.json

The free preview removes the example's navigation and retains its timeout guidance and code sample. Check chargedMicroUsd, result.content, result.truncated and result.measurement. This is a synthetic demonstration, not a customer result.

For MCP, connect to https://agent-utilities.agent-utilities.workers.dev/mcp/remote?category=web and call agent_utilities_page_pack_preview with the same input. For larger inputs or longer output, read the paid contract and explicitly authorize execution. HTTP paid calls require a private API key, a stable Idempotency-Key and can use X-Max-Credit-Micro-Usd: 500 to cap a new call at $0.0005. A per-call ceiling is not a total session budget; follow the recovery instructions below after uncertainty.

For SEO agencies

Try the free SEO audit. It is a separate free entry point; the paid Page Pack capacity described above is for supplied-HTML extraction.

The live catalog currently contains 49 paid tools, separate from free resources and previews. Verified on October 4, 2026: the hosted MCP server reports 1.9.0; this repository's local stdio adapter and immutable MCPB release remain 0.3.0. These are separate components, not interchangeable version numbers.

Pay per call with USDC

For agents with a Circle Gateway balance, a separate standalone USDC client supports Base mainnet payments without a Stripe credit pack. Download and preview the example. It pins network and contracts, caps each call, and saves signed requests privately for recovery. Preview is offline; preparation and submission require separate explicit commands. Real execution spends real USDC. This client is separate from the Stripe-funded MCP adapter and is not included in the immutable MCPB 0.3.0 release.

Try the shopping example without an account

Clone this repository and preview the supplied cart with Node.js 22+:

cd examples/cart
shasum -a 256 -c cart-workflow.mjs.sha256
node cart-workflow.mjs --preview cart-example.json

Preview validates the input and prints the three-step plan offline, with no API key, network request or charge. It does not execute the tools. The included expected output is a local fixture: German price strings become decimal amounts, guarded patches update the supplied cart snapshot, and cost reconciliation returns a known total of €45.92. Tax is unknown, so the final total remains null.

To run those three operations against the hosted service, privately set AGENT_UTILITIES_API_KEY in your process environment and explicitly choose:

node cart-workflow.mjs --execute cart-example.json

Execution spends existing service credits. The recipe enforces per-call price ceilings totaling at most $0.0013 (0.13 cents) across its three logical calls. It stops if a discovered price is too high or a later price exceeds the authorized ceiling. Completed steps stay charged if a later step fails. Each step returns its debit receipt and recovery information; do not rerun the entire recipe after an uncertain response. Read the recipe instructions before execution. This example does not buy credits or place a merchant order.

The recipe is a separate standalone download, not part of the immutable v0.3.0 MCPB bundle. You can also get it from the workflow page. The generic MCP adapter's spending behavior remains as described below.

Read the material directly from an agent

No account or key is needed to read contracts, examples, prices and guides:

curl --fail --silent --show-error \
  https://agent-utilities.agent-utilities.workers.dev/v1/content/index?utm_source=github

• Complete JSON content: tool input/output schemas, example requests, execution headers, workflows and documentation.
• Full text guide: the same material as plain text.
• One tool's contract: request schema, example, price and execution URL.
• Cart workflow: the steps and current aggregate price.
• OpenAPI: HTTP tool operations, optional credit ceiling header and error responses.

These public GET endpoints support cross-origin browser reads. Tool execution remains paid. Custom HTTP clients can send X-Max-Credit-Micro-Usd to cap a new prepaid credit debit; read the quickstart for retry semantics. Adapter 0.3.0 caps each new call at its startup catalog price and requires server-advertised support.

Prefer Python?

The Python HTTP client uses only Python 3.10+ standard libraries. See examples/python for offline preview, free discovery and explicit paid calls with per-call ceilings and stable retry identities. No Node or MCP process is required for this route. It is separate from the MCPB bundle.

Install

Also listed on Smithery as a local Node.js MCPB bundle. Its download matches the v0.3.0 GitHub artifact. Connect the adapter for the complete current tool schemas and prices; directory metadata is a discovery summary.

For clients that support MCP bundles, download agent-utilities-mcp-0.3.0.mcpb and its checksum from the v0.3.0 release. Verify the checksum before importing the bundle through your client's extension settings. It contains the adapter, manifest and license notices. The bundle is unsigned; the release checksum establishes file consistency, not an independent signature. Bundle schema and standalone execution are tested; installation in each desktop client is not verified.

The bundle's optional Agent Utilities API key setting is marked sensitive. Leave it empty for free discovery, or enter only your API key to enable paid calls. Node.js 22+ is required; use a compatible runtime provided by your client or installed locally. If your client cannot import MCPB files, use the manual setup below.

Requires Node.js 22 or newer. Download agent-utilities-mcp.mjs and its .sha256 file from the installation guide, then verify the file from its folder:

shasum -a 256 -c agent-utilities-mcp.mjs.sha256

Alternatively, clone this repository and use its bundled agent-utilities-mcp.mjs directly. No npm install is needed to run the bundle. Source is in src/; npm ci && npm run build rebuilds it. The public bundle is tested as a standalone process outside the application's dependency tree.

For a client that uses the common mcpServers configuration format:

{
  "mcpServers": {
    "agent-utilities": {
      "command": "node",
      "args": ["/absolute/path/agent-utilities-mcp.mjs"],
      "env": {
        "AGENT_UTILITIES_API_KEY": "YOUR_PRIVATE_API_KEY"
      }
    }
  }
}

Replace the file path. Configure the API key privately using the client's secret settings where supported; never commit a real key or paste it into an agent prompt. Use the absolute path to Node if the client cannot find it. For remote-only MCP clients, use the hosted Streamable HTTP endpoint above. Its paid calls require a private Authorization header and the wrapped arguments in the hosted MCP guide.

Omit the key to discover tools without spending credits. Obtain an API key and separately saved recovery key in the workspace. Only give the API key to the adapter. Live mode sells $1 or $5 USD prepaid service-credit packs. Check the displayed mode before buying.

What it does

• Fetches the public tool definitions and current per-call prices on startup.
• Exposes the service tools discovered from the current catalog and one recovery helper. The recovery helper is not an additional product.
• Sends authenticated calls only to the fixed Agent Utilities origin; redirects are rejected.
• Generates a stable debit request ID and retries one failed HTTP exchange with the identical body and ID.
• Keeps request identities and input hashes in process memory, without logging inputs, results or credentials. Remote data handling is described in the service policies.
• Does not purchase credits, automatically top up, access a wallet or accept recovery credentials.

Try a useful task such as: “Use commerce_gtin_validate to check barcode 036000291452.” One successful call costs $0.0003. Current tool prices range from $0.0003 to $0.003; these are experimental prices, not fixed forever. Every new operation spends credits. Version 0.3.0 caps each new debit at the price discovered at startup. There is no total session budget; repeated new calls can spend the available balance. A higher server price returns HTTP 412 instead of increasing the ceiling. Restart only after reviewing refreshed prices. Review prices and approve spending in your client.

Retry an uncertain result

Results and uncertain outcomes include a requestId. Call agent_utilities_retry with that ID, the original MCP tool name, and the original arguments:

{
  "requestId": "COPY_THE_RETURNED_REQUEST_ID",
  "name": "commerce_gtin_validate",
  "arguments": { "code": "036000291452" }
}

Within ten minutes a completed request returns the saved result without another debit. In version 0.3.0 the recovery helper sends a zero ceiling: a request that never reached the service is rejected without a new reservation. This does not cancel a previous reservation or refund a charge. The automatic transport retry of a new call retains its original nonzero ceiling and can still execute that authorized operation once. Do not generate a new ID or change the input to recover an uncertain result. Expired request identities cannot make another debit. Reusing an MCP request ID within one process also retains its original debit identity.

After a process restart you need the returned request ID and original input for recovery. If the process died before your client received the ID, inspect the balance or contact support before repeating the operation. No durable local input or result history is stored. Each process retains up to 5,000 MCP request identities, then refuses new calls until restarted; finish pending recovery first.

Service limits

The individual-tool service allows up to 1,000 new paid call attempts per day per payment rail across the service. HTTP and hosted MCP share the credit rail's capacity; retries of an existing matching request do not create a new debit. Inputs are bounded to 128 KiB including protocol overhead. Network tools are restricted to the hosts shown in the catalog; they are not a general web browser. Security checks are heuristics. Successful results are encrypted for ten-minute retry recovery, with request tombstones retained for one day. See the policies for retention and refund details.

Automated tests verify lost-response recovery against a local Cloudflare credit ledger. They do not establish customer demand or prove a live customer purchase. Directory validation and free tool discovery are not sales.

License

Adapter code: MIT. Bundled dependencies: see THIRD-PARTY-NOTICES.txt. The license covers the adapter, not free access to the hosted APIs.

Choose whole packs for a shopping task

The pack planner finds the minimum item subtotal for a required count of interchangeable items using explicit pack limits. Twelve items can cost $15.98 as two six-packs at $7.99, even when a ten-pack at $11.99 has a lower unit price. The operation costs $0.0008 in prepaid credits. Shipping, tax, coupons and product equivalence are outside its optimization.

Call commerce_pack_plan through MCP, or use the Python client with tool ID commerce.pack-plan and an explicit 800-micro-dollar ceiling. Inspect the free JSON contract before executing. The worked workflow explains stock limits and how pack counts map into cart reconciliation. The adapter discovers this tool from the service; new tools do not require replacing the adapter.

Try the Python pack-planning example with its three sample cases. Run python3 pack_plan_example.py from examples/python, or select --scenario limited-stock / --scenario insufficient-stock. The default is an offline display of fixed fixtures; it sends no request and computes no new answer. Adding --execute explicitly authorizes one hosted call capped at $0.0008 using existing credits. A valid infeasible result is billable too. See the Python guide for checksums, input limits and recovery before executing. Each new run creates a new ID; do not rerun to recover an uncertain paid result.

Upgrading from 0.2.1

Install 0.3.0 for per-call price ceilings and recovery-only manual retries. Version 0.2.1 does not enforce these adapter protections. Existing 0.2.1 release bytes remain available and unchanged; upgrading requires replacing the installed adapter. The per-call ceiling does not limit the number of new calls or provide a total session budget.

Compare delivered checkout totals

The standard-library Python recipe in examples/python/compare_carts.py compares supplied merchant checkout snapshots using one capped reconciliation per cart. Default preview is offline; execution requires --execute and existing credits. It ranks complete totals, retains ties and declines to name an overall winner when any cart has unknown shipping, tax or fees. The two-cart default ceiling is $0.001. See the comparison guide for sample inputs, checksums, explicit budgets and recovery.