Frugal MCP Server

Frugal MCP server exists for a simple reason — assistants are far more useful when they can act on Frugal directly instead of describing what you should do. Cost-optimized MCP server: routes every tool call to the cheapest provider that returns a result.

What you get

Frugal is an MCP server that sits between your agent and its tool providers. You describe the job — a search, an extraction, a render, or just an intent — and Frugal decides how to complete it, routing each call per policy: cheapest capable provider by default, fastest or premium when you say so, pinned or denied when compliance says so, with automatic failover when a provider errors or comes up empty. Every response carries the decision — provider_used, cost_usd, and (via frugal__execute) a one-line reason — so you can audit why each call went where it did.

What the assistant can call

Once Frugal is connected, these are the calls the assistant has available:

• fast — ordered by your machine's own observed latency (from the
• premium — prefers your premium-priced providers, list price
• order — an explicit preference list. It's a prefix, not a
• deny — providers that must never be called. Enforced on pinned
• Org — wide API key management
• Capability — Free / local
• Search — SearXNG · Marginalia · Wikipedia
• Extract — go-readability (local)
• Browse — local Playwright (deferred)
• Embeddings — nomic-embed-text, bge-large
• Transcription — whisper.cpp
• AnythingLLM — frugal mcp install finds AnythingLLM Desktop on its own and merges frugal into /plugins/anythingllm_mcp_servers.json. For a self-hosted or

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need 6 environment variables: SEARXNG_URL, SERPER_API_KEY, YDC_API_KEY, FIRECRAWL_API_KEY, BROWSERLESS_TOKEN, FRUGAL_AUTH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of file and storage access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Frugal's toolset — fast, premium, order and 9 more — is a fair guide to whether it matches your workflow. It is maintained by brainsparker; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Frugal.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the frugal mcp server does with a few real requests.