Mcp reference servers

Skill tuliosousapro/SaaS-blueprint/skills/mcp-reference-servers

Guidance on using and integrating official reference servers. Use when building custom servers or deploying standard configurations. For server listings, see mcp-server-registry.From its SKILL.md

Install

npx -y skills add tuliosousapro/SaaS-blueprint --skill mcp-reference-servers

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 325 tokens by cl100k_base, as published. Nobody here has run it

MCP Reference Servers Skill

When to Use

When building new MCP servers and needing a reference implementation.
When the user wants robust, community-tested servers for common tools (Filesystem, Google Search, Fetch, etc.).
When debugging MCP connection issues using standardized servers.

Reference

MCP Reference Servers GitHub

Instructions

1. Identify Target Server

Review the src directory in the reference repository to see available servers.
Common servers include:
fetch: For web page scraping.
filesystem: For local file access.
google-search: For web searching capabilities.
postgres: For database interaction.

2. Implementation & Setup

Most reference servers are built with Node.js/TypeScript or Python.
Follow the README.md within each sub-directory for build and run instructions.
Ensure the appropriate runtime (Node.js 18+ or Python 3.10+) is installed.

3. Usage via MCP Configuration

{
  "mcpServers": {
    "server-name": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-name"],
      "env": {
        "ENV_VAR": "value"
      }
    }
  }
}

Quality Gates

Use npx for quick access without local installation unless performance is a concern.
Keep environment variables secure in protected configuration files.
Verify the server's capabilities via list_tools command after initialization.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most mcp tooling skills give in 325 tokens

Counted across 780 of the 1,136 authors here whose files we hold, read 2026-09-06

Use Zod for input validationin 34 of 780, across 21 files
Use stdio for local clientsin 27 of 780, across 10 files
Restart Claude Code after configurationin 26 of 780, across 23 files
Verify MCP server connection before using toolsin 23 of 780, across 17 files
Define input schemas for every toolin 20 of 780, across 11 files
Use Streamable HTTP for remote clientsin 18 of 780, across 8 files
Pin SDK version in package.jsonin 17 of 780, across 6 files
Keep server logic independent of transportin 16 of 780, across 6 files
Verify SDK methods against official documentationin 15 of 780, across 5 files
Format evaluation results as an XML filein 15 of 780, across 12 files
Test servers using the MCP Inspectorin 15 of 780, across 14 files
Create ten complex and independent evaluation questionsin 14 of 780, across 11 files

Said here and by no other author read

Review the source directory for available servers
Follow the readme for build and run instructions
Ensure required runtime versions are installed
Use npx for quick access
Keep environment variables in protected files
Verify server capabilities via list_tools

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.