Usage

First, check it is actually connected

Restart your agent after connecting it, then confirm it is there. In Claude Code:

claude mcp list

You want to see tokensaver: tokensaver - ✔ Connected. If it times out instead, the tokensaver command on your PATH is probably not this server — check with which tokensaver.

Then just ask

You never call the tools yourself. You ask for something, and the agent reaches for tokensaver instead of fetching the raw page.

read https://go.dev/doc/effective_go with tokensaver

Long documents: outline first

The outline costs a few hundred tokens, and then you only pay for the part you actually want.

outline https://arxiv.org/pdf/1706.03762 with tokensaver, then read just the Attention section

Pull requests

A PR or commit URL is fetched as its diff automatically, collapsed to the changed hunks, one heading per file.

read https://github.com/use-tokensaver/tokensaver/pull/16 with tokensaver

Getting oriented in a repository

A gitignore-aware tree instead of an ls -R dump.

read ~/code/some-project with tokensaver

APIs

Shrunk to the fields you asked for, instead of the whole payload.

fetch https://api.github.com/search/repositories?q=language:go&sort=stars with tokensaver — just full_name and stargazers_count, as a table

If a page looks empty

It is probably JavaScript-only. Ask again with js=true and tokensaver renders it in headless Chrome first, when Chrome is installed.

Next: the full parameter tables for read and read_json.