agent_run
Run a local Agent by name. Executes via the Rotifer CLI (rotifer agent run <agent-name>). The Agent must exist in .rotifer/agents/. Returns stdout/stderr from the execution.
LABSCO SUMMARY
The publish path has a gate on it.
publish_gene runs a static security scan and refuses below grade B, and vg_scan lets you run the same check before you get there. In a registry of code other people will execute in their own sandbox, that gate is the difference between a package index and a supply-chain incident.
What it is
The MCP server for Rotifer, a registry and runtime for Genes — capability modules compiled to WASM. It searches the public registry, installs Genes locally, wraps your own functions or SKILL.md files as new ones, compiles and tests them in a sandbox, composes several into an Agent, and publishes back.
What you get
- Discovery — search_genes, get_gene_detail, get_arena_rankings with five-dimensional fitness, compare_genes, get_gene_stats, get_leaderboard, get_developer_profile, get_gene_reputation, list_gene_versions, suggest_domain
- Local workspace — list_local_genes, list_local_agents, install_gene
- Gene lifecycle — init_gene, scan_genes for candidate functions or SKILL.md files, wrap_gene, test_gene, compile_gene to WASM, run_gene, and doctor to check the TypeScript-to-WASM toolchain when compilation fails
- Agents — create_agent composes local Genes into a pipeline; agent_run executes it through the Rotifer CLI
- Publishing — publish_gene validates with a V(g) security scan and uploads; arena_submit records fitness metrics; vg_scan runs the same static safety analysis on its own
- Accounts — login opens a browser OAuth flow, plus logout, auth_status, get_my_reputation and get_mcp_stats
Requirements
The npm package @rotifer/mcp-server, run with npx over stdio. Node.js 20 or newer. Discovery and local work need no account; arena_submit and publish_gene require login, which opens a GitHub or GitLab OAuth flow in the browser and saves credentials locally. Compiling needs a local TypeScript-to-WASM toolchain — esbuild and javy — and doctor reports what is missing, since a broken toolchain is the usual reason compile_gene fails. Publishing requires a V(g) security grade of B or better.
Setup effort
One command — npx @rotifer/mcp-server
USE CASES
01
Finding a capability instead of writing one
Search by domain, compare candidates on fitness, and read the Arena ranking for that capability.
02
Turning a function you already have into a Gene
Scan the project for candidates, wrap one, and compile it to WASM.
03
Working out why a compile failed
Check the local toolchain first — a missing esbuild or javy is the usual cause.
04
Composing several Genes into a pipeline
Build the Agent from local Genes with a composition strategy, then run it.
05
Publishing without shipping a problem
Run the security scan and the sandbox tests yourself before the publish call enforces them.
06
Checking a Gene before installing it
Its phenotype and fitness, its reputation breakdown, and its version history with changelogs.
30 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
arena_submit
Submit a Gene to the Arena with fitness metrics. Requires authentication (rotifer login). Upserts the Gene's Arena entry with 5-dimensional fitness scores.
auth_status
Check current authentication status. Returns whether the user is logged in, their username, provider, and how many minutes until the token expires.
compare_genes
Compare two or more Genes by their F(g) fitness metrics. Returns side-by-side fitness breakdown.
compile_gene
Compile a local Gene to WASM via the Rotifer CLI (rotifer compile). The Gene must exist in the local genes/ directory. Returns compilation output.
create_agent
Create a new Agent by composing one or more local Genes. The Agent is saved to .rotifer/agents/ in the project. Genes must exist locally (wrap them first with wrap_gene).
doctor
Check the local TypeScript→WASM toolchain (esbuild / javy) and report what is missing or misconfigured. Read-only: inspects the environment and changes nothing. Use this when compile_gene fails — a missing or broken toolchain is the most common cause.
get_arena_rankings
Get Arena rankings for a domain with full 5-dimensional fitness metrics: fitness (F(g)), safety, success_rate, latency, and resource_efficiency. Use this to find the best Gene for a capability.
get_developer_profile
Get a creator's public profile and reputation data by username.
get_gene_detail
Get detailed information about a specific Gene by its ID or content_hash, including phenotype, fitness, and metadata. At least one of gene_id or content_hash must be provided.
get_gene_reputation
Get detailed reputation breakdown for a Gene (Arena, Usage, Stability scores).
get_gene_stats
Get download statistics for a Gene, broken down by time period (total, last 7 days, 30 days, 90 days).
get_leaderboard
Get the creator reputation leaderboard. Shows top creators ranked by reputation score, including their published gene count, total downloads, and arena wins.
get_mcp_stats
Get MCP Server call analytics for a given time period. Returns total calls, success rate, average latency, top tools, and top genes. Requires authentication.
get_my_reputation
Get the current logged-in creator's reputation and stats. Requires authentication.
init_gene
Initialize a new Rotifer Gene project. Creates a directory with phenotype.json template and starter files. Supports Wrapped, Hybrid, and Native fidelity types.
install_gene
Install a Gene from the Rotifer Cloud Registry into the local project. Downloads phenotype and metadata. Requires a valid gene_id from search_genes or get_gene_detail.
list_gene_versions
List the version history chain of a Gene by creator and name. Returns all published versions in chronological order with changelog entries and previous_version_id links.
list_local_agents
List Agents registered in the local project workspace. Returns each Agent's name, state, genome composition, strategy, and reputation. Agents are local constructs that compose multiple Genes into pipelines.
list_local_genes
List Genes installed in the local project workspace. Scans the genes/ directory for phenotype.json files and returns metadata, compile status, and cloud origin for each Gene.
login
Log in to Rotifer Cloud. Opens the browser for OAuth authorization (GitHub or GitLab). After the user authorizes in the browser, credentials are saved locally. This must be done before using arena_submit or publish_gene.
logout
Log out from Rotifer Cloud. Clears locally saved credentials.
publish_gene
Publish a Gene to Rotifer Cloud Registry (default destination since v0.8.8). Calling this tool = explicit publish consent. Requires authentication (use login tool first). Validates with V(g) security scan (Grade >= B required), uploads, and optionally submits to Arena. Either gene_name or all=true must be provided.
run_gene
Execute a local Gene via the Rotifer CLI (rotifer run). The Gene must exist in the local genes/ directory. Returns execution output.
scan_genes
Scan source files for candidate gene functions or local SKILL.md files that can be wrapped as Genes. Returns discovered candidates with metadata.
search_genes
Search the Rotifer Gene ecosystem. Returns a list of Genes matching the query, filterable by domain and fidelity.
suggest_domain
Suggest top matching domains from the domain registry based on a description.
test_gene
Test a Gene in the sandbox. Validates phenotype schema, runs input/output tests, and checks compilation.
vg_scan
V(g) security scan — static analysis for Gene/Skill code safety. Returns a grade (A/B/C/D/?) and per-finding details with severity, file, line, and snippet.
wrap_gene
Wrap a function or SKILL.md as a Rotifer Gene. Generates phenotype.json from the source. The target must exist in the project.
BEFORE YOU INSTALL
What to know first
Tools you get
30 tools when we connected; the project documents 31. rollback_gene is new and missing from older builds. ROTIFER_MCP_TOOLS or --tools= narrows the set (--tools=readonly gives 14, --tools=evolve 10), and excluded tools are refused by name.
Requires
- npx on PATH
- Node.js >= 20
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @rotifer/mcp-serverMCP Clients
Cursor, Claude Desktop, Windsurf
JSON
{
"mcpServers": {
"rotifer": {
"command": "npx",
"args": [
"@rotifer/mcp-server"
]
}
}
}Any MCP client — fewer tools
ANY MCP CLIENT — FEWER TOOLS · TERMINAL
npx @rotifer/mcp-server --tools=evolveAny MCP client — no sandbox
ANY MCP CLIENT — NO SANDBOX · TERMINAL
npx @rotifer/mcp-server --allow=no-sandbox,trust-unsigned
