Five engagements, five firm prices. This page also says what each price does not cover, because that is where the bad surprises live. Nothing is invoiced before the scope is written down and accepted.
MCP server audit
€950
Duration
2 days
Revision rounds
1
A document, not a meeting. I compare your server against the new spec, list what breaks in order of severity, and price each item.
Included
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
Not included
The implementation. The audit says what to do, it does not do it.
Access to your production. I work on a copy of the repository.
2026-07-28 migration sprint
€2,400
Duration
5 days
Revision rounds
2
The full migration, run on a separate branch, validated from real clients before anything touches your production.
Included
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
Not included
Redesigning the tool set. Migrating is not redesigning.
The directory submission, which is a separate engagement.
Hosting and third-party services, which stay on your accounts.
Production MCP server build
€4,500 to €7,500
Duration
2 to 3 weeks
Revision rounds
3
From scratch. Tools are designed for an agent that sees no screen, which is not the same thing as exposing your existing API.
Included
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
Not included
Designing your product itself. I design its surface for an agent.
Hosting, domain and third-party services, which stay on your accounts.
The directory submission, taken alongside.
Claude connector directory submission
€1,200
Duration
fixed fee
Preparation, submission and review rounds through to acceptance. I ran this for my own server, with the same checklist.
Included
Privacy policy review, the number one rejection reason
Tool declarations checked one by one
Transport and OAuth connection tested from Claude
Pagination and readable error messages
Demo account with sample data
Not included
A guarantee of acceptance. The decision belongs to Anthropic.
Technical fixes that review might surface, where they fall outside what was already delivered.
MCP compliance watch
€290per month
Duration
monthly
The protocol moves fast. I follow the changes, warn you before they affect you, and apply the small updates.
Included
Tracking of changes that touch your server
Alert before impact, not after
Minor changes applied, included
Compatibility review at each major release
No minimum term
Not included
Heavy rework. A major spec revision is a sprint, not a minor update.
On-call. I warn you and I apply changes, I am not reachable around the clock.
What moves a price
Three things, and only one is genuinely expensive. The number of tools moves a build, not a migration. Unusual authentication adds time end to end. And a server holding a lot of state in memory is the one case that can push a migration past five days. The audit answers that question before you commit, which is exactly what it is for.
Payment terms
30% on order, once the scope is written down and accepted.
40% at the halfway point, on engagements running longer than a week.
30% on delivery.
Bank transfer or card. Prices in euros, excluding tax for businesses.
Beyond the included revision rounds, requests are billed at 80 EUR an hour.
Guarantees
30 days of conformity guarantee against the agreed scope, after delivery.
Confirmed bugs fixed for 30 days on a migration, 90 days on a build.
The code is yours, in your repositories and your accounts. No lock-in.
What I cannot sell you
Acceptance into the Claude connector directory cannot be guaranteed contractually: the decision belongs to Anthropic, not to me. I prepare the submission with the checklist I used for my own server, I submit it and I iterate through review. A provider promising you acceptance is selling a decision that is not theirs to make.
Questions about pricing
Why fixed prices rather than a day rate?
Because the overrun risk is mine, not yours. On a migration the checklist is the same from one server to the next, so I know how long it takes. A day rate would make you pay for my learning on every engagement.
What if the scope changes along the way?
A substantial change gets a written, priced amendment before any work starts on it. Nothing appears on the final invoice without having been accepted in writing before it was done.
Is the audit deducted if I take the migration afterwards?
The audit is included in the 2,400 EUR migration sprint. If you take it alone at 950 EUR and then continue, it is deducted. You never pay for it twice.
The starting point is always the same
Describe your server in five minutes. I reply within one business day with a first written diagnosis, free of charge, and I tell you which of these five lines applies to you. Sometimes the answer is none of them.
