Your SaaS, usable by AI agents in two weeks.
Your customers are starting to ask ChatGPT and Claude to do the work instead of opening your app. I build the piece that lets them: a production MCP server, sign-in for agents, and listings where assistant users find tools. Fixed scope, two weeks, and the code is yours.
What you get.
Three things an assistant needs to use your product properly, and a handover so you can run them without us.
| Deliverable | What it is | What it means for you |
|---|---|---|
| A production MCP server | The tools an assistant needs to do real jobs in your product, with names and descriptions the model reads correctly. Deployed to your infrastructure and tested in ChatGPT, Claude and a coding agent. | Your users can ask their assistant to do the work instead of opening your app. |
| Agent sign-in | OAuth so a user connects their existing account from the assistant, with a scope for each tool. Anything that spends money, deletes data or sends a message can require confirmation in your product first. | Agents act as a signed-in user with limits you set, not with a shared API key. |
| Directory listings | A connect page on your site, an Official MCP Registry entry, and prepared submissions to the directories where assistant users find tools. | People can find the server and connect it without emailing you. |
| Handover | The code in your repository, a short runbook, and a walkthrough with whoever will maintain it. | You own it and can change it without us. |
7 MCP servers we already run.
These are on Soxoa's own products, not client work. Connect any of them from your assistant today, and you will see the same kind of server you would get.
| Product | What an assistant can do | Sign-in | Connect |
|---|---|---|---|
| Postedly | Prepare a letter or fax, quote it, and hand the sender a review link before payment.https://postedly.com/mcp/send | OAuth account sign-in | Connect guide |
| Intakra | Review a sales account list and the dated buying signals behind each account.https://intakra.com/mcp | Public tools, plus OAuth for your workspace | Connect guide |
| MentionedOn | See how AI assistants describe a local business, then draft and verify website fixes.https://mentioned-on.com/mcp | Public tools, plus OAuth for your account | Connect guide |
| Portravo | Run a construction takeoff from plan PDFs and read back quantities and estimates.https://portravo.com/mcp | Public tools, plus OAuth for your account | Connect guide |
| Dokyumi | Extract structured data from business documents, with review before it lands.https://dokyumi.com/mcp | OAuth account sign-in | Connect guide |
| Ocolta | Connect paid bank-statement and paystub review summaries to an assistant.https://app.ocolta.com/mcp | OAuth account sign-in | Connect guide |
| Soxoa planning tools | Estimate automation value, rank workflows and draft a pilot plan.https://soxoa.com/mcp | No sign-in | Connect guide |
New to MCP? The Soxoa MCP guide walks through connecting a server from ChatGPT, Claude or Codex in about two minutes.
The two weeks, day by day.
Ten working days from kickoff to a live server. You see something working by day three.
| When | Work | You see |
|---|---|---|
| Day 1 | Kickoff. Agree the jobs an agent should be able to do in your product, which actions need a person to confirm, and get staging access. | A one-page tool plan you approve. |
| Days 2–3 | Write the tool names, inputs, limits and descriptions. Wire the first tools to your API against staging. | First tools callable from a test client. |
| Days 4–6 | Build out the rest of the tools, errors an assistant can recover from, and rate limits. Deploy to your infrastructure. | The full tool set running on staging. |
| Days 7–8 | Agent sign-in: OAuth with per-tool scopes, consent screen and token handling, connected to your existing accounts. | A user connects from ChatGPT or Claude with their own login. |
| Day 9 | Test real requests in ChatGPT, Claude and a coding agent. Fix any tool the model misreads or misuses. | A test log of what was asked, what ran and what was fixed. |
| Day 10 | Production release, connect page, registry entry and directory submissions. Walkthrough and runbook. | A live server you own, and the handover. |
One fixed price, agreed before work starts.
$5,000–$15,000Fixed price, set on the scoping call
Most builds land in this range. You get the exact figure in writing after the scoping call, before you commit. It does not grow during the build; anything new gets written down and priced separately.
What changes the price
- How many jobs agents need to do. A focused first set is cheaper than covering the whole app.
- Whether you already have a documented API the tools can call.
- Whether you already have OAuth or an identity provider agents can sign in through.
- Write actions that move money or send messages, which need confirmation flows.
- Hosting, security review or compliance steps your team requires before release.
Who builds it.
I'm John Arndt. I founded Soxoa and built every server in the table above, including the OAuth sign-in on Postedly, Intakra, MentionedOn and Portravo. Before Soxoa I spent more than a decade in AI, fraud and risk, payments and enterprise software.
You talk to me on the scoping call and I write the code. There is no account manager in between.
What I need from you.
Two weeks only works if these are ready on day one.
- API docs or read access to the code that serves your API.
- A staging environment and a test account with realistic data.
- One person who can answer product questions within a working day.
- A decision on which actions agents may take, and which need a person to confirm.
- Someone who can approve the production deploy, or access to do it.
- Your logo and product description for the listings.
Questions founders ask.
What is an MCP server, in plain terms?
The Model Context Protocol is the open standard ChatGPT, Claude and other assistants use to call tools in other software. An MCP server is the part of your product that tells an assistant what it can do, and then does it for the signed-in user.
Do we need an API already?
It helps a lot. If your product has an API, the server calls it. If it does not, the scoping call works out whether a few internal endpoints fit inside the two weeks, and that is reflected in the price before you agree to anything.
Who owns the code?
You do. It is written in your repository, deployed to your infrastructure, and handed over with a runbook. Nothing runs in a Soxoa account.
Can an agent do something damaging?
Only what you allow. Each tool has a scope, and actions that spend money, delete data or send a message on a user's behalf can require confirmation in your product before they run.
Will you get us listed in the ChatGPT and Claude directories?
We publish the Official MCP Registry entry and prepare and submit the directory listings. Curated directories review submissions on their own schedule, so acceptance and timing are up to them.
What if it does not fit in two weeks?
You find out on the scoping call, before you pay. If the full scope will not fit, you get a smaller first version that does and a written list of what comes after.
Who actually does the work?
John Arndt, who founded Soxoa and built the servers listed on this page. The person on the scoping call is the person who builds it.
Book the scoping call.
Thirty minutes. Bring your product URL and the jobs you want agents to do. You leave with a yes or no on two weeks, and a fixed price in writing afterwards.
Prefer email? john@soxoa.com · Open the calendar in a new tab
Loading the calendar. Open it on Cal.com instead.