Discorevy local MCP Servers. Specification.
MCP Servers discovery spec
jonnyzzz
README
Discorevy local MCP Servers. Specification.
Version: 1.0.1
Goals
This specification aims to allow the standard way to list and configure MCP Servers on a local machine.
Many tools already use MCP Servers to augment the LLMs. Currently, there is no standard approach to quickly registering an MCP Server.
Here are the most popular MCP Clients:
- IntelliJ IDEA
- Anthropic Claude
- OpenAI ChatGPT
- Cursor
- Windsurf
- Warp
- PR to add you
Supported in the following tools
- PR if you support the spec
Specification
Create a file per each MCP server in the ~/.mcp
folder (%USER_HOME%
on Windows).
The file is a Markdown file that explains an LLM (such as Claude or CharGPT) about your MCP Server details. The client uses LLM to transform your explanation into an actionable MCP Server.
The client is required to regularly refresh the information from the disc to discover new MCP Servers.
This protocol does not resolve any security implications for MCP servers. That is still the responsibility of MCP Clients.
For example:
~/.mcp/my-mcp-server-tool-id.md
Create the following text inside:
---
version: 1.0.1
---
# MCP Server: Production
Here, I describe what my MCP Server is doing and why the LLM would decide to include my server in a specific request, which is queried.
## Basic Information
- **Name**: Production Jonnyzzz MCP Server
- **ID**: prod-mcp-01
- **Version**: 3.2.1
- **URL**: https://mcp-prod.jonnyzzz.com:8443
- **API Version**: v2
## Authentication
- **Type**: oauth2
- **Client ID**: client_123
- **Token Endpoint**: https://auth.example.com/token
## Capabilities
- compute
- storage
- networking
## Regions
### us-east
- us-east-1a
- us-east-1b
### eu-west
- eu-west-1a
- eu-west-1b
## Health Check
- **Endpoint**: /health
- **Interval**: 60 seconds
## Metadata
- **Environment**: production
- **Owner**: platform-team
- **Priority**: high
How to use the Spec?
An MCP client uses the LLM (e.g., Claude, ChatGPT) to extract the necessary information from each of the available MCP server's markdown files, which are discovered in the files under the ~/.mcp
folder.
It is up to the LLM and the client to decide if to use a specific LLM, ask for credentials, and so on.
The client should refresh the files from the disk regularly.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
MCP Package Docs Server
Facilitates LLMs to efficiently access and fetch structured documentation for packages in Go, Python, and NPM, enhancing software development with multi-language support and performance optimization.
Claude Code MCP
An implementation of Claude Code as a Model Context Protocol server that enables using Claude's software engineering capabilities (code generation, editing, reviewing, and file operations) through the standardized MCP interface.
@kazuph/mcp-taskmanager
Model Context Protocol server for Task Management. This allows Claude Desktop (or any MCP client) to manage and execute tasks in a queue-based system.
Linear MCP Server
Enables interaction with Linear's API for managing issues, teams, and projects programmatically through the Model Context Protocol.
mermaid-mcp-server
A Model Context Protocol (MCP) server that converts Mermaid diagrams to PNG images.
Jira-Context-MCP
MCP server to provide Jira Tickets information to AI coding agents like Cursor

Linear MCP Server
A Model Context Protocol server that integrates with Linear's issue tracking system, allowing LLMs to create, update, search, and comment on Linear issues through natural language interactions.

Sequential Thinking MCP Server
This server facilitates structured problem-solving by breaking down complex issues into sequential steps, supporting revisions, and enabling multiple solution paths through full MCP integration.