mcp-developer

mcp-developer is a skill for Claude Code, Codex from msdakot/ai-foundary. It costs 42 tokens per session (1,050 once invoked), scanned A, original, MIT.

A guide for building servers that let AI applications use tools, data, and reusable instructions through the Model Context Protocol, an agreed way for AI clients and servers to communicate. It covers TypeScript and Python implementations, schemas, resources, prompts, and transport setup.

In plain words
What is it for?
Use it to create MCP servers exposing actions such as file reads or database queries, publish data resources, define reusable prompt templates, validate tool parameters, and configure communication.
Why use it?
It helps turn ordinary actions, data sources, and prompt templates into clearly described capabilities that compatible AI clients can invoke or read. It also keeps inputs and outputs defined according to the protocol.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

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/msdakot/ai-foundary/mcp-developer
Any agent
npx skills add msdakot/ai-foundary --skill mcp-developer
Clone the repo
git clone --depth 1 https://github.com/msdakot/ai-foundary

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for mcp-developer

README.md
[![agentmods](https://agentmods.dev/badge/skills/msdakot/ai-foundary/mcp-developer.svg)](https://agentmods.dev/skills/msdakot/ai-foundary/mcp-developer)
Your own site
<a href="https://agentmods.dev/skills/msdakot/ai-foundary/mcp-developer"><img src="https://agentmods.dev/badge/skills/msdakot/ai-foundary/mcp-developer.svg" alt="Measured on agentmods" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,050 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.1 $0.00042 $0.01050
Opus 5 $0.00021 $0.00525
Sonnet 5 $0.00008 $0.00210
Haiku 4.5 $0.00004 $0.00105

Measured 6d ago against content hash 8ced1de62f94, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

mcp-developer 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 6d ago.

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.

agents/devops-agent/mcp-developer/SKILL.md · 144 lines

How it starts

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

MCP Developer Agent

You build MCP servers that expose tools, resources, and prompts to Claude and other MCP-compatible clients. You follow the MCP specification precisely and build for production — not demos.

MCP Primitives

Primitive Purpose
Tool Executable action the model can invoke (read file, call API, query DB)
Resource Data the model can read (file contents, DB records, API responses)
Prompt Reusable prompt template with parameters

Project Setup

TypeScript

npm init -y
npm install @modelcontextprotocol/sdk zod
npm install -D typescript @types/node tsx

Python

pip install mcp

Tool Implementation (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-server",
  version: "1.0.0",
});

server.tool(
  "tool-name",
  "Clear description of what this tool does and when to use it",
  {
    param1: z.string().describe("Description of this parameter"),
    param2: z.number().optional().describe("Optional numeric parameter"),
  },
  async ({ param1, param2 }) => {
    // Validate business rules beyond schema
    if (!param1.trim()) {
      return {
        content: [{ type: "text", text: "Error: param1 cannot be empty" }],
        isError: true,
      };
    }

    try {
      const result = await doWork(param1, param2);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    } catch (err) {
      return {
        content: [{ type: "text", text: `Error: ${err.message}` }],
        isError: true,
      };
    }
  }
);

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

Resource Implementation (TypeScript)

server.resource(
  "resource-name",
  "resource://scheme/{param}",
  async (uri) => {
    const param = extractParam(uri);
    const content = await fetchContent(param);
    return {
      contents: [{
        uri: uri.href,
        mimeType: "text/plain",
        text: content,
      }],
    };
  }
);

Read the full file on GitHub · 144 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. 6d ago First seen · 144 lines · 42 tokens per session scan A 8ced1de62f94

Subscribe to this mod's changes

mcp-developer is a skill published in the GitHub repository msdakot/ai-foundary (5 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 1,050 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-31.

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

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 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

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens