All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Reducing MCP Costs by 94% Through CLI Conversion

By

thellimist

3mo ago· 3 min readen

Summary

The article discusses how AI agents using Model Context Protocol (MCP) are overpaying due to inefficient tool catalog loading. The author demonstrates that by converting an MCP server to a CLI using CLIHub, they achieved 94% cost reduction while maintaining the same tools, OAuth, and underlying API. The key insight is that MCP loads the entire tool catalog as JSON Schema at session start, while CLI loads only what's needed, dramatically reducing token usage and costs.

Key quotes

· 4 pulled
Every AI agent using MCP is quietly overpaying. Not on the API calls themselves - those are fine. The tax is on the instruction manual.
Before your agent can do anything useful, it needs to know what tools are available. MCP's answer is to dump the entire tool catalog into the conversation as JSON Schema. Every tool, every parameter, every option.
I took an MCP server and generated a CLI from it using CLIHub. Same tools, same OAuth, same API underneath.
Two things change: what loads at session start, and how you interact with the tools.
Snippet from the RSS feed
I Made MCP 94% Cheaper (And It Only Took One Command)

You might also wanna read