Skip to main content
Glama
MCPJam

MCP Specification Server

by MCPJam
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

MCP Specification Server

npm version npm downloads License: MIT Node.js TypeScript Discord

Overview

We turned the Model Context Protocol documentation into an MCP server so that your LLM can get context on the full MCP specs. Query specific sections like "Tools", "Resources", "Authorization", and 20+ others to get the complete documentation for that section.

Features

📚 Complete MCP Specification Access

  • 364KB of comprehensive MCP documentation indexed and searchable

  • 25+ distinct sections covering every aspect of the protocol

  • Complete section content returned, not just snippets

⚡ Smart Document Processing

  • Intelligent chunking by major headings (# tags)

  • 500-line chunk limits for optimal performance

  • Fast startup indexing (<1 second)

🔧 Developer-Focused Sections

  • Tools - Function calling and tool execution patterns

  • Resources - Data access and resource management

  • Authorization - Security, authentication, and authorization

  • Transports - Communication layers (stdio, HTTP, SSE)

  • Debugging - Troubleshooting and development tools

  • Core components - Protocol architecture fundamentals

  • Connection lifecycle - Initialization and termination

  • And 18+ more specialized sections

🛠️ Built for MCP Development

  • Perfect for developers building MCP servers or clients

  • Reference implementation patterns and best practices

  • Complete protocol specifications at your fingertips

Related MCP server: Swagger/OpenAPI MCP Server

Install with an IDE

Add this server to any MCP-compatible client (Claude Desktop, Cursor, VSCode, Windsurf, etc.):

Claude Desktop Config:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Cursor config:

Chat Settings, Tools / Integrations. Edit mcp.json

{
  "mcpServers": {
    "mcp-spec": {
      "command": "npx",
      "args": ["-y", "@mcpjam/mcp-spec@latest"]
    }
  }
}

How it works

┌─────────────────┐    ┌──────────────────┐    ┌─────────────────┐
│   MCP Client    │◄──►│  MCP Spec Server │◄──►│ Specification   │
│   (Claude,      │    │                  │    │ Document        │
│    Your App)    │    │  - Section Index │    │ (llms-full.md)  │
└─────────────────┘    │  - Content Cache │    └─────────────────┘
                       │  - Search Logic  │
                       └──────────────────┘

  1. Server indexes the complete MCP specification on startup

  2. Document is split into sections by major headings

  3. Query by section name to get the full content for that section

  4. Returns complete documentation for topics like Tools, Resources, Authorization, etc.

Contributing

Want to improve this server? Here's how:

# 1. Clone the repository
git clone https://github.com/your-org/mcp-spec.git
cd mcp-spec

# 2. Install dependencies
npm install

# 3. Build the project
npm run build

# 4. Start development server
npm run dev

Development workflow:

  1. Fork this repository

  2. Create a feature branch: git checkout -b my-feature

  3. Make your changes

  4. Test locally: npm run build && npm run dev

  5. Submit a pull request

  • Community: Join the MCP community discussions

Note: This is an unofficial server created to make the MCP specification more accessible. For official MCP resources and documentation, visit modelcontextprotocol.io.

Available Tools

1 tool
mcpjam_search_mcp_specC

Search the MCP specification document for relevant content

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesSelect a specific section of the MCP specification to retrieve.

TDQS

C2.8/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

There are no annotations, and the description provides no behavioral information such as what the tool returns (e.g., text, citations), side effects, or error scenarios. For a search tool, this is a significant omission; the agent knows it searches but not what the output looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one sentence of eight words, which is concise but perhaps too minimal. It could benefit from a bit more detail without becoming verbose. It is front-loaded but overly sparse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema and annotations, the description should compensate by explaining what the tool returns. It does not. The schema's enum helps, but the description does not clarify that the output is the content of the selected section. The tool feels incomplete for an agent to use confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage with a clear description for the parameter. The tool description adds no additional semantic value beyond what the schema already provides, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it searches the MCP specification document, but does not explicitly indicate that the search is restricted to the predefined sections listed in the enum. The combination of the description and the schema's enum makes the purpose clear, but the description alone could be slightly more precise.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidelines are provided. Since there are no sibling tools, the guidance is not strictly needed, but the description does not mention when to use this tool or any limitations. The agent can infer usage from the context, but the lack of explicit guidance is a slight gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool update
    • First observedmcpjam_search_mcp_spec
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion between tools, so disambiguation is perfect.

Naming Consistency5/5

The single tool name follows a clear pattern (prefix_verb_noun) and is internally consistent.

Tool Count3/5

One tool is borderline thin for a server; while it may be sufficient for a simple search utility, typical specification servers offer more operations.

Completeness2/5

The server only provides search, missing obvious operations like retrieving specific sections or listing contents, making the toolset incomplete for comprehensive specification interaction.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Swagger/OpenAPI MCP Server

    gulbaki
    A
    license
    D
    quality
    D
    maintenance
    A Model Context Protocol server that enables LLMs to explore and interact with API specifications by providing tools for loading, browsing, and getting detailed information about API endpoints.
    4
    16
    14
    ISC

  • @shuji-bonji/pdf-spec-mcp

    shuji-bonji
    A
    license
    A
    quality
    B
    maintenance
    An MCP (Model Context Protocol) server that provides structured access to ISO 32000 (PDF) specification documents. Enables LLMs to navigate, search, and analyze PDF specifications through well-defined tools.
    8
    386
    2
    MIT

  • mcp-advisor

    olaservo
    A
    license
    Not graded
    quality
    F
    maintenance
    Provides comprehensive access to the Model Context Protocol specification through prompts and resources, enabling evaluation of server compliance and detailed explanations of MCP topics.
    24
    25
    MIT

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MCPJam/mcp-spec'

If you have feedback or need assistance with the MCP directory API, please join our Discord server