Discover mcp

Skill kenantang/codex-and-claude-skills/collected-academic-research-skills/sources/rand__cc-polymath/skills/discover-mcp

Automatically discover MCP (Model Context Protocol) skills when building MCP servers, designing tools, implementing resources/prompts, or testing MCP integrations. Activates for MCP server development tasks.From its SKILL.md

Install

npx -y skills add kenantang/codex-and-claude-skills --skill discover-mcp

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.7 KB, 788 tokens by cl100k_base, as published. Nobody here has run it

MCP Skills Discovery

Provides automatic access to comprehensive MCP server development, tool design, and testing skills.

When This Skill Activates

This skill auto-activates when you're working with:

Building MCP servers (TypeScript or Python)
Designing MCP tools, resources, or prompts
Choosing MCP transports (stdio, SSE, Streamable HTTP)
Implementing JSON-RPC 2.0 over MCP
Testing MCP servers with Inspector or automated tests
Debugging MCP protocol or transport issues
Publishing or deploying MCP servers

Available Skills

Quick Reference

The MCP category contains 3 specialized skills:

mcp-server-fundamentals - Architecture, transports, tools/resources/prompts primitives, SDK setup
mcp-tool-design - Tool naming, schemas, error handling, annotations, progressive disclosure
mcp-testing - Inspector, unit tests, integration tests, transport debugging, CI/CD

Load Full Category Details

For complete descriptions and workflows:

Read ../mcp/INDEX.md

This loads the full MCP category index with:

Detailed skill descriptions
Usage triggers for each skill
Common workflow combinations
Cross-references to related skills

Load Specific Skills

Load individual skills as needed:

Server architecture and setup

Read ../mcp/mcp-server-fundamentals.md

Tool design and best practices

Read ../mcp/mcp-tool-design.md

Testing and debugging

Read ../mcp/mcp-testing.md

Common Workflows

New MCP Server

Sequence: Fundamentals -> Tool Design -> Testing

Read ../mcp/mcp-server-fundamentals.md # Architecture, transport, SDK Read ../mcp/mcp-tool-design.md # Design tool interfaces Read ../mcp/mcp-testing.md # Test with Inspector, CI

Adding Tools to Existing Server

Sequence: Tool Design -> Testing

Read ../mcp/mcp-tool-design.md # Naming, schemas, errors Read ../mcp/mcp-testing.md # Test new tools

Debugging MCP Issues

Sequence: Testing -> Fundamentals

Read ../mcp/mcp-testing.md # Inspector, transport debugging Read ../mcp/mcp-server-fundamentals.md # Lifecycle, capabilities

Integration with Other Skills

MCP skills commonly combine with:

API skills (discover-api):

MCP servers wrapping REST or GraphQL APIs
Authentication for MCP tool backends

Testing skills (discover-testing):

Comprehensive test strategies
Contract testing patterns

Infrastructure skills (discover-infra, discover-cloud):

Deploying MCP servers
Scaling HTTP transports

Progressive Loading

This gateway skill (~170 lines, ~1.5K tokens) enables progressive loading:

Level 1: Gateway loads automatically (you're here now)
Level 2: Load category INDEX.md (~2.5K tokens) for full overview
Level 3: Load specific skills (~2-3K tokens each) as needed

Total context: 1.5K + 2.5K + skill(s) = 4-8K tokens vs 12K+ for everything.

Quick Start Examples

"Build an MCP server": Read ../mcp/mcp-server-fundamentals.md

"Design MCP tools for my API": Read ../mcp/mcp-tool-design.md

"Test my MCP server": Read ../mcp/mcp-testing.md

"Debug why my MCP tool isn't showing up": Read ../mcp/mcp-testing.md

Next Steps: Run Read ../mcp/INDEX.md to see full category details, or load specific skills using the commands above.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most mcp tooling skills give in 788 tokens

Counted across 780 of the 1,136 authors here whose files we hold, read 2026-09-06

Use Zod for input validationin 34 of 780, across 21 files
Use stdio for local clientsin 27 of 780, across 10 files
Restart Claude Code after configurationin 26 of 780, across 23 files
Verify MCP server connection before using toolsin 23 of 780, across 17 files
Define input schemas for every toolin 20 of 780, across 11 files
Use Streamable HTTP for remote clientsin 18 of 780, across 8 files
Pin SDK version in package.jsonin 17 of 780, across 6 files
Keep server logic independent of transportin 16 of 780, across 6 files
Verify SDK methods against official documentationin 15 of 780, across 5 files
Format evaluation results as an XML filein 15 of 780, across 12 files
Test servers using the MCP Inspectorin 15 of 780, across 14 files
Create ten complex and independent evaluation questionsin 14 of 780, across 11 files

Said here and by no other author read

load specific MCP skill files as needed
follow the recommended sequence for server development
use progressive loading to manage context tokens

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.