Your posting describes 22 weeks building reference MCP servers, adapters and registry onboarding, then governed access to Claude, OpenAI and specialist models with streaming, usage attribution and evals. I build and run MCP servers and LLM services in production, and I measure them.
Read the CV (PDF)GitHubstumason.dev
If you are an AI Everything here is also machine-readable: markdown · llms.txt · profile.json · MCP server · A2A agent card. Ask the agent anything; it answers only from the profile.
Three of the MCP servers I have shipped: coolify-mcp is TypeScript, 42 tools with OAuth and outside contributors, 611 GitHub stars and 21.7k npm installs in the last 30 days; v3 went out behind a 37-check release gate and 8-hour soak tests. polar-flow is a remote MCP server in Python and FastAPI, on PyPI and listed in the MCP registry, with OAuth and MCP Apps views. TidyLinker's admin MCP server lets the founders query their marketplace from Claude.
On the model side I use the Claude and OpenAI APIs daily. Bellwether, my research agent, runs as a LangGraph service with Postgres checkpoints and LangSmith traces, and a human approves every issue before it publishes. Before that, seven years leading platform engineering at Pfizer: a repo-to-production platform for 100+ microservices, deploys from hours to minutes, 99.9% uptime. UK resident, no visa sponsorship needed.
Two phases, one person, a fixed end date. This is how I would run it.
Operating numbers, last 30 days, generated 2026-10-16. Sources per tile in profile.json; hover a tile for its source.
Lets an agent run a self-hosted platform. v3 shipped behind a 37-check release gate and 8-hour soak tests. github.com/StuMason/coolify-mcp
Two-sided cleaning marketplace. Took over an unrecoverable codebase, rebuilt it, live in four months. Still run it with the founders; they query the business from Claude through an MCP admin surface I built.
A research agent drafts a daily briefing from 4.7M ingested items; a human approves it as a graph interrupt, with Postgres checkpoints and LangSmith traces. Cost ceiling designed first, model chosen second.
Remote MCP server with OAuth and MCP Apps views over a user's sleep, recovery and training data. github.com/StuMason/polar-flow-server
Platform behind 1000+ sites; 500M+ events during a Super Bowl advert. Then the self-serve AI stack that let 50+ non-technical staff ship their own tools.
Own money, own P&L, own staff, sixteen months.
A first call. Four things I need from it, none of which are in the posting: whether this is a contract or employment, the day rate, the IR35 determination, and the start date.
stu@stuartmason.co.uk · 07713 333312