Two MCPs, One Front End, Three Days

Two MCPs, One Front End, Three Days

The Tollbooth DPYC network already ran many MCPs. This is the story of the first time we deliberately built one front end on two of them, between a Thursday and a Saturday.


One service among many

By this autumn, the Tollbooth DPYC network already ran many MCP operators, covering weather, farming, brokerage data, publishing, a knowledge graph, and more. Each one is paid by the call, and each one stands on its own. An agent such as Claude could already use several of them in a single conversation. What we had not yet done was build a web front end that deliberately coupled two of them into one experience for a person at a screen.

One of those operators was Good Earth, an MCP server with a map-first web front end. It answers a grower's questions about a particular piece of ground, such as when to plant garlic, whether a crop will finish before frost, and how wet the leaves have stayed this week. Growers draw their Plots on a map, and Good Earth reasons about each one from regional weather and a terrain model.

One autumn evening the next question arrived, as next questions always do. Many growers already own a small weather station on a fence post, and those stations publish their readings to the vendor's cloud. Could each Plot show what its own station reports right now?

We could have added that to Good Earth. Instead, we decided that reading weather stations was a job of its own, worth doing once and well, for Good Earth and for anyone else who needed it. So we started a new service, with the intention, from its first day, of composing it with Good Earth.

Thursday: a new MCP, open for business

FieldData reads a patron's weather stations from the Ecowitt and Ambient Weather clouds and returns the readings in one consistent shape, whoever made the station. That was the part we actually had to write. Everything else that turns a script into a business came from two libraries we had already built.

On the back end, FieldData depends on the tollbooth-dpyc wheel from PyPI. Adding it gives a new MCP server metered tools, Lightning-paid credits, patron identity, coupons, account statements, and onboarding into the Tollbooth DPYC network. On the front end, the @tollbooth-dpyc/web module from NPM supplies the patron sign-in, balance, and top-up pieces of the web interface, shared by every Tollbooth DPYC front end. A developer writes the tools that make the service useful, and the libraries supply the commerce around them.

By the end of that first day, FieldData was deployed, adopted by Tollbooth Authority New England, wired to its own BTCPay Lightning node, and priced at a single satoshi per call. In other words, it was open for business on the same day it was born.

E-commerce without the paperwork

It is worth pausing on how unusual that is. A conventional SaaS launch spends its first weeks on everything except the product. The team applies for a merchant account, waits on a payment processor's Know Your Customer review, builds a user table with password resets and email verification, and wires up subscription billing before a single customer can pay a single cent.

Unlike that path, a Tollbooth DPYC operator takes payment immediately, in Bitcoin over Lightning, with no processor to apply to and no KYC to wait on. Patrons do not create accounts at all. Each patron is a Nostr public key of their own choosing, and they prove it by replying to a sealed message in their own Nostr app. A patron may use one key at every Tollbooth service or a different key at each one; the choice is theirs, not the operator's. There are no passwords to store, no customer database to protect, and no sign-up form to abandon. On the other hand, nothing about this is loose: every call is metered, every credit is accounted for, and every grant of permission is signed and revocable by the patron.

Patrons also pay ahead, in a small Lightning balance, rather than at every call. That is where Tollbooth DPYC parts ways with per-request payment schemes such as x402, which settle a payment on each call; we compare the two in Don't Pester Your Customer, and Monetizing Intelligence beats Monetizing Electrons explains why settling every cheap call is the expensive way to charge for it. A pre-funded balance lets an agent call FieldData many times in a session without stopping the patron for a payment ceremony each time.

The practical effect is that the cost of standing up a new paid service collapses to the cost of writing its useful part. That changes which services are worth building. A small, focused tool that might earn a few satoshis a call is no longer too small to bother with.

Friday and Saturday: two services behind one front end

With FieldData live, the remaining question was how Good Earth should use it. The answer was to treat FieldData exactly as any other client would. Good Earth connects to FieldData over the Model Context Protocol, the same way Claude does, and calls its published tools. The two services share no code, and neither one imports the other. Their only contract is FieldData's public tool interface.

Identity carried across without any new machinery. Each Tollbooth service knows its patrons only by the Nostr keys they present, so the FieldData account that owns a station could belong to the grower, to a neighbor, or to a farm cooperative, each under its own key. For the Good Earth front end, we took the simplest path: the same patron who curates the Plots also holds the FieldData account. When Good Earth asks FieldData for that patron's stations, it does so on the patron's behalf, with the patron's one-time consent, and the patron pays FieldData's small fee from their FieldData balance. Each service keeps its own books, and neither needs to know how the other keeps them.

The ownership split stayed simple. FieldData knows the stations a patron tracks, and Good Earth knows the Plots a patron curates. A grower picks one station for each Plot, and the Almanac for that Plot now opens with a card named for the station, showing the temperature, humidity, wind, pressure, rain, and sunlight it reports at that moment, right above Good Earth's own outlook for the days ahead.

The idea was sketched on Friday evening. By Saturday evening, that card was showing live readings from a real station on a real farm in Vermont.

Why composition is fast

Looking back, the speed came from a handful of choices that each removed work rather than adding it.

  • Small services with one job each. FieldData worries about station vendors, while Good Earth worries about crops and seasons. Each is small enough to understand in an afternoon.
  • A standard way to call each other. MCP gave Good Earth a ready-made client for FieldData's tools, so there was no bespoke API to design, document, or version.
  • Commerce in the box. The tollbooth-dpyc wheel and the @tollbooth-dpyc/web module made payment, metering, and onboarding a dependency rather than a project.
  • Identity without accounts. Because every patron is simply a Nostr key, a new service needs no user database on its first day, and two services can cooperate on a patron's behalf without a shared login, whether that patron uses one key for both or a separate key for each.

None of these ideas is exotic on its own. Together, they mean that the second service in a federation costs about as much as its own useful code, and the third will cost the same. The MCPs collection lists the rest of the ecosystem, each a separate operator built on the same two libraries, and each now a candidate for the same kind of composition. A federation built this way grows the way a good farm does, one well-tended Plot at a time, with each new piece making the ones beside it more valuable.

Write the useful part. The libraries bring the shop, the till, and the guest book.

Try it on your own ground

If you have a weather station, connect it to FieldData and choose it for your Plot in Good Earth. If you do not have one yet, the Terroir collection lists the hobby and prosumer gear that works with FieldData. And if you have a useful tool of your own that deserves to be paid by the call, the same two libraries are waiting for it.

Further reading


FieldData and Good Earth are Tollbooth DPYC operators. Tollbooth DPYC is open source under Apache 2.0: tollbooth-dpyc and fielddata-mcp

Return to Collection