MCP server for Tessera's LLM cost-optimization layer: anchored spend, drift, recommendations.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"tessera": {
"env": {
"TESSERA_API_KEY": "tk_..."
},
"args": [
"-y",
"@tessera-llm/mcp-server"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Status: v0.1.3 — published 2026-05-27 on npm with sigstore SLSA provenance v1, listed on registry.modelcontextprotocol.io.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@tessera-llm/mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @tessera-llm/mcp-server against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
An autonomous agent that conducts deep research on any data using any LLM providers
🌊 The leading agent orchestration platform for Claude. Deploy intelligent multi-agent swarms, coordinate autonomous workflows, and build conversational AI systems. Features enterprise-grade architecture, distributed swarm intelligence, RAG integration, and native Claude Code / Codex Integration
MCP Security Weekly
Get CVE alerts and security updates for io.tesseraai/mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The MCP server that returns money, not data.
Status: v0.1.3 — published 2026-05-27 on npm with sigstore SLSA provenance v1, listed on registry.modelcontextprotocol.io.
Tessera is an LLM proxy that optimizes API spend through multi-provider routing, prompt compression, audit-immutable logging, output-length prediction, and batch arbitrage. This package exposes Tessera as an MCP server for tool-using agents — Claude Desktop, Claude Code, Cursor, Cline, Continue, Goose, Zed.
Where other LLM-infrastructure MCP servers return logs, traces, or prompt metadata, this one returns savings decisions: what's drifting, what to switch, what to approve, what to audit.
▶ 41-second walkthrough: live counter ticks · baseline $74,800 → actual $30,000 ($44,800 saved, 60% reduction) · audit-immutable savings ledger. Click to play.
npx @tessera-llm/mcp-server
Or add to your client config:
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):
{
"mcpServers": {
"tessera": {
"command": "npx",
"args": ["-y", "@tessera-llm/mcp-server"],
"env": {
"TESSERA_API_KEY": "tk_..."
}
}
}
}
Claude Code (.mcp.json in project root):
{
"mcpServers": {
"tessera": {
"command": "npx",
"args": ["-y", "@tessera-llm/mcp-server"],
"env": {
"TESSERA_API_KEY": "tk_..."
}
}
}
}
Cursor (~/.cursor/mcp.json):
{
"mcpServers": {
"tessera": {
"command": "npx",
"args": ["-y", "@tessera-llm/mcp-server"],
"env": { "TESSERA_API_KEY": "tk_..." }
}
}
}
Get a TESSERA_API_KEY at tesseraai.io/dev — Free Sandbox is 60M tokens/month with no card.
v0.1 exposes 6 tools (5 read + 1 mutate). Hard cap — no tool sprawl.
| Tool | Read/Write | Purpose |
|---|---|---|
tessera_list_workloads | read | List your mapped workloads with anchor cost + current m-stack. |
tessera_get_savings_report | read | Anchored spend + measured savings for a window. |
tessera_get_recommendation_queue | read | Pending Optimize-tab recommendations with expected lift + confidence. |
tessera_get_ledger_entries | read | Audit-immutable Monthly Reading rows (provider call, mechanic stack applied, savings). |
tessera_get_quality_snapshot | read | SLA floor + p50/p95 quality scores + drift events. |
tessera_approve_recommendation | mutate | Move a queued mechanic from "suggested" to "active" with audit-trail entry. |
Provider config writes, API-key management, composition cap changes, and Stripe operations are deliberately NOT in this surface — they live in the dashboard, where blast-radius requires explicit modal confirmation.
TESSERA_MCP_TRANSPORT=http to bind on localhost:8788 for remote / Goose / Zed-via-mcp-remoteSSE (deprecated in MCP spec 2025-11-25) is not supported.
TESSERA_API_KEY env var or Authorization: Bearer <key> header (HTTP transport). Same API key as the SDK — tk_* format. Future v0.2: OAuth 2.1 (aligned with MCP spec RC 2026-07-28).
__untrusted__ to prevent prompt-injection cascade per the Supaba