services
Let ChatGPT search your product. A custom MCP server in one sprint.
I build a custom MCP server for your SaaS, so AI clients such as ChatGPT can search and use your product. One two-week sprint, $6,000.
I added MCP servers to two of my live apps in two days. Your server gets two weeks, a fixed scope, and a live check before handover.
Who this is for
SaaS companies with paying customers and an API or a search that those customers use now.
Teams whose customers ask to use the product from ChatGPT or another AI client.
TypeScript codebases. I work in TypeScript.
Who it is not for
Teams that need an MCP developer for three to six months. I sell two-week sprints.
Teams that want a guaranteed listing in the ChatGPT or Claude directories. I prepare the submission. The directory decides.
Developers who want to build it themselves. Read how I built mine.
What one sprint can ship
Three example scopes. We agree on yours in writing before the sprint.
One search tool. A query in plain language goes to the search you already have, and the results come back to the AI client.
Read-only tools over your API. For example, find an order by email. Each tool has a strict input schema.
Limits that protect your bill. Body size limits, input length limits, rate limits per IP and per day, origin checks, and timeouts on paid AI calls.
Each sprint ends with a check script, a deploy, a live call from ChatGPT, and a handover document.
Proof: two live servers and one open-source server
On 8 and 9 October 2026, I added MCP servers to WhatIsThatBook and WhatIsThatMovie and connected them to ChatGPT. The search already existed, so each MCP server file is under 200 lines.
The limits in production: 20 searches per IP per hour on the book app, 10 per IP per minute on the movie app, and 500 per day on each. AI calls stop after 45 seconds on books and 20 on movies. A request that fails the input schema never reaches a paid model.
My MCP server and agent plugin ThreadCast is open source. A local MCP server runs behind its plugins for Claude Code and Codex.
Words from clients
Justin did a killer job for us, organizing and planning out the first part of our education platform, and honestly, we wouldn't have been able to launch it without him.
He came in and built it from scratch from the very beginning in SvelteKit, he was an integral part of the team as we built up the team around him to be able to support a larger platform like updraft. It was a fantastic experience with Justin.
We would definitely come back to him when we need another extra pair of hands on the SvelteKit side.
Just ten out of ten. Huge kudos.
Thank you, Justin. Bye.
Justin is a delight to work with.
From the start of the project to the end, he made sure to be on par with the scope and even went beyond our expectations.
What started as a business partnership has now evolved into a close relationship between our two businesses, NerdyJoe and Okupter.
How it works
01 / Scope by email. Send me your API docs, or the search you want AI clients to use. I reply within one business day. We agree on the tools and the limits by email, with a short call if useful.
02 / Start on a sprint Monday. You pay upfront. New sprints start every other Monday.
03 / Mid-sprint sync. One 30-minute call to try the first tool and adjust the rest.
04 / Deploy. The server goes live, the check script passes, and I run a live call from ChatGPT.
05 / Handover. A document with the tools, the limits, and the steps to connect a client. You own the code from day one.
Price and refund
$6,000 per two-week sprint. Paid upfront, after we agree on scope and a start date. See the full sprint terms.
Something usable after the first sprint. Or I refund it. No usable server after sprint one means a full refund.
FAQ
An endpoint that AI clients call through the Model Context Protocol. A custom one gives them tools for your product, with your limits.
$6,000 for one two-week sprint, for the scope we agree in writing.
In your app, as one more route, when your stack allows it. Mine are routes in SvelteKit apps on Cloudflare Workers, built with the official TypeScript SDK.
My two live servers are public search tools without user sign-in. I have not shipped OAuth for an MCP server yet. If yours needs it, we scope it in writing before you pay. It can need a second sprint.
Yes. ThreadCast is public on GitHub. The code of your server is yours.