The read tools answer the questions a cost-conscious engineer actually asks — what is drifting, what would switching save, did quality hold — and tessera_approve_recommendation is the single call that commits a change. The surface is deliberately kept small, which also means anything outside routing decisions still happens in the Tessera dashboard.
The agent-facing surface of Tessera, an LLM proxy that routes across providers to reduce API spend. Its tools read the state — workloads, savings, quality, the recommendation queue, the ledger — and one of them approves a recommendation.
- Your mapped workloads, each with its anchor cost and current model stack
- A savings report for a window: anchored spend against measured savings
- A quality snapshot, so a cheaper route can be judged on output and not price alone
- The queue of routing recommendations waiting on a decision
- Approval of a recommendation — the one call here that changes anything
- Ledger entries, kept append-only for audit
TESSERA_API_KEY, issued at tesseraai.io/dev. The Free Sandbox tier issues one with no card and covers a monthly token allowance. Installs with npx @tessera-llm/mcp-server; Apache-2.0.
One command plus a key — npx @tessera-llm/mcp-server, then supply credentials