MCP server development: connect your application to Claude, ChatGPT and other AI assistants
Model Context Protocol (MCP) servers for PHP and Symfony applications, so Claude, ChatGPT and other AI clients can use your data and actions safely.
An MCP server lets AI assistants such as Claude and ChatGPT use your application directly: read its data, call its actions, and work within the permissions a user already has. The protocol is the easy part. What decides whether it is safe to switch on is everything in front of the tools.
What this looks like
- An MCP server for your existing application, written in PHP alongside the Symfony code it exposes, so tools reuse your services, validation and domain rules instead of a parallel copy that drifts.
- Tool design models can use well: a small set of clearly described tools with typed inputs, not your whole API exposed at once.
- Authentication and authorization: each user connects with their own account, and every tool call is checked against the same permissions as the rest of the app.
- Per-tool policy: which tools exist for which users, rate limits, usage and billing gates, and an audit trail of what the assistant did.
- Output control: a serialization layer that decides exactly what a model is allowed to see, so private fields never leave just because a tool returned an entity.
Where I've done it
Madori, my own product, exposes its data to LLM clients through an MCP server with a tool registry, per-tool policy, authorization and billing gates in front of it, and a serializer that decides what a model is allowed to see.
Other services
Most engagements touch more than one of these.
Symfony & API development
Freelance Symfony developer, 15 years in production PHP. API Platform, REST/JSON design, third-party integration, and the tests that keep it maintainable.
Security & authentication
Symfony security consultant: OpenID Connect SSO, two-factor authentication, and role-based access control, shipped into applications that already have users.
AI & LLM integration
AI integration for existing PHP applications: assistants, retrieval, structured extraction and streaming — built around cost, latency and failure modes, not demos.
Architecture & modernization
Moving long-lived PHP applications, Drupal 7 sites included, onto Symfony and Doctrine incrementally, while the team keeps shipping features.
Small projects
Fixed-scope, fixed-price work from $1,000: WordPress builds and fixes, plugin work, site migrations including Drupal 7, and small Symfony or PHP fixes.
Game & app prototyping
A working prototype of your game or app for $1,000 a month: a playable or clickable core on a live URL in 3 to 6 months, with the code yours.
How I work
What working together looks like, from the first conversation to well after launch.
-
Discovery
We start with what you need and what "done" looks like, written down and agreed, so the estimate and the finish line mean the same thing to both of us.
-
A staging site from the first week
You get a working URL early, updated as work lands, so progress is something you can click rather than a status report.
-
Feedback while it's being built
Reviews and change requests happen throughout, not in one big reveal at the end, when changes cost the most.
-
Delivery and handover
Code, documentation and a proper handover, so your team can run and extend it without me.
-
A 30-day bug-fix guarantee
For 30 days after delivery, I fix defects in what I delivered, against the agreed scope, at no charge. New features aren't covered; mistakes are.
-
Support after launch
I don't disappear at handover. I stay on to support what I've built after it goes live, with fixes, updates and new features as your needs change.
Engagements are part-time and remote, running alongside your team rather than around it, with working hours that overlap teams in the US and Europe.
Start a project
Tell me what you are working on and I will come back with a view on scope, sequence and what I would do first.
Or reach me directly: