Skip to content
SkillModel-led1,181 tokens in use

MCP Developer

Builds and debugs Model Context Protocol servers and clients in TypeScript or Python: tools, resources, prompts, schema validation and stdio, HTTP and SSE transports.

12,471 stars on the repository MIT LicenseJeffallan/claude-skills · skills/mcp-developer
/plugin marketplace add jeffallan/claude-skills /plugin install fullstack-dev-skills@fullstack-dev-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing MCP Developer costs

78tokens idle
1,181tokens in use
11,899tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetectednetworkdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter15/15
  • Structure22/25
  • Examples15/15
  • Output15/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance100
  • Community60
  • Maturity36
  • Momentum40

MCP Developer guides Claude through MCP work in six steps: analyze requirements, scaffold a project, design tool schemas and resource URIs, implement handlers and a transport, test with the MCP Inspector and deploy with auth and rate limiting. The test step has a feedback loop for schema errors and malformed responses.

Five reference files cover the protocol, the TypeScript SDK, the Python SDK, tool definitions and resource providers.

What You Get

  • A scaffolded MCP server or client in TypeScript or Python
  • Tool definitions with JSON Schema, Zod or Pydantic validation and structured error handling
  • Resource providers with URI schemes, templates, subscriptions and path checks
  • Prompt templates and a client that lists and calls tools
  • A test loop with the MCP Inspector and notes on protocol versions and the initialize handshake

Common Use Cases

  • Exposing a database or internal API to an AI assistant as MCP tools
  • Serving files or schemas as MCP resources
  • Writing a Python MCP server with FastMCP
  • Debugging a tool that returns malformed JSON-RPC responses
  • Adding authentication and rate limiting before deploying a server

What Makes It Unique

It is about the protocol itself and shows each pattern in both TypeScript and Python. The test step runs the MCP Inspector with a stated fix loop for schema failures, and the references include security patterns such as table-name checks for query tools, path containment for file resources, rate limiting, idempotency keys and timeouts.

Under The Hood

The skill is a SKILL.md with five reference files and no scripts, and the references load by topic. The workflow tells the agent to scaffold a project with npx or install the mcp package with pip, and to run the MCP Inspector through npx, so it uses the shell, downloads packages from the registries and writes server code. The reference examples show tools that read files from an allowed directory, query a database, fetch a URL over HTTP, read git state and watch a folder for changes, and they ask for credentials from environment variables. Anything the agent builds this way can reach those systems, so the skill’s own validation and access rules are worth keeping.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers