Logo Accura
Accura

MCP server developer, France

Your customers want to run your SaaS from their assistant.
That takes an MCP server.

I build yours, or I bring yours up to date. Audit in 2 days, migration in 5, a new server in 2 to 3 weeks.

Prices on this page. Scope written down before anything starts. I run two MCP servers in production myself.

Five engagements, five firm prices. Each scope is written down, including what it does not cover.

The problem

Between your product and your customer's assistant, there is nothing

Your product

Your SaaS runs. It gets paid. It has a dashboard that cost you months.

Your customer

They just spent the whole day inside Claude. They will not open one more tab for you.

What is missing between the two is not an integration. It is a front door built for a machine that sees no screen.

That is exactly what an MCP server is. Done well, it becomes the main door into your product. Done badly, it is your REST API in a hat: the agent uses it poorly, and you conclude the protocol is worthless.

Pricing

Audit, migration or build: prices shown, scope written

No drawn-out quotes, no billed discovery. Every engagement has a written scope, a stated duration and a named deliverable.

The audit stands on its own. If the finding is that you have nothing to migrate, you keep the document and I sell you nothing else. It has happened.

MCP server audit

2 days

€950

A document, not a meeting. I compare your server against the new spec, list what breaks in order of severity, and price each item.

  • Line-by-line comparison against the 2026-07-28 spec
  • Review of what each tool declares to the agent
  • Review of OAuth and its public configuration
  • Test of the real network path, firewall and proxy included
  • The document is yours, whether or not you hand me the rest
Start with the audit

Most requested

2026-07-28 migration sprint

5 days

€2,400

The full migration, run on a separate branch, validated from real clients before anything touches your production.

  • Server moved to sessionless operation
  • New mandatory headers, verified all the way to the client
  • Continuous streams replaced by the new round-trip mechanism
  • Error codes and OAuth 2.1 hardening
  • Validated from Claude, ChatGPT, Cursor and VS Code
Start with the audit

Production MCP server build

2 to 3 weeks

€4,500 to €7,500

From scratch. Tools are designed for an agent that sees no screen, which is not the same thing as exposing your existing API.

  • Design of the tools, their names and what they accept
  • Every tool states from day one whether it reads or writes
  • OAuth 2.1, quotas and plan-level permissions
  • Write audit trail, visible to your users
  • Deployment, monitoring and go-live
Start with the audit

Claude connector directory submission

€1,200

fixed fee

Preparation, submission and review rounds through to acceptance. I ran this for my own server, with the same checklist.

MCP compliance watch

€290per month

monthly

The protocol moves fast. I follow the changes, warn you before they affect you, and apply the small updates.

The proof

Two production MCP servers, which I run myself

No client logos, no testimonials, no project counter. The addresses are public and the tools are documented. Go and check.

Brieform

A form SaaS driven by MCP

No drag and drop builder in the dashboard, on purpose. The product's main interface is the MCP server. The dashboard is only a control view.

Server address
https://brieform.app/api/mcp/mcp
MCP tools
12
Stack
Next.js, Supabase, Vercel, PostHog, Polar
  • Sign-in through OAuth 2.1 or an API key
  • Every tool states whether it reads or writes, so the agent knows before calling
  • Audit trail on the 7 write tools, visible in the dashboard
  • Live form preview rendered inside the chat, no iframe
  • Tested from Claude, ChatGPT, Cursor, Le Chat, Perplexity and VS Code
  • EU hosting in Frankfurt, encryption at rest, no raw IP addresses stored

Rendering a real interface inside the chat goes through MCP Apps, the protocol's first official extension, published on 26 January 2026. The list of those doing it fits on one line: Amplitude, Asana, Box, Canva, Clay, Figma, Hex, monday.com, Slack. And one developer alone in south-west France.

DirectoryFast AI

From dashboard-driven to conversation-driven

The clearest case, because it is a transformation rather than a build. A Next.js code template sold once for $197, turned into a SaaS at 29 EUR a month where the user never sees a line of code.

MCP tools
39
  • 39 MCP tools, OAuth sign-in
  • The agent designs the structure of the listings before filling them, so listings genuinely compare
  • The agent stays in charge after launch: publish, fix, write, read the analytics
  • The public site reflects a change on the next read, with no rebuild
  • Business model redrawn around the constraint: free subdomains left unindexed, the paid plan buys indexing

Changing how a product is driven, plenty of people can do. Redrawing its economics around that is a product design problem, not a protocol one. It is the part I charge most for.

Web developer for 8 years, freelance in south-west France. Serving military, former special forces, which mostly explains my zero tolerance for approximate checklists.

How it runs

How an MCP migration goes, day by day

Nothing touches your production until the last day. You can stop after day 0.

  1. Day 0

    Written audit, before a line of code

    You get the list of what breaks and a priced plan. If the verdict is that you have nothing to migrate, I say so and we stop there. You keep the document.

  2. Days 1 to 3

    Migration on a dedicated branch

    Sessions, headers, interactive flows, error codes, authentication. Your production does not move one byte in the meantime.

  3. Day 4

    Validation from real MCP clients

    Real connections from Claude, ChatGPT, Cursor and VS Code. Not a unit test that only confirms my own reading of the spec.

  4. Day 5

    Back to production, then submission

    Supported deployment, then the directory submission if it is in the agreed scope.

Who this is for

What I take on, and what I don't

Better said upfront. A bad client costs more than a lost one.

This is for you if

  • You run a SaaS and your users already work inside Claude, ChatGPT or Cursor.
  • You have an MCP server written before July 2026, and you don't know what needs redoing.
  • You want into the Claude connector directory, and you want to pass review on the first try.
  • You want the agent to use your tools well, not just get a response back.

This is not for you if

  • You want a support chatbot on your website. MCP is not for that, and I will say so on the first call.
  • You want a throwaway prototype. The scope here is production: authentication, quotas, an audit trail.
  • You need an in-house team. I work alone, I deliver directly, and that is a deliberate choice.

State of the market

MCP is no longer a bet, and here are the figures with their sources

Linux Foundation

Anthropic handed MCP to an independent foundation, co-founded with Block and OpenAI, backed by AWS, Google, Microsoft, Salesforce and Snowflake.

Source : Anthropic, December 2025

500M

downloads a month across the official SDKs.

Source : Official MCP blog, 28 July 2026

9,652

servers listed in the official MCP registry, plus 15,926 GitHub repositories tagged mcp-server.

Source : Reading taken 24 May 2026

950+

connectors in the Claude directory. Without a listing, your user has to paste a URL by hand, which a non-developer will never do.

Source : Anthropic, July 2026

41%

of the software organisations surveyed run MCP servers in production.

Source : Stacklok, 2026 report

40%

of enterprise applications will ship with dedicated AI agents by the end of 2026.

Source : Gartner, 2026

Frequently asked questions

Frequently asked questions about MCP servers

Contact

Get your MCP server audited

Describe your server in five minutes: the revision you are targeting, the number of tools, how you authenticate. I reply within one business day with a first written diagnosis, free of charge.

A short form, five fields. No drip sequence, no newsletter: your message lands in my inbox and I answer it myself.

MCP server developer | 2026-07-28 migration and Claude directory