Set up the Loomal console for your team.
When several people manage several monetized MCP servers, the questions stop being technical: who owns the claims, where does the money land, and who's allowed to change a price. Settle those before the first listing goes live.
A solo maintainer can run a Loomal listing from a personal account and a personal wallet. A team can't — claims tied to one engineer's GitHub account and revenue settling to one engineer's wallet are an offboarding incident waiting to happen.
This guide covers the decisions that make a multi-person, multi-listing setup boring in the good way: ownership that survives staff changes, money that lands somewhere the organization controls, and a clear answer to who touches pricing.
Anchor claims to the organization, not a person
Loomal verifies listing ownership through GitHub. If your servers live in an organization's repositories, claim them through that org ownership rather than a maintainer's personal account — the claim then follows the org, and an engineer leaving doesn't orphan your listings.
Audit this early if your servers were imported from the official MCP registry: registry entries published under personal io.github.* namespaces trace ownership to that person. Moving repos and registry entries under the org before claiming saves an awkward migration later.
Choose a payout wallet the team controls
Every paid call settles as USDC on Base to the wallet on the listing, and settlement is non-custodial — whoever holds that wallet's key holds the revenue. For a team, that wallet must be organizational: a multisig or a treasury-managed wallet, never a founder's personal one.
Treat the key like your highest-tier production secret, because it is one. Decide who can authorize outbound transfers, document recovery, and keep the payout address consistent across listings unless you deliberately want per-product accounting at the wallet level.
Give pricing a single owner
Repricing on Loomal is one field that takes effect on the next 402 challenge — which is exactly why two people experimenting independently will trample each other's data. Pick one owner per listing for price changes, and have them log every change with a date and a rationale.
The console's settled-revenue view is your experiment readout: price change on Monday, compare the week's settled USDC and call volume against the prior week. That discipline only works if changes are serialized.
Split duties along natural seams
A workable division for a team running several listings: maintainers own the servers and their probed tool lists (reconnecting after deploys so listings stay current), a product owner owns descriptions, categories, and pricing, and finance owns the wallet and reconciliation.
Reconciliation deserves a recurring slot, not a someday. Because every call carries an Ed25519-signed receipt and every settlement is on-chain, console revenue should match the wallet's Base transaction history exactly — a five-minute monthly check that catches problems while they're small.
Write down the runbook
The whole setup fits on one page: which GitHub org holds the claims, which wallet receives settlement and who holds its key, who may change prices and where changes are logged, and who re-probes after server deploys. Add offboarding steps — rotate the wallet key if the departing person had access, confirm their GitHub access is gone.
Loomal's fee model keeps the finance section short: 5% on settled transactions, currently waived, with no monthly platform charge to budget for. As of mid-2026, check the console docs for the current state of team and seat management features before assuming a specific roles screen.
FAQ
Can revenue from different servers go to different wallets?
Settlement goes to the wallet configured for each listing, so separating products into separate payout wallets is possible if you want wallet-level accounting per product. Most teams prefer one org-controlled wallet for all listings and split revenue in their books instead — fewer keys to protect.
What happens to our listings when the engineer who claimed them leaves?
That's exactly why claims should be anchored to organization-owned GitHub repositories rather than a personal account. Org-anchored ownership survives any individual's departure; if you're currently claimed through someone's personal account, plan the migration before it's urgent.
How should a team handle the payout wallet key?
Like the production database credentials: a multisig or treasury-managed wallet, access limited to finance-level roles, documented recovery, and rotation on offboarding. Settlement on Base is final with no chargebacks, so key custody is the security boundary for your revenue.
Do we pay per seat or per listing for the console?
No — there's no listing fee or monthly platform charge. Loomal's fee is 5% of settled transactions, currently waived, so the cost of running ten listings with five people involved is the same as one maintainer with one listing: a share of revenue that actually settles.
Set it up once, properly.
Org-owned claims, a team wallet, and one page of runbook.