Skip to content
TrustedSkillsbeta
Back to all skills

Mcp Builder

Checked
project-n-e-k-o·vlatest·agents·Apache-2.0

Provides MCP tools guidance and assistance for orchestrating AI agents and multi-step workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add project-n-e-k-o/n.e.k.o --skill mcp-builder -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

project-n-e-k-o

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned project-n-e-k-o/n.e.k.o at 4e45b30d1c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
4e45b30d1c
Manifest
.agent/skills/mcp-builder/SKILL.md
Scanned
9 files, 3,176 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, Mcp Builder, provides guidance and assistance for developing Model Context Protocol (MCP) servers. MCP servers enable Large Language Models (LLMs) to interact with external services through tools. The skill focuses on helping developers create high-quality MCP servers that allow LLMs to accomplish real-world tasks by providing information on design principles, protocol documentation, and framework best practices.

When to use it

  • When designing a new MCP server for an LLM application.
  • To understand the trade-offs between comprehensive API coverage versus specialized workflow tools within an MCP server.
  • For guidance on naming conventions and structuring tool descriptions for improved agent discoverability.

Key capabilities

  • Provides information on modern MCP design principles, including balancing API coverage with workflow tools.
  • Offers guidance on tool naming and discoverability using consistent prefixes and action-oriented names.
  • Explains the importance of actionable error messages to guide agents toward solutions.
  • Directs users to relevant MCP protocol documentation (specification overview, transport mechanisms, definitions).
  • Recommends a development stack including TypeScript and Streamable HTTP for transport.
  • Provides links to best practices guidelines and SDK documentation for both TypeScript and Python.

Example prompts

  • "What are the key considerations when designing tool names for an MCP server?"
  • "Where can I find the official Model Context Protocol specification documentation?"
  • "What is the recommended development stack for creating a new MCP server?"

Tips & gotchas

  • Prioritize comprehensive API coverage over specialized workflow tools unless performance testing indicates otherwise.
  • Refer to the sitemap (https://modelcontextprotocol.io/sitemap.xml) to navigate the MCP specification documentation effectively.
  • TypeScript is recommended for development due to strong SDK support and compatibility.