MCP_server

motiondesignlv/MCP_server

3.1

If you are the rightful owner of MCP_server and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

This is a local development server designed for managing and accessing markdown documents using the Model Context Protocol (MCP).

MCP Server for Document Management

A local development server that provides a simple interface for managing and accessing markdown documents using the Model Context Protocol (MCP).

Features

  • Serve markdown documents from a local directory
  • List available documents
  • Read document contents
  • Simple and fast local development setup
  • Support for both direct MCP and SSE communication

Project Structure

.
ā”œā”€ā”€ documents/         # Directory containing markdown files
ā”œā”€ā”€ tools/             # Tool definitions
ā”œā”€ā”€ resources/         # Resource templates
ā”œā”€ā”€ utils/             # Utility functions
└── server.js          # Main server file

Setup

  1. Install dependencies:
npm install
  1. Create a documents directory in the project root and add your markdown files:
mkdir documents
  1. Start the server:
npm start
  1. In a separate terminal, run the inspector:
npm run inspect

Usage

The server provides the following functionality:

  1. List Documents:

    • Access available markdown files through the inspector
    • Files are listed with their names (without .md extension)
  2. Read Documents:

    • Click on any document in the inspector to view its contents
    • Documents are served with proper markdown formatting
  3. File Management:

    • Add new markdown files to the documents directory
    • Files are automatically detected and made available
    • Only .md files are supported

Development

The server uses:

  • Express.js for the web server
  • Model Context Protocol (MCP) for communication
  • SSE (Server-Sent Events) for real-time updates
  • Direct MCP communication for simple requests

Error Handling

The server includes:

  • Automatic port conflict resolution
  • Graceful error handling for file operations
  • Connection management for SSE
  • Proper cleanup of resources

Notes

  • This is a local development server, not intended for production use
  • No security measures are implemented as it's meant for local use only
  • File operations are optimized for quick access and response

lv.