Model or dataset
TheLunarCompany/lunar avatar
TheLunarCompany/lunar

lunar.dev splits agent traffic control between proxy/ and mcpx/

lunar.dev: Agent native MCP Gateway for governance and security

510 stars56 forksTypeScriptMIT

At a glance

What is it?
Lunar.dev is a TypeScript gateway for third-party API consumption, pitched at agent workloads and MCP servers. The README is short and sells five capabilities, but ships no config file, no thresholds and no dashboard, and its MIT licence coexists with paid tiers for production use.
Who is it for?
Lunar.dev is worth a look for teams consolidating several MCP servers behind one address who also want token, cost and latency accounting on the same hop, and the mcpx/ half looks like the more self-contained piece to trial first.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • TheLunarCompany/lunar510 ★ · +17
Star history
Repository2026-09-122026-11-15
TheLunarCompany/lunar493510

17 Stars in the last 64 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

proxy/ and mcpx/ split the gateway from the aggregator

Lunar.dev arrives as two pieces under one repository. The proxy/ directory holds Lunar Proxy, described as the core API gateway and control layer. The mcpx/ directory holds Lunar MCPX, a zero-code aggregator that fronts several MCP servers behind unified API access. You can run either one alone or both together for what the README calls a full-stack solution, and each half carries its own README, so the two are explained and versioned separately rather than as one product. The top-level tree backs that up with example-consumer-app/, interceptors/, readme-files/, CODE_OF_CONDUCT.md and CONTRIBUTING.md. No config file sits at the top level.

Visibility claims four metrics and no thresholds

The first capability is live traffic visibility, scoped to outbound calls and said to include LLM and agent traffic. The named metrics are latency, errors, cost and token usage. What is missing is any definition of those numbers: no unit for latency, no window for the error rate, no currency for cost, no distinction between cached and uncached tokens, no retention or sampling policy. No dashboard directory appears among the top-level entries either, so an evaluator has to read the documentation site linked from the README badges to learn whether metrics are computed inside the proxy or forwarded from upstream providers.

Policy enforcement for agents names no identity

The repository description calls Lunar.dev an agent native MCP Gateway for governance and security, and the second capability follows that line: control tool access, throttle agent actions, and govern agentic traffic with fine-grained rules. Fine-grained carries the weight in that sentence. The README does not say how an agent is identified, whether a rule attaches to a token, a session, a model name or a tool name, what a denial looks like to the caller, or whether a policy change lands without a restart. Throttling agent actions is also a different problem from throttling a person, which matters the moment one gateway serves several autonomous loops.

Traffic shaping lists four mechanisms and no example

The third capability, advanced traffic shaping, names rate limits, retries, priority queues and circuit breakers in a single line. Those are the four controls you reach for first when a gateway sits in front of a paid third-party API, and they are also the four that need numbers to be worth anything: a limit without a window, a retry without a budget, a priority order without a queue depth, a breaker without a threshold. None of those values appears here, and no policy file sits at the repository root. The nearest thing to a worked example is the example-consumer-app/ directory, whose contents and purpose the README leaves for you to open and read yourself.

interceptors/ has no description anywhere in the README

Of the top-level entries, interceptors/ is the one directory that never gets a sentence. In a gateway product an interceptor layer is where custom request handling, logging or vendor specific quirks would live, and sitting beside proxy/ it implies a supported extension point. The README never confirms that. It also does not name the language the interceptors are written in, whether an interceptor can block a request outright, or whether it runs in the same process as the proxy. Open source evaluation usually turns on how far behaviour can be pushed without patching core, and here the answer has to come from reading code or asking the maintainers.

Newest tag is lunar-proxy-v0.9.2 from March 2024, main pushed 2026-10-01

The version story is uneven and worth pinning down before adopting anything. The published releases stop at lunar-proxy-v0.9.2 on 2024-03-21, preceded by v0.9.1 on 2024-03-17 and v0.8.27 on 2024-01-14, and every one of them carries the lunar-proxy name, so nothing was ever cut for mcpx. The last push to main is dated 2026-10-01 and the repository is not archived, which means work continued well past the last tag. For a self-hosted gateway that gap is a decision rather than an accident: pin v0.9.2 and know what you have, or track main and accept that no published artifact corresponds to it.

MIT in the LICENSE file, paid tiers in the README for production

The licence metadata and the LICENSE file both say MIT, and the README repeats that the project remains open source at its core. The same paragraph then narrows the promise: free for non-production and personal use, with advanced features for production environments offered through guided onboarding and platform tiers, and the website as the place to find them. Those two statements sit close enough together that anyone with a legal reviewer will want the actual terms rather than the summary. It also splits the product in a way the repository does not spell out, since the self-hosted proxy is MIT while whatever the paid tiers unlock is described only in marketing terms. Nothing here enumerates which capabilities fall on which side of that line.

Editorial conclusion

Lunar.dev is worth a look for teams consolidating several MCP servers behind one address who also want token, cost and latency accounting on the same hop, and the mcpx/ half looks like the more self-contained piece to trial first. It is not yet a project you can adopt from the README alone: policy syntax, thresholds, identity and rollout behaviour all live behind docs.lunar.dev, the interceptor layer is undocumented, and the newest tagged release is lunar-proxy-v0.9.2 from 2024-03-21 even though main was pushed on 2026-10-01. Before committing, read the policy format, confirm which capabilities the MIT core actually covers versus the production tiers, and decide whether tracking main is acceptable given no tagged artifact matches it.

Frequently asked questions

What is Lunar.dev and what is it written in?

Lunar.dev is a platform for managing, governing and optimizing third-party API consumption across applications and AI agent workloads, described as an agent native MCP Gateway for governance and security. Its primary language is TypeScript, it is licensed MIT, and its homepage is https://lunar.dev.

What is the difference between Lunar Proxy and Lunar MCPX?

Lunar Proxy is the core API gateway and control layer in the proxy/ directory. Lunar MCPX, in mcpx/, is a zero-code aggregator that puts several MCP servers behind a single gateway with unified API access. The README says you can use either one on its own or both together for a full-stack solution.

What can Lunar.dev actually measure and control?

Four outbound metrics are named: latency, errors, cost and token usage, across LLM and agent calls included. The control side covers tool access, throttling of agent actions, and rate limits, retries, priority queues and circuit breakers. The README gives no thresholds, units or policy file for any of them.

How recent are Lunar.dev releases?

The published releases stop at lunar-proxy-v0.9.2 on 2024-03-21, after v0.9.1 on 2024-03-17 and v0.8.27 on 2024-01-14. The repository is not archived and its last push to main is dated 2026-10-01, so commits continue well past the newest tag.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. TheLunarCompany/lunar on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/thelunarcompany-lunar.svg)](https://hysenlabs.com/projects/thelunarcompany-lunar)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/thelunarcompany-lunar.svg)](https://hysenlabs.com/projects/thelunarcompany-lunar)

Was this useful?