Back to catalog
Human reviewedDevelopment

Skill dossier

mcp-developer

Source declaration

Use when building, debugging, or extending MCP servers or clients that connect AI systems with external tools and data sources. Invoke to implement tool handlers, configure resource providers, set up stdio/HTTP/SSE transport layers, validate schemas with Zod or Pydantic, debug protocol compliance issues, or scaffold complete MCP server/client projects using TypeScript or Python SDKs.

The author's original description, preserved in English. It describes intent, not verified performance.

Use when building, debugging, or extending MCP servers or clients that connect AI systems with external tools and data sources. Invoke to implement tool handlers, configure resource providers, set up stdio/HTTP/SSE transport layers, validate schemas with Zod or Pydantic, debug protocol compliance issues, or scaffold complete MCP server/client projects using TypeScript or Python SDKs.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

A Skill for building and debugging Model Context Protocol servers and clients in TypeScript or Python, with schema validation and MCP Inspector testing.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Scaffolds MCP server projects with the TypeScript or Python SDK.
  • Defines tool schemas with Zod or Pydantic and registers resources.
  • Configures stdio, SSE or HTTP transport.
  • Tests protocol compliance with the MCP Inspector and iterates on failures.

Limitations & scope

  • SDK APIs change over time; the examples are not verified against current SDK versions.
  • Auth and rate limiting are required but no implementation is given.
  • Protocol, SDK and tool details sit in separate reference files.

Relevant for

  • Developers connecting AI tools to internal data
  • Teams building MCP servers
  • Engineers debugging protocol issues

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
50.2 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/mcp-developer/references/protocol.mdReference4.9 KB
skills/mcp-developer/references/python-sdk.mdReference9.6 KB
skills/mcp-developer/references/resources.mdReference11.9 KB
skills/mcp-developer/references/tools.mdReference10.2 KB
skills/mcp-developer/references/typescript-sdk.mdReference7.8 KB
skills/mcp-developer/SKILL.mdInstruction5.8 KB

SKILL.md frontmatter

{
  "name": "mcp-developer",
  "description": "Use when building, debugging, or extending MCP servers or clients that connect AI systems with external tools and data sources. Invoke to implement tool handlers, configure resource providers, set up stdio/HTTP/SSE transport layers, validate schemas with Zod or Pydantic, debug protocol compliance issues, or scaffold complete MCP server/client projects using TypeScript or Python SDKs.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "api-architecture",
    "triggers": "MCP, Model Context Protocol, MCP server, MCP client, Claude integration, AI tools, context protocol, JSON-RPC",
    "role": "specialist",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": "fastapi-expert, typescript-pro, security-reviewer, devops-engineer"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Analyze requirements

    Identify data sources, tools needed and client applications.

  2. 02
    Action

    Design and implement

    Define resource URIs and tool schemas, register handlers and configure transport.

  3. 03
    Decision

    Test with the Inspector

    On schema or response failures, inspect errors, fix the definition or handler, and re-run.

  4. 04
    Output

    Deliver server and config

    Provide the implementation, schema definitions, configuration and design notes.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

75 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Note

File modification is described or implemented

66 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 66 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

9 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 9 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Review the npx and pip packages and any credentials or tool permissions the generated server exposes before running it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/mcp-developer # .claude/skills/mcp-developer
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/mcp-developer/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Ask Claude Code to scaffold a tool with a Zod schema and confirm it proposes running the MCP Inspector to test it.

Prerequisites

  • SDK APIs change over time; the examples are not verified against current SDK versions.
  • Auth and rate limiting are required but no implementation is given.
  • Protocol, SDK and tool details sit in separate reference files.

Example prompts

Representative task

Using the mcp-developer skill, build a TypeScript MCP server over stdio exposing a validated get_weather tool and a config resource, then test it with the MCP Inspector.

Inspect before use

Read the mcp-developer skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/mcp-developer/SKILL.md and its reference files. Explain its workflow, any commands it tells the agent to run, and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Gives a feedback loop for schema and malformed-response failures.
  • Includes minimal working examples in both languages.

Considerations

  • Scaffolding uses npx and pip, which download and run third-party packages.
  • Examples use a placeholder weather fetch rather than a real integration.
Research conclusion

A useful starting point for MCP server work with an explicit test loop.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/mcp-developer
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.