ck:mcp-management

A toolkit for finding, understanding, and using MCP servers and the tools or data they expose. MCP is a standard connection between AI agents and external tools, services, or resources.

In plain words
What is it for?
Use it to discover MCP tools, prompts, and resources, choose capabilities for a task, run MCP operations, and manage several MCP servers.
Why use it?
It helps select only the relevant capabilities from multiple servers instead of loading every available tool into the working context. It also supports managing server configurations and executing discovered tools.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/manhvann/codexkit/mcp-management
Any agent
npx skills add manhvann/codexkit --skill mcp-management
Clone the repo
git clone --depth 1 https://github.com/manhvann/codexkit

Made for: Claude Code, Codex.

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,802 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.01802
Opus 5 $0.00018 $0.00901
Sonnet 5 $0.00007 $0.00360
Haiku 4.5 $0.00004 $0.00180

Measured 3d ago against content hash a77f521f2bce, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ck:mcp-management scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/cli.ts, scripts/mcp-client.ts), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/skills/mcp-management/SKILL.md · 211 lines

How it starts

The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MCP Management

Skill for managing and interacting with Model Context Protocol (MCP) servers.

Overview

MCP is an open protocol enabling AI agents to connect to external tools and data sources. This skill provides scripts and utilities to discover, analyze, and execute MCP capabilities from configured servers without polluting the main context window.

Key Benefits:

  • Progressive disclosure of MCP capabilities (load only what's needed)
  • Intelligent tool/prompt/resource selection based on task requirements
  • Multi-server management from single config file
  • Context-efficient: subagents handle MCP discovery and execution
  • Persistent tool catalog: automatically saves discovered tools to JSON for fast reference

When to Use This Skill

Use this skill when:

  1. Discovering MCP Capabilities: Need to list available tools/prompts/resources from configured servers
  2. Task-Based Tool Selection: Analyzing which MCP tools are relevant for a specific task
  3. Executing MCP Tools: Calling MCP tools programmatically with proper parameter handling
  4. MCP Integration: Building or debugging MCP client implementations
  5. Context Management: Avoiding context pollution by delegating MCP operations to subagents

Core Capabilities

1. Configuration Management

MCP servers configured in .codex/.mcp.json.

Gemini CLI Integration (recommended): Create symlink to .gemini/settings.json:

mkdir -p .gemini && ln -sf .codex/.mcp.json .gemini/settings.json

See references/configuration.md and references/gemini-cli-integration.md.

GEMINI.md Response Format: Project root contains GEMINI.md that Gemini CLI auto-loads, enforcing structured JSON responses:

{"server":"name","tool":"name","success":true,"result":<data>,"error":null}

This ensures parseable, consistent output instead of unpredictable natural language. The file defines:

  • Mandatory JSON-only response format (no markdown, no explanations)
  • Maximum 500 character responses
  • Error handling structure
  • Available MCP servers reference

Read the full file on GitHub · 211 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 211 lines · 37 tokens per session scan A a77f521f2bce

Subscribe to this mod's changes

ck:mcp-management is a skill published in the GitHub repository manhvann/codexkit (88 stars, last pushed 5d ago), licensed MIT. It adds 37 tokens to every session and 1,802 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens