Run any Skill in Manus with one click

Get Started

mcp-install

Install, validate, and manage MCP servers for OMK using the curated catalog and parallel processing.

Run Skill in Manus

Overview

Install, validate, and manage MCP servers for OMK using the curated catalog and parallel processing.

Install command

npx skills add https://github.com/dmae97/oh-my-kimi --skill mcp-install

Copy and paste this command into Claude Code to install the skill

Source

dmae97/oh-my-kimi

Stars83

Forks8

UpdatedMay 17, 2026 at 16:49

SKILL.md

readonly

name	mcp-install
description	Install, validate, and manage MCP servers for OMK using the curated catalog and parallel processing.

MCP Server Installation Skill

Guide for adding MCP servers to an OMK project using the built-in catalog and parallel orchestration.

Commands

# List configured MCP servers
omk mcp list

# Diagnose all MCP servers
omk mcp doctor

# Diagnose a specific server
omk mcp doctor <server-name>

# Install a single MCP server
omk mcp install <name> <command> [args...]

# Remove a server from project-local config
omk mcp remove <name>

# Sync global MCP servers into project
omk mcp sync-global

Curated Catalog

OMK ships with a verified catalog in src/mcp/server-catalog.ts (or accessible via the runtime). Recommended categories:

reasoning: sequential-thinking — structured problem solving
memory: memory — persistent knowledge graph
docs: pdf — PDF text extraction
web: puppeteer — browser automation
devtools: filesystem, sqlite — file and database access
ops: railway — remote Railway MCP; supabase — database management and edge functions

Parallel Installation

When installing multiple servers (e.g., during omk init), OMK uses Promise.all for parallel setup. Agents and hooks can also trigger bulk installs:

Agent lane: explorer validates which servers are needed
Coder lane: writes the MCP JSON entries
QA lane: runs omk mcp doctor to verify each server
Hook: post-init-mcp.sh runs non-blocking validation after init

Rules

Prefer npx -y <package> so no global install is required.
Use ${PROJECT_ROOT} and ${DB_PATH} placeholders in catalog entries; they are resolved at install time.
Do not commit secrets in mcp.json env values.
Run omk mcp doctor after adding servers to confirm they start.
If a server fails to start, check startup_timeout_sec and network access.

When to Use

During omk init when selecting additional MCP servers.
When a task requires a new capability (browser, PDF, database).
Before reporting an MCP issue, run omk mcp doctor --json for structured evidence.

More from this repository

same repository

open-design

dmae97/oh-my-kimi

Launch nexu-io Open Design on localhost so OMK/Kimi can generate prototypes, decks, and design artifacts in a local web UI.

2026-05-2283

provider

dmae97/oh-my-kimi

Slash command for safe OMK provider routing, doctor checks, and OAuth/login guidance without exposing secrets.

2026-05-2283

omk-adaptorch-orchestration-review

dmae97/oh-my-kimi

Review AdaptOrch, OMK, and similar DAG multi-agent orchestration frameworks. Use when assessing DAG node responsibility, dependency edges, worker write authority, fallback/retry/timeout/evidence gates, review/merge boundaries, or reproducible decision traces.

2026-05-1783

omk-control-loop-debugger

dmae97/oh-my-kimi

Diagnose agent, runtime, tool, hook, context, provider-routing, DAG, retry, fallback, and evidence-gate failures using an industrial automation feedback-control loop. Use when workflows oscillate, stall, lose context, misroute tools, or need setpoint/sensor/controller/actuator/disturbance/correction analysis.

2026-05-1783

omk-evidence-contract

dmae97/oh-my-kimi

Generate task-specific evidence contracts before a done/completed claim. Use for feature, bugfix, refactor, research, release, security, docs, or orchestration tasks that need changed files, non-empty diffs, test/build/typecheck results, citations, uncertainty, conflicting evidence, and final risk notes.

2026-05-1783

agentmemory

dmae97/oh-my-kimi

Persistent memory, recall, session replay, and memory-governance workflow adapted from rohitg00/agentmemory for OMK. Use when setting up agent memory, deciding what to remember, importing/replaying sessions, reducing repeated context, or auditing memory safety.

2026-05-1383

Source

dmae97

dmae97/oh-my-kimi

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Network and Computer Systems AdministratorsComputer and Mathematical Occupations15-1244L4

name	mcp-install
description	Install, validate, and manage MCP servers for OMK using the curated catalog and parallel processing.

MCP Server Installation Skill

Guide for adding MCP servers to an OMK project using the built-in catalog and parallel orchestration.

Commands

# List configured MCP servers
omk mcp list

# Diagnose all MCP servers
omk mcp doctor

# Diagnose a specific server
omk mcp doctor <server-name>

# Install a single MCP server
omk mcp install <name> <command> [args...]

# Remove a server from project-local config
omk mcp remove <name>

# Sync global MCP servers into project
omk mcp sync-global

Curated Catalog

OMK ships with a verified catalog in src/mcp/server-catalog.ts (or accessible via the runtime). Recommended categories:

reasoning: sequential-thinking — structured problem solving
memory: memory — persistent knowledge graph
docs: pdf — PDF text extraction
web: puppeteer — browser automation
devtools: filesystem, sqlite — file and database access
ops: railway — remote Railway MCP; supabase — database management and edge functions

Parallel Installation

When installing multiple servers (e.g., during omk init), OMK uses Promise.all for parallel setup. Agents and hooks can also trigger bulk installs:

Agent lane: explorer validates which servers are needed
Coder lane: writes the MCP JSON entries
QA lane: runs omk mcp doctor to verify each server
Hook: post-init-mcp.sh runs non-blocking validation after init

Rules

Prefer npx -y <package> so no global install is required.
Use ${PROJECT_ROOT} and ${DB_PATH} placeholders in catalog entries; they are resolved at install time.
Do not commit secrets in mcp.json env values.
Run omk mcp doctor after adding servers to confirm they start.
If a server fails to start, check startup_timeout_sec and network access.

When to Use

During omk init when selecting additional MCP servers.
When a task requires a new capability (browser, PDF, database).
Before reporting an MCP issue, run omk mcp doctor --json for structured evidence.