Useful tools.
One local connection.

Set up in VS Code

Add the pinned 0.3.0 adapter with a private API-key prompt. You need Node.js 22+ and npm where the server runs. Review the configuration in VS Code, then confirm installation and trust.

Leave the key prompt empty for free discovery. For paid execution, add service credits and enter only your API key in the private prompt. Keep tool approvals enabled. The link contains no key and cannot buy credits.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "agent-utilities-api-key",
      "description": "Agent Utilities API key (leave empty for free discovery)",
      "password": true,
      "default": ""
    }
  ],
  "servers": {
    "agent-utilities": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "--yes",
        "--package=https://github.com/cgvhbjk/agent-utilities-mcp/archive/09d4673c0a057cf1201649646fb1154f83106994.tar.gz",
        "agent-utilities-mcp"
      ],
      "env": {
        "AGENT_UTILITIES_API_KEY": "${input:agent-utilities-api-key}"
      }
    }
  }
}

Install as a bundle

If your client supports MCP bundles, download the version 0.3.0 MCPB bundle and its checksum. Verify them from the same folder, then import the bundle through your client's extension settings:

shasum -a 256 -c agent-utilities-mcp-0.3.0.mcpb.sha256

Leave the optional API-key setting empty for free tool discovery. Add only your API key to enable paid calls. The bundle needs a Node.js 22+ runtime provided by your client or installed locally. It is unsigned. Its schema and standalone execution have been checked; installation in individual desktop clients is not verified. Release notes.

Listed in the official MCP Registry as io.github.cgvhbjk/agent-utilities-mcp. View registry metadata. Listing does not imply endorsement or compatibility with every client.

You can also find the same local bundle on Smithery. It runs on your computer with Node.js 22+. Connect the adapter to discover the complete current tool schemas and prices.

For clients that cannot import bundles, use the manual setup below.

1. Save and verify the adapter

Download the JavaScript file and checksum to a private working folder. It includes the MCP SDK and runs with Node.js 22 or newer; no npm install is needed. Review downloaded code before running it. On macOS, verify the downloaded file from its folder:

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

Checksums detect changed downloads; they are served by the same website and are not an independent signature. Bundled library notices · Source code on GitHub.

2. Add service credits

In the API workspace, create an account, save both credentials privately, and purchase a $5 credit pack for a useful task. Give only the API key to the adapter. Keep the recovery key separate. Check the displayed payment mode before purchasing. The adapter cannot buy credits or charge a card.

3. Configure your MCP client

Choose a local stdio server, executable node, and the absolute path to the saved file as its sole argument. Set AGENT_UTILITIES_API_KEY in the child process environment using your client's private secret setting when available. If Node is not on the client's PATH, use its absolute executable path.

For clients using the common mcpServers JSON configuration format:

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

Replace both placeholders locally. Never paste a real key into a prompt, shared configuration, source control or command-line arguments. Omit the environment key to check tool discovery without spending credits. Managed remote-only MCP clients cannot run this local adapter.

4. Try a useful task

Review the per-call prices in your client's tool list and approve spending before use. For example: “Use commerce_gtin_validate to check the barcode 036000291452.” This costs $0.0003 for one successful call. Each new call is a new billable operation; adapter 0.3.0 caps a new debit at its startup catalog price. A price increase is rejected. There is no total session budget. It never tops up automatically.

Recover a lost response

The adapter retries a failed HTTP exchange once with the same request ID. It returns that ID alongside results and uncertain outcomes. Ask your agent to use agent_utilities_retry with that ID, the original tool name and unchanged arguments within ten minutes. In 0.3.0 this helper uses a zero ceiling to recover an existing request without a new reservation. A request that never arrived is rejected. Automatic transport retries of a new call retain its original ceiling. Do not repeat the original tool as a new call after an uncertain result.

Request identities stay in process memory. If the process exits, recovery needs the ID returned to your client and the original input. If the client never received the ID, inspect your balance or contact support before repeating work; restart alone cannot restore a lost operation. Tool inputs and results are sent to Agent Utilities under the service data policy.