Write it anywhere. Merge it yourself.
A remote MCP server for ashutoshverma.dev. Any client that speaks MCP can read the site, save a draft, and open a pull request. Publishing stops at the pull request. The merge stays with you.
- 1.0 draft
- 2.0 save
- 3.0 publish
- 4.0 merge
The posts that got written were the ones that survived the laptop.
Publishing meant opening the laptop, finding the repo, copying a template, getting the metadata block exactly right, committing, pushing, waiting for Vercel. Drafting from a phone was not possible at all.
So the idea you had on a train did not survive. This server is the shortest path from that idea to a preview URL, and deliberately nothing more.
How a thought becomes a page
-
1.0Draft
In any client that speaks MCP: a desktop app, a browser, a phone. get_skill serves the rules for the kind of content you are writing, plus be-human, the voice. The model does the writing. The server only moves bytes.
-
2.0Save
save_draft writes real MDX into workshop, a private repo. It commits straight to main, because nothing in there is public yet. A draft can be read back, rewritten, or thrown away.
-
3.0Publish
publish checks the draft against the site's live schema, cuts a branch on portfolio, and opens a pull request. The server does not parse the MDX. The Vercel preview on that pull request is the check. Saying "publish it" twice still leaves one pull request.
-
4.0Merge
Vercel builds a preview of the pull request. You read the preview, then you press merge. There is no tool for this stage. The model has no path to that button.
Three repos, one process
This repo is the server. The site and the drafts live in two other GitHub repos. Nothing is cloned. A client calls the tools over HTTP, and the server reads and writes through the GitHub API and the site's JSON routes.
| Repo | Holds | This server |
|---|---|---|
| portfolio | The public site and published MDX | Opens a pull request. Never commits to main |
| workshop | Drafts, skills, templates, the social-post archive | Reads, and commits straight to main |
| blog-mcp | This server | Runs on Fly.io, at mcp.ashutoshverma.dev |
Inside the process the chain is tools, then services, then lib. A tool only speaks MCP. A service decides. lib talks to GitHub and the site.
GET /health is the liveness probe and does no I/O. The deep check and the MCP endpoint sit behind an unguessable path. A wrong secret matches no route and looks like any other 404.
Six tools
The model is the caller here, not a person. Tool names and error strings are its whole interface, which makes their wording part of the product rather than polish.
| Tool | What it does | Reach |
|---|---|---|
| list_content | Published catalogue from the site, or draft slugs from workshop | site or workshop · read |
| get_content | One draft, or one published item, by slug | site or workshop · read |
| get_skill | The rules for one kind of content, plus the voice | workshop · read |
| save_draft | Write or replace a draft | workshop · write |
| publish | Open a pull request on the public site | portfolio · PR only |
| discard_draft | Delete a draft | workshop · write |
The tool opens the pull request. A person merges it.
Everything else follows from that. A slug that is already published cannot be touched without an explicit revise flag. No repo is ever cloned, so there is no stale checkout waiting to surprise anyone. Auth is one unguessable secret in the URL path — there is exactly one user, which is the one case OAuth adds nothing to.
The phone is the dangerous client: no diff to read, and a distracted reader. Every refusal in the design exists for that case.
What it runs on
- Runtime
- Bun · TypeScript, strict
- Server
- Elysia · the MCP TypeScript SDK
- Validation
- Zod, at every boundary
- Tooling
- Biome · bun:test
- Host
- Fly.io — one small machine that stops itself when idle
- Storage
- None. Every read and write goes through the GitHub API
- Status
- All six tools built.
An idea on a train now reaches a preview URL with no laptop involved.