Run It on AI
OfficialValidates license keys against Gumroad to control access to chapter text.
Run It on AI — the companion server, in full
This repository is the complete source code of the server that powers the
Run It on AI reading companion at mcp.runitonai.com. If you bought the
book and connected your AI to it, this is everything that runs on our side.
We publish it so you do not have to take our word for anything. The server is a few hundred lines of TypeScript. You (or your AI — paste any file into it and ask) can read exactly what it does and, just as importantly, what it cannot do.
The short version
What reaches our server when you use the companion:
The name of the tool your AI called (for example "fetch chapter 3").
The chapter or exercise it asked for.
Your access code — the license key printed on your Gumroad receipt.
What never reaches us, because there is no code here that could receive, store, or forward it:
Your conversations with your AI.
Your files, documents, or anything on your machine.
Your name.
Your email. Search this repository for an email field: there is none. No tool, no endpoint, no code path accepts one.
The picture your AI forms of you while you work. That stays inside your AI, on your side.
Who talks to whom: when you add the companion as a Claude connector, your machine never contacts our server directly — Anthropic's cloud brokers the connection. On ChatGPT, OpenAI's cloud does. We see tool calls, not you.
Related MCP server: IBM Content Services MCP Server
How access works
Your credential is the license key on your Gumroad receipt (a code like
XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX). It identifies a purchase, not a
person. The server checks it against Gumroad, caches a hash of it for a day,
and rate-limits it. Refunded or disabled keys stop working. See
src/license.ts — the whole mechanism is one file.
Only chapter text needs the key. The companion's operating instructions
(activate) and every Implementation Block — the book's working exercises —
are served without any credential at all; the exercises are also published
right here in implementation-blocks/.
Connect it
Claude (web or desktop) — the easy path. Settings -> Connectors -> Add custom connector, then paste:
https://mcp.runitonai.com/mcpStart a chat with: Activate Run It on AI — my access code is <your license key>.
ChatGPT. Use the "Run It on AI Companion" GPT (link in the book), or
build your own: create a Custom GPT and import
https://mcp.runitonai.com/openapi.yaml as an Action.
Claude Code (terminal users).
claude mcp add --transport http runitonai-book https://mcp.runitonai.com/mcpCodex. In ~/.codex/config.toml:
[mcp_servers.runitonai_book]
url = "https://mcp.runitonai.com/mcp"What is in this repo
Path | What it is |
| The Cloudflare Worker: routing, transports, the Gumroad sync endpoint |
| License-key verification and caching (the access gate) |
| Verification of legacy bearer tokens (nothing mints new ones) |
| Per-key rate limiting |
| MCP protocol plumbing (tool catalog, dispatch, transports) |
| The tools your AI can call |
| The same surface described for ChatGPT Actions |
| Every Implementation Block from the book, as readable markdown |
Two data files ship as placeholders: src/data/chapters.json (the book's
chapter text) and src/data/skill.json (the companion's operating
instructions). Both are generated from the book manuscript at deploy time.
The book's prose is the product, so it is not in the public repo — but the
code that serves it is all here, and the Implementation Blocks (the working
exercises) are published in full in implementation-blocks/.
Note for contributors: everything in this repo is generated from the private manuscript repo by a sync script, and a pre-commit hook there re-syncs it on every relevant change. The Implementation Blocks live in the book's manuscript; the copies here are build artifacts — never edit them here, they will be overwritten.
Run it yourself
npm install
npm run typecheck
npm run dev # local server on localhost:8787wrangler.toml ships with placeholder KV namespace ids; point them at your
own Cloudflare account if you want to self-host the shell.
License
MIT — see LICENSE. The book itself (chapters, companion instructions) remains copyrighted content of StructLabs.io Pte Ltd and is not part of this repository.
This server cannot be installed
Maintenance
Related MCP Servers
- Alicense-qualityDmaintenanceProvides RAG (Retrieval Augmented Generation) access to technical documentation through MCP, enabling LLMs to search and retrieve relevant documentation on-demand.Last updated4MIT
- AlicenseAqualityBmaintenanceEnables AI models to access IBM FileNet Content Manager capabilities including document management, property extraction, legal holds, and AI-powered document insight through standardized MCP interfaces.Last updated30Apache 2.0
- Flicense-qualityBmaintenanceProvides access to self-contained, runnable implementation patterns across multiple programming languages via MCP tools for searching and retrieving documentation and code examples.Last updated
- AlicenseAqualityAmaintenanceRead-only MCP server that exposes the agentic-os governance, SDLC, and Quality Engineering methodology to any MCP host. It never writes to your repository and never executes code — it serves the methodology, plans an install, and verifies it, handing any commands back to the host to run.Last updated27Apache 2.0
Related MCP Connectors
Read-only Remote MCP for externally grounded AI agent trust receipts.
Your memory, everywhere AI goes. Build knowledge once, access it via MCP anywhere.
Self-hosted MCP gateway: turn any API, database or MCP server into AI connectors — no code.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/StructLabs-io/runitonai-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server