Agent skill

MCP Tool Developer

by sickn33 in sickn33/agentic-awesome-skills

Build Model Context Protocol (MCP) servers and tools from scratch.

Install MCP Tool Developer

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill mcp-tool-developer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills mcp-tool-developer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/mcp-tool-developer .claude/skills/mcp-tool-developer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "mcp-tool-developer" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/mcp-tool-developer into .claude/skills/mcp-tool-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-tool-developer", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/mcp-tool-developer

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill mcp-tool-developer -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills mcp-tool-developer --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/mcp-tool-developer .agents/skills/mcp-tool-developer && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "mcp-tool-developer" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/mcp-tool-developer into .agents/skills/mcp-tool-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-tool-developer", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill mcp-tool-developer -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills mcp-tool-developer --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/mcp-tool-developer .cursor/skills/mcp-tool-developer && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "mcp-tool-developer" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/mcp-tool-developer into .cursor/skills/mcp-tool-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-tool-developer", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/sickn33/agentic-awesome-skills.git --path skills/mcp-tool-developer

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill mcp-tool-developer -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills mcp-tool-developer --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/mcp-tool-developer .gemini/skills/mcp-tool-developer && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "mcp-tool-developer" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/mcp-tool-developer into .gemini/skills/mcp-tool-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-tool-developer", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills mcp-tool-developer

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill mcp-tool-developer -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/mcp-tool-developer .github/skills/mcp-tool-developer && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "mcp-tool-developer" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/mcp-tool-developer into .github/skills/mcp-tool-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-tool-developer", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill mcp-tool-developer -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills mcp-tool-developer --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/mcp-tool-developer .opencode/skills/mcp-tool-developer && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "mcp-tool-developer" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/mcp-tool-developer into .opencode/skills/mcp-tool-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-tool-developer", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: mcp-tool-developer
GitHub stars: 47k
Used in: 1 other repo
Token cost: ~1.2k tokens
SKILL.md length: 505 words
Files: 1
Skills in repo: 1,394
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Build Model Context Protocol (MCP) servers and tools from scratch.

Works in 4 steps: Define the MCP Server Scope → Design the Tool Schema → Implement the Server → …
Tasks that involve MCP servers
SKILL.md covers Overview, When to Use This Skill, How It Works and Examples, plus 5 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

MCP Tool Developer is an agent skill from sickn33/agentic-awesome-skills. Build Model Context Protocol (MCP) servers and tools from scratch. Full-stack MCP development with TypeScript/Python, testing, deployment, and registry publishing.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol, TypeScript and Python. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

Tasks that involve MCP servers

Example prompts

“/mcp-tool-developer”

Requirements

Python 3

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Define the MCP Server Scope
Design the Tool Schema
Implement the Server
Test and Deploy

What it can do on your machine

Read from SKILL.md and the folder at commit 1e53ce2. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

MCP Tool Developer loads about 1.2k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 505 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~46
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit 1e53ce2, republished under its MIT licence (© sickn33). 505 words, ~1,217 tokens.

