
Hebline
io.github.HeblinePublished by GitHub account Heblinev0.2.1Updated Nov 10, 2026
Intelligent API routing for AI agents. Best service, best price, free alternatives.
Overview
Routes an assistant's API calls (LLMs, geocoding, translation, search, weather and more) to a free or paid provider and returns the result with cost and latency
- What you can do
- Hebline is a local MCP server that acts as a broker for external APIs. Its execute tool picks a service for a requested capability, makes the call and returns the result plus metadata such as service, cost and latency; compare shows all services for a capability with their scores, and categories lists supported capabilities. It covers nine categories and twenty services, including LLMs, geocoding, translation, web scraping, currency, OCR, weather, web search and news, preferring free providers unless a paid key is configured.
- When to use it
- Use it when an assistant needs several kinds of external lookups and you want one interface that prefers free providers and reports what each call cost. It suits agents that would otherwise call many separate APIs and where you want visibility into spend.
- Requirements
- Runs as a local stdio process, installed via npm (npx or global install) and configured in the client's MCP config. Node.js is needed. Free providers work without keys; paid providers are enabled by setting DEEPL_API_KEY, GOOGLE_MAPS_API_KEY or LIBRETRANSLATE_API_KEY, and the README also lists other provider keys. Network access is required. Without a local LLM key, LLM calls go through the Hebline proxy with a daily free limit.
Installation
In SourceWeft
- Open Hebline in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Hebline MCP Server
Your agents overpay for every API call. We fix that.
Hebline routes every API call — including LLM calls — to the best service at the right price. Free when it's enough. Paid when it matters. It knows the difference.
Every other router earns a margin on your paid calls. Routing you to free alternatives kills their revenue. No margin on your API calls. Ever.
Why Hebline?
Your agents are bleeding money. One task triggers 5–10 paid API calls across different providers. No transparency, no cost control. Hebline fixes that:
- Route free first — Most calls don't need the best model. Hebline learns precisely when it matters — and keeps learning as the market changes.
- No margin. Honest routing. — We don't earn when you pay more. So we're the only router built to actually save you money.
- Provider Abstraction — Your agent says what it needs ("geocode this address"), not which service to use. Swap providers without changing agent code.
- Cost Transparency — Every call is logged with service used, latency, and cost. Know exactly what your agents spend.
- Learns from usage — Hebbian learning strengthens what works, weakens what doesn't. Your broker gets smarter every day.
- BYOK (Bring Your Own Key) — Paid services use your API keys via environment variables. No key? The service is automatically excluded from routing.
- GDPR compliant — Only anonymized metadata logged. No API call content stored. Self-hosted option for zero data leaving your network.
- Open Source — Core MCP server is MIT licensed. Community-driven adapter system.
How It Works
Your agent connects to Hebline as an MCP server. Instead of calling APIs directly, it uses Hebline's tools — execute, compare, or categories. Hebline scores all available services, picks the best one, makes the call, and returns the result with full metadata.
Available MCP Tools
Quick Start
Add to Claude Desktop
Add to claude_desktop_config.json:
Add to Claude Code
Add to .mcp.json:
Add to Cursor
Add to .cursor/mcp.json:
Add to Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
Add to VS Code (Copilot)
Add to .vscode/mcp.json:
Install globally
With paid services (optional)
Set environment variables for any paid providers you want to use:
No keys? No problem — Hebline routes to free alternatives automatically.
Supported Services
9 categories, 20 services. Free services work instantly — no API key needed. LLMs route through the Hebline proxy when no local key is set (50 free calls/day).
Example
An agent asks: "Geocode the Brandenburg Gate in Berlin"
Hebline receives:
Hebline responds:
The agent got coordinates, knows it was free, and Hebline logged the call for future analysis.
Architecture
Call Logging
Every API call is logged to ~/.hebline/calls.jsonl:
No content is logged — only metadata. This data will power Hebbian Learning in future versions.
Roadmap
- Core MCP server with stdio transport
- Weighted scoring router
- Geocoding adapters (Nominatim, Google Maps)
- Translation adapters (MyMemory, LibreTranslate, DeepL)
- BYOK key management
- Append-only call logging
- CI/CD with GitHub Actions
- Hebbian Learning — router learns from call history
- Hopfield network scoring (replaces weighted scoring)
- More categories (web scraping, currency, OCR, email)
- Community adapter system
- SSE transport for remote deployments
- Web dashboard for cost analytics
- Budget alerts and spending limits
- Multi-agent cost attribution
Contributing
Contributions are welcome! Adding a new adapter is straightforward — implement the ServiceAdapter interface and register it.
License
Built by Hebline — Route free first. Only pay when necessary.
Source: README.md at commit 548ed23
Tools
0Version history
1- v0.2.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts