foro
foro studio

We build your MCP app for you.

Your customers already work inside Claude, Cursor and Le Chat. foro studio designs, builds and runs the server that puts your product in there with them, on the infrastructure we operate ourselves.

Twenty minutes with the engineers who would build it, on your own use case.

A second storefront, in the window your customers already have open

A web storefront is a place customers go. An MCP app is a place they are already standing. When someone asks their assistant to reorder, check a shipment or file a claim, the assistant needs somewhere to send that request. If your product is not reachable, the one that is gets the order.

It is the same catalogue, the same pricing rules and the same fulfilment behind it. What changes is the surface: instead of pages a person clicks, a small set of actions an agent may take, each one scoped and priced by you.

Chat

Browse, pick and pay, without leaving the conversation.

What we hand over

A server your customers can reach from any MCP client, with every call authenticated, isolated, masked and logged on the way past.

A diagram of four tool calls, left to right. An AI client asks a question in plain language, it reaches foro's gate where it is authenticated and isolated, runs against one of your systems as a named tool call, and the answer returns the same way, masked for PII and logged as it passes back through the gate. “Which accounts churned?” becomes crm.search_accounts against your CRM, returns 12 accounts, and comes back as “Twelve, mostly on annual plans.”. “Revenue by region, Q3?” becomes warehouse.run_query against your warehouse, returns 1,204 rows, and comes back as “EMEA up, APAC flat.”. “File a bug for this crash” becomes tickets.create against your tracker, returns TICKET-4417, and comes back as “Filed, and on the on-call queue.”. “Find our refund policy” becomes docs.search against your docs, returns 8 documents, and comes back as “Thirty days, unopened only.”. “Buy 3 more of these” becomes store.create_order against your storefront, returns order #8821, and comes back as “Ordered, arrives Thursday.”.

Reachable from

  • Claude
  • Cursor
  • Codex
  • VS Code
  • Windsurf
  • Antigravity
  • Le Chat

We have been shipping this in production

MCP is young enough that most of the advice about it is guesswork. Ours is not: we run MCP servers under real load, for real users, and we wrote the platform they run on.

We build MCP for a living
One of us builds the MCP layer for an international marketing technology scale-up. The other leads data and business applications at an international retailer. This is the day job, not a side interest.
We run the platform underneath
foro is our own MCP hosting platform: containers, routing, tokens, masking, metrics. Every app we build for you lands on infrastructure we operate.
Regulated environments
Between us, cloud infrastructure for a Dutch insurer, a fintech data platform, and aviation. We are used to a security review being the hard part.
It stays yours
The repository, the tokens and the domain are on your side of the line. You can take the server and run it somewhere else the day you want to.

How an engagement runs

Four steps, each ending in something you can open: a tool list, a repository, a URL, a dashboard.

  1. 1ScopeOne session on your systems and your customers. We come back with the tool surface: which actions an agent may take, which it may never take, and what each one is worth.
  2. 2BuildWe write the server against your APIs, your auth and your data model. You get the repository, not a black box, and your engineers review every tool as it lands.
  3. 3ShipIt deploys on foro: EU hosting, per-project tokens, one isolated container. Your customers get a snippet to paste into their client and the app appears there.
  4. 4RunPer-tool metrics, latency and logs from day one, so the questions after launch (what gets called, what fails, what to build next) have answers.

Things we get asked to build

  • Buying without a browser

    Catalogue search, availability, reorder and order status, so a customer can complete a purchase from the assistant they asked in.

  • Your data, answerable

    A read-only surface over the warehouse or the API you already publish, scoped so an agent can answer without being handed the database.

  • The tasks people log in for

    Check a claim, update a record, file a ticket. The handful of actions that make up most of your support volume.

Tell us what your customers ask for. We will build the thing that answers.

Twenty minutes with an engineer, on your own use case. No slide deck.