Setup

Connect a server

The PDF and image server speaks streamable-HTTP, so most clients need nothing but the URL. There is no key and no account.

Claude Code

Add it from the terminal:

claude mcp add --transport http pdf-tools https://mcp.pdfsnaps.com/mcp

Any client that reads a JSON config

Add an entry pointing at the same URL:

{
  "mcpServers": {
    "pdf-tools": {
      "type": "http",
      "url": "https://mcp.pdfsnaps.com/mcp"
    }
  }
}

Clients differ in where that file lives and whether the key is called type or transport — check your client's docs for the exact shape. The URL is the part that matters.

Token Audit

The auditor is an HTTP API rather than an MCP server today. The simplest way to use it is the Apify Actor, which handles the request and billing:

https://apify.com/truesoft/ai-agent-cost-token-savings-auditor

To call the API directly you need a key. It takes a finished run's metrics and returns the report:

POST https://api.mcp-share.com/v1/audit
Authorization: Bearer <your key>
Content-Type: application/json

A native MCP server for the auditor is planned.

Checking it worked

Once connected, ask your assistant to list its tools — you should see the PDF and image ones. If nothing appears, the usual cause is a client that needs restarting after a config change.