Download SKILL.mdSave it as .claude/skills/mcp-tool-developer/SKILL.md (or your agent's skills folder).

name: mcp-tool-developer
description: Build Model Context Protocol (MCP) servers and tools from scratch. Full-stack MCP development with TypeScript/Python, testing, deployment, and registry publishing.
category: developer-tools
risk: safe
source: community
source_repo: demo112/yunqu-ai-skills
source_type: community
date_added: 2026-05-13
author: yundu-ai
tags: mcp, ai-agent, tool-development, typescript, python, llm, model-context-protocol
tools: claude, cursor, gemini

MCP Tool Developer

Overview

Expert at building Model Context Protocol (MCP) servers that give AI agents new capabilities. Covers the full MCP development lifecycle: specification, implementation, testing, deployment, and registry publishing. Supports both TypeScript and Python with production-ready patterns.

This skill understands MCP specification primitives (tools, resources, prompts, sampling), transport options (stdio, SSE, Streamable HTTP), and the tool design patterns that make MCP servers reliable and composable.

When to Use This Skill

Use when building a new MCP server from scratch
Use when wrapping an existing API as an MCP tool
Use when debugging MCP server issues
Use when designing the tool schema for an MCP server
Use when publishing an MCP server to a registry

How It Works

Step 1: Define the MCP Server Scope

Identify what capabilities the server should expose:

Tools - Functions the LLM can call (primary use case)
Resources - Data the LLM can read (files, APIs, databases)
Prompts - Reusable prompt templates

Choose the transport:

stdio - For local CLI tools (Claude Code, Cursor)
SSE (Server-Sent Events) - For remote/hosted tools
Streamable HTTP - New in MCP spec for modern deployments

Step 2: Design the Tool Schema

Define input/output schemas before writing implementation:

typescript

{
  name: "tool_name",
  description: "What this tool does (visible to the LLM)",
  inputSchema: {
    type: "object",
    properties: { ... },
    required: [ ... ]
  }
}

Step 3: Implement the Server

Create the server with proper error handling, validation, and logging. Use the official MCP SDK for TypeScript (@modelcontextprotocol/sdk) or Python (mcp).

Step 4: Test and Deploy

Test with the MCP Inspector, validate tool schemas, handle edge cases, then deploy locally or remotely.

Examples

Example 1: TypeScript MCP Server

typescript

import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";

const server = new McpServer({ name: "my-tools", version: "1.0.0" });

server.tool("greet", "Greet someone by name",
  { name: z.string().describe("Person's name") },
  async ({ name }) => ({ content: [{ type: "text", text: `Hello, ${name}!` }] })
);

const transport = new StdioServerTransport();
await server.connect(transport);

Example 2: API Wrapper Pattern

Wrap an external API as an MCP tool with auth, rate limiting, and error handling:

Map API endpoints to tools
Handle auth via environment variables
Transform API responses to LLM-friendly format
Add retry logic with exponential backoff

Show full SKILL.md (217 more words)Show less

Best Practices

Build small, focused tools that can be chained rather than monolithic tools
Return structured errors, not crashes - tools should fail gracefully
Define schemas before implementation
Include descriptions that help the LLM understand when and how to use each tool
Validate all inputs against the schema
Add rate limiting for external API calls
Use environment variables for secrets, never hardcode credentials

Limitations

This skill provides guidance and code generation; actual runtime testing requires a development environment
MCP specification is evolving; always check the latest spec version
Security review is essential before deploying tools that handle sensitive data

Security and Safety Notes

Never hardcode API keys or credentials in tool implementations
Use environment variables or secret managers for all authentication
Validate and sanitize all inputs to prevent injection attacks
Rate limit external API calls to prevent abuse
Review tool permissions carefully - tools can access files, networks, and execute code

Common Pitfalls

Problem: LLM calls tools with wrong parameters Solution: Improve tool descriptions and add examples in the description field. The LLM reads descriptions to decide how to call tools.
Problem: Tool times out on large inputs Solution: Add input size validation and pagination. Stream large responses instead of buffering.

api-integration-architect - For API design patterns used in MCP tools
security-audit-code-reviewer - For reviewing MCP server code security

Files

Just SKILL.md in skills/mcp-tool-developer of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit 1e53ce2

Used in 1 other repository

We found 7 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

lingxling/awesome-skills-cnantigravity-awesome-skills/skills/mcp-tool-developer antigravity-awesome-skills/plugins/agentic-awesome-skills/skills/mcp-tool-developer+2 more

Compare with similar skills

MCP Tool Developer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

MCP Tool Developer compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
MCP Tool Developer this skillsickn33/agentic-awesome-skills	47k	1 repos	~1.2k	Automated safety check: Pass	MIT	yesterday
MCP Server Builderanthropics/skills	180k	62 repos	~2.3k	Automated safety check: Pass	Apache-2.0	2 days ago
MCP Server BuildershareAI-lab/learn-claude-code	78k	5 repos	~1.2k	Automated safety check: Pass	MIT	9 days ago
Create MCP Serversglittercowboy/taches-cc-resources	2k	—	~1.5k	Automated safety check: Pass	MIT	6 mo ago
MCP BuilderLeastBit/Claude_skills_zh-CN	588	—	~1.2k	Automated safety check: Pass	Apache-2.0	8 mo ago
Build MCP Serverbobmatnyc/claude-mpm	155	—	~2k	Automated safety check: Pass	Apache-2.0	1 mo ago

Similar skills

MCP Server Builder
anthropics/skills
Official
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
180k GitHub starsUsed in 62 repos~2.3k tokens
Agent WorkflowsAuto-check passed
MCP Server Builder
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
78k GitHub starsUsed in 5 repos~1.2k tokens
Agent WorkflowsAuto-check passed
Create MCP Servers
glittercowboy/taches-cc-resources
Create Model Context Protocol (MCP) servers that expose tools, resources, and prompts to Claude.
2k GitHub stars~1.5k tokensUpdated 6 mo ago
Agent WorkflowsAuto-check passed
MCP Builder
LeastBit/Claude_skills_zh-CN
构建高质量 MCP（模型上下文协议）服务器的指南，使 LLM 能够通过精心设计的工具与外部服务交互。在使用 Python (FastMCP) 或 Node/TypeScript (MCP SDK) 构建 MCP 服务器以集成外部 API 或服务时使用。
588 GitHub stars~1.2k tokensUpdated 8 mo ago
Agent WorkflowsAuto-check passed
Build MCP Server
bobmatnyc/claude-mpm
Create high-quality MCP servers that enable LLMs to effectively interact with external services.
155 GitHub stars~2k tokensUpdated 1 mo ago
Agent WorkflowsAuto-check passed
MCP Server Builder
shareAI-lab/Kode-CLI
Guide to designing and building MCP servers: tool, resource and prompt design for agent usability, with TypeScript or Python implementation workflows.
5.2k GitHub stars~1.9k tokensUpdated 1 mo ago
Agent WorkflowsAuto-check passed

Questions about MCP Tool Developer

What does MCP Tool Developer do?

Build Model Context Protocol (MCP) servers and tools from scratch. MCP Tool Developer is an agent skill from sickn33/agentic-awesome-skills. Build Model Context Protocol (MCP) servers and tools from scratch.

When should I use MCP Tool Developer?

MCP Tool Developer fits situations like: tasks that involve MCP servers.

How do I install MCP Tool Developer in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill mcp-tool-developer -a claude-code`. Or copy the skill folder (skills/mcp-tool-developer in sickn33/agentic-awesome-skills) into .claude/skills/mcp-tool-developer in your project. Claude Code loads it when a task matches its description.

How do I install MCP Tool Developer in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill mcp-tool-developer -a codex`. Or copy the skill folder (skills/mcp-tool-developer in sickn33/agentic-awesome-skills) into .agents/skills/mcp-tool-developer in your project. Codex loads it when a task matches its description.

Can I use MCP Tool Developer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill mcp-tool-developer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcp-tool-developer, .gemini/skills/mcp-tool-developer, .github/skills/mcp-tool-developer and .opencode/skills/mcp-tool-developer in your project.

What does MCP Tool Developer need to run?

SKILL.md names no scripts, command-line tools or credentials: MCP Tool Developer is instructions for the agent only. Our summary lists: Python 3.

Does MCP Tool Developer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is MCP Tool Developer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does MCP Tool Developer use?

MCP Tool Developer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does MCP Tool Developer use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to MCP Tool Developer?

Skills that share tags, products or a category with MCP Tool Developer: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), Create MCP Servers (glittercowboy/taches-cc-resources, 2k stars) and MCP Builder (LeastBit/Claude_skills_zh-CN, 588 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains MCP Tool Developer?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install MCP Tool Developer

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

MCP Tool Developer

Overview

When to Use This Skill

How It Works

Step 1: Define the MCP Server Scope

Step 2: Design the Tool Schema

Step 3: Implement the Server

Step 4: Test and Deploy

Examples

Example 1: TypeScript MCP Server

Example 2: API Wrapper Pattern

Best Practices

Limitations

Security and Safety Notes

Common Pitfalls

Related Skills

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from sickn33/agentic-awesome-skills

Related

Questions about MCP Tool Developer