← All writing
field note · 2026 · draft

Why I turned our #1 ticket into an MCP tool

Thirty percent of our queue was the same four-minute click-path. Here's what happened when I taught it to speak English instead.

(Placeholder structure — replace this body with your writing. Edit this file at src/content/writing/why-i-turned-our-top-ticket-into-an-mcp-tool.md.)

Open with the moment it clicked — the specific Tuesday, the specific ticket, the specific person. One concrete paragraph, no throat-clearing.

The setup

What the world looked like before: the queue, the click-path, the cost nobody was measuring. Give the reader the “before” in numbers if you have them.

One line worth pulling out — the sentence someone would screenshot.

What I actually did

The build, the decision, the tradeoff. Keep the technical detail real but skimmable — the reader should feel the competence without needing to hold the architecture.

What it taught me

The takeaway that outlives the tool. This is the part that makes it writing instead of documentation.