MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Set up Rigor's bundled MCP server for an AI coding agent and verify the connection.
$ npx skills add rigortype/rigor --skill rigor-mcp-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rigortype/rigor rigor-mcp-setup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/rigor-mcp-setup .claude/skills/rigor-mcp-setup && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "rigor-mcp-setup" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-mcp-setup into .claude/skills/rigor-mcp-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-mcp-setup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rigortype/rigor/tree/master/skills/rigor-mcp-setupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rigortype/rigor --skill rigor-mcp-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rigortype/rigor rigor-mcp-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/rigor-mcp-setup .agents/skills/rigor-mcp-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rigor-mcp-setup" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-mcp-setup into .agents/skills/rigor-mcp-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-mcp-setup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rigortype/rigor --skill rigor-mcp-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rigortype/rigor rigor-mcp-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/rigor-mcp-setup .cursor/skills/rigor-mcp-setup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "rigor-mcp-setup" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-mcp-setup into .cursor/skills/rigor-mcp-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-mcp-setup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rigortype/rigor.git --path skills/rigor-mcp-setup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rigortype/rigor --skill rigor-mcp-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rigortype/rigor rigor-mcp-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/rigor-mcp-setup .gemini/skills/rigor-mcp-setup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "rigor-mcp-setup" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-mcp-setup into .gemini/skills/rigor-mcp-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-mcp-setup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rigortype/rigor rigor-mcp-setupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rigortype/rigor --skill rigor-mcp-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/rigor-mcp-setup .github/skills/rigor-mcp-setup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "rigor-mcp-setup" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-mcp-setup into .github/skills/rigor-mcp-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-mcp-setup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rigortype/rigor --skill rigor-mcp-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rigortype/rigor rigor-mcp-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/rigor-mcp-setup .opencode/skills/rigor-mcp-setup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "rigor-mcp-setup" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-mcp-setup into .opencode/skills/rigor-mcp-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-mcp-setup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
rigor-mcp-setupSet up Rigor's bundled MCP server for an AI coding agent and verify the connection.
Rigor MCP Setup is an agent skill from rigortype/rigor. Set up Rigor's bundled MCP server for an AI coding agent and verify the connection. Use when wiring rigor mcp into Claude Code, Cursor, Cline, or another MCP client; not for editor LSP or CI setup.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: Inference-first static analysis for Ruby. The licence is MPL-2.0.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 57a67cf. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Rigor MCP Setup loads about 1.3k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 631 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from rigortype/rigor at commit 57a67cf, republished under its MPL-2.0 licence (© rigortype). 631 words, ~1,271 tokens.
.claude/skills/rigor-mcp-setup/SKILL.md (or your agent's skills folder).rigor mcp is the Model Context Protocol server bundled with the
rigortype gem. It exposes Rigor's analysis as JSON-RPC tool calls over
stdio, so an AI coding agent can call Rigor directly during a session —
check types before a refactor, look up the type at a cursor, or triage a
project's diagnostics as review context. All tools are read-only
(write-side commands like rigor init / sig-gen --write are
deliberately excluded — modifying files stays the developer's call).
The authoritative, per-client configuration lives in the manual. With Rigor installed, read it offline with no network round-trip:
rigor docs mcp-server(Web fallback, only before Rigor is installed: Rigor MCP Server — AI Agent Integration.) This skill is the workflow around it (identify the client → apply the manual's snippet → verify the handshake), so it does not duplicate (and cannot stale-out) the config details.
The config details already come live from rigor docs; this keeps the
workflow itself current too. Prefer the copy of this skill that ships
with the installed Rigor over any vendored or frozen copy of this file:
rigor skill --full rigor-mcp-setupIf you already loaded this skill via rigor skill you have the current
copy — just proceed. If rigor is not on PATH, this task needs it: run
rigor-next-steps to install Rigor first, then come back.
.mcp.json, .cursor/mcp.json)
and you want to add Rigor to it for the whole team.rigor-editor-setup (rigor lsp).rigor-project-init first
(the MCP tools use the same .rigor.yml discovery as rigor check).rigor_check, rigor_type_of, rigor_triage, rigor_annotate,
rigor_sig_gen, rigor_explain, rigor_coverage — each the JSON form
of the matching rigor CLI command. See the manual's Tool reference
for inputs and outputs.
Every client config simply launches rigor mcp (stdio) and needs
rigor on the agent's PATH — the same executable rigor check
uses. For agents that do not inherit your shell, the mise shim path is
the most reliable channel (see rigor docs install, or
Installing Rigor
on the web). Do not add rigortype to the project's Gemfile — it
is a tool, not a library.
rigor check <a-file-or-dir>The MCP tools share rigor check's config discovery. If check works
from the project root, the tools will too.
Ask the developer which agent they use, or detect a committed config
(.mcp.json, .cursor/mcp.json, .claude/settings.json). Apply the
matching snippet from the manual's Client wiring section verbatim —
it covers Claude Desktop, Claude Code CLI, Cursor, Cline, and a generic
stdio client:
rigor docs mcp-server(or, pre-install, the web copy: https://github.com/rigortype/rigor/blob/master/docs/manual/10-mcp-server.md)
Each snippet is the same shape — {"command": "rigor", "args": ["mcp"]}.
If the project commits a shared MCP config, add the Rigor entry there and
commit it so every contributor gets it.
Working-directory gotcha (from the manual's Troubleshooting): the
server discovers config from the directory it is launched in. If the
client starts rigor mcp from $HOME or a temp dir, no .rigor.yml is
found and tools return an empty set. Pin it with
"args": ["mcp", "--config=/abs/path/.rigor.yml"], or pass absolute
paths in the tool call.
Confirm rigor mcp answers the MCP initialize request:
echo '{"jsonrpc":"2.0","id":0,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0"}}}' | rigor mcpA JSON result with serverInfo.name: "rigor" means it works; nothing
or a shell error means rigor is not on the PATH the client uses. Then
restart the client and confirm the rigor_* tools appear in its tool
palette.
Re-run rigor skill describe for the next move — with the agent able to
call Rigor's tools, raising protection (rigor-protection-uplift) or
reducing a baseline (rigor-baseline-reduce) is a tighter loop.
© rigortype, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/rigor-mcp-setup of rigortype/rigor.
Open the folder on GitHubat commit 57a67cf
Rigor MCP Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Rigor MCP Setup this skillrigortype/rigor | 106 | — | ~1.3k | Automated safety check: Pass | MPL-2.0 | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 5 repos | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Context Mode Output Sandboxmksglu/context-mode | 26k | — | ~4.1k | Automated safety check: Pass | Custom licence |
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
mksglu/context-mode
Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.
warpdotdev/warp
Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.
rigortype/rigor
Measure Rigor's baseline drift across the tagged history of a real OSS Ruby project.
rigortype/rigor
Adjudicate a rigor unused report safely before proposing dead-code removal.
rigortype/rigor
Reduce an existing .rigor-baseline.yml rule by rule by triaging sites, fixing or intentionally suppressing them, and regenerating the baseline.
rigortype/rigor
Validate that a project's Rigor configuration, plugins, paths, and baseline are actually healthy.
rigortype/rigor
Author a new Rigor plugin, choosing plugins/ for production support or examples/ for a contract walkthrough.
rigortype/rigor
Author a Rigor plugin in an adopting project or standalone rigor- gem for a DSL, framework, or metaprogramming pattern.
Works with
Categories
Set up Rigor's bundled MCP server for an AI coding agent and verify the connection. Rigor MCP Setup is an agent skill from rigortype/rigor. Set up Rigor's bundled MCP server for an AI coding agent and verify the connection.
Rigor MCP Setup fits situations like: wiring rigor mcp into Claude Code; another MCP client; not for editor LSP.
Run `npx skills add rigortype/rigor --skill rigor-mcp-setup -a claude-code`. Or copy the skill folder (skills/rigor-mcp-setup in rigortype/rigor) into .claude/skills/rigor-mcp-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add rigortype/rigor --skill rigor-mcp-setup -a codex`. Or copy the skill folder (skills/rigor-mcp-setup in rigortype/rigor) into .agents/skills/rigor-mcp-setup in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rigortype/rigor --skill rigor-mcp-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rigor-mcp-setup, .gemini/skills/rigor-mcp-setup, .github/skills/rigor-mcp-setup and .opencode/skills/rigor-mcp-setup in your project.
SKILL.md names no scripts, command-line tools or credentials: Rigor MCP Setup is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Rigor MCP Setup is published under the MPL-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Rigor MCP Setup: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Crush Configuration (charmbracelet/crush, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
rigortype (a GitHub organization) maintains it in rigortype/rigor, which has 106 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 8, 2026.
Source: rigortype/rigor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.