Solutions

Turn your web app into an MCP server

Your users increasingly work through an AI assistant. The Model Context Protocol is how that assistant reaches other software. Merlean makes your application reachable without you writing and maintaining a tool catalogue by hand.

Why this matters now

A growing share of knowledge work starts in an assistant rather than in an application. If your product is not reachable from there, it is one context switch further away than a competitor that is - and context switches are where habits are lost.

The Model Context Protocol has become the common way to make software reachable by agents. Implementing it is straightforward. Keeping it useful is not: a hand-written MCP server means a hand-written tool for every action, kept in step with an application that keeps changing.

Tools derived from your application, not written by hand

Merlean produces the tool surface from the same analysis that powers the in-app assistant. Endpoints, parameters, validation rules and multi-step workflows all come out of your source, which means the MCP server describes what your application can genuinely do today rather than what someone documented last quarter.

When a release changes a form or adds a route, a re-analysis brings the tool surface with it. There is no second artefact drifting away from the first.

Per-user authorisation

Agents authorise as an individual user through a standard OAuth flow. An agent inherits exactly that user's permissions, and nothing more.

Workflows, not just endpoints

A raw endpoint list makes an agent guess the order. Merlean exposes the real flows, including preconditions and decision points, so multi-step work completes.

One model, several surfaces

The same understanding drives the embedded widget and the MCP server, so the two cannot disagree about what your application does.

What your users can then do

Ask their assistant to complete a task in your product without opening it.
Combine your application with the other tools their assistant reaches, in a single request.
Work from wherever the assistant lives, including a desktop client or a terminal.

Frequently asked questions

What is the Model Context Protocol?

An open protocol for describing tools and resources to an AI assistant in a standard way, so any compliant assistant can discover and use them. It is the practical answer to every product needing a bespoke integration with every assistant.

How do agents authenticate?

Through a standard OAuth authorisation flow against your application, per user. The resulting access is scoped to that user, so an agent cannot exceed the permissions of the person who authorised it.

Is this instead of the embedded widget, or as well as?

As well as, if you want both. They are two surfaces over one execution layer. Many products start with the widget and add the MCP server once usage patterns are clear.

What happens when we ship a breaking change?

Re-run the analysis. The tool surface is regenerated from the current code, so it follows your application rather than lagging behind it.

See it against your own application

Merlean reads your repository and shows you what it understood before anything is exposed to a user. The fastest way to judge the fit is to point it at a real codebase.

Get in touch Read the docs