Runitonai Mcp

io.github.StructLabs-ioPublished by GitHub account StructLabs-iov0.2.0Updated Oct 25, 2026

Read-only MCP connector serving the Run It on AI book; index and Implementation Blocks are free.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

A read-only companion server for the Run It on AI book, letting an assistant fetch the book index, chapters and Implementation Blocks.

What you can do
Load the companion's operating instructions and engagement modes via activate, meant to be called first when the user asks for help choosing or deploying AI in their business. List every chapter and appendix ID with its Implementation Block names, and fetch a full chapter or named section by slug. Retrieve structured Implementation Blocks (reader prompt, agent notes, target artifact) by chapter and name, free of charge. Several tools for section search, playbooks, telemetry and session history are stubs not implemented in Phase 1.
When to use it
Useful for readers of the Run It on AI book who want their assistant to pull chapter text and working exercises while discussing AI adoption, or to browse the free index and Implementation Blocks without a purchase.
Requirements
A remote streamable HTTP endpoint; no local install. Chapter text requires the reader's Gumroad license key passed as an access code; the activate instructions and Implementation Blocks need no credential. Connections are brokered through the assistant platform's cloud.
Before you install
The access code is a Gumroad license key that identifies a purchase; it is sent to the server, checked against Gumroad and cached as a hash for a day. Refunded or disabled keys stop working. The README states conversations, files, name and email are not received, and tool calls are seen by the platform's cloud rather than directly by the user's machine.

Installation

In SourceWeft

  1. Open Runitonai Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.StructLabs-io%2Frunitonai-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "runitonai": {
      "type": "http",
      "url": "https://mcp.runitonai.com/mcp"
    }
  }
}

README

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.

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/mcp

Start 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).

sh
claude mcp add --transport http runitonai-book https://mcp.runitonai.com/mcp

Codex. In ~/.codex/config.toml:

toml
[mcp_servers.runitonai_book]url = "https://mcp.runitonai.com/mcp"

What is in this repo

PathWhat it is
src/worker.tsThe Cloudflare Worker: routing, transports, the Gumroad sync endpoint
src/license.tsLicense-key verification and caching (the access gate)
src/auth.tsVerification of legacy bearer tokens (nothing mints new ones)
src/rate_limit.tsPer-key rate limiting
src/mcp/MCP protocol plumbing (tool catalog, dispatch, transports)
src/tools/The tools your AI can call
openapi-v1.yamlThe same surface described for ChatGPT Actions
implementation-blocks/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

sh
npm installnpm run typechecknpm run dev        # local server on localhost:8787

wrangler.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.

Source: README.md at commit d8fb21d

Tools

11

activate

Start here. Returns the Run It on AI companion's full operating instructions (engagement modes, routing, voice rules, tool usage). Call this FIRST — before any other tool — when the user says "Activate Run It on AI", mentions the Run It on AI ebook, or asks for help choosing/deploying AI in their business. No authentication.

Takes no parameters.

list_book_index

Discovery: every valid chapter_id with its title — front matter, all chapters, AND all appendices (e.g. appendix-b-online-reference) — plus Implementation Block names per chapter. Call this whenever unsure which chapter_id to use. No authentication.

Takes no parameters.

lookup_chapter

Fetch a full chapter or a named section by slug — works for appendices too. Buyer-gated: pass the reader's access_code (their Gumroad license key). Unsure of the slug? Call list_book_index first.

Parameterssectionchapter_idrequiredaccess_code

get_implementation_block

Fetch a structured Implementation Block (reader_prompt, agent_notes, target_artifact) by chapter and name. Free to call — no access code needed; the Implementation Blocks are public (they also ship in the open-source server repo).

Parametersnamechapter_idrequired

find_section

Stub — not implemented in Phase 1. See tool response 'phase' field.

Takes no parameters.

find_playbook

Stub — not implemented in Phase 1. See tool response 'phase' field.

Takes no parameters.

get_playbook

Stub — not implemented in Phase 1. See tool response 'phase' field.

Takes no parameters.

report_telemetry

Stub — not implemented in Phase 1. See tool response 'phase' field.

Takes no parameters.

get_session_history

Stub — not implemented in Phase 1. See tool response 'phase' field.

Takes no parameters.

save_session_state

Stub — not implemented in Phase 1. See tool response 'phase' field.

Takes no parameters.

forget_session_history

Stub — not implemented in Phase 1. See tool response 'phase' field.

Takes no parameters.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts