mcp

This MCP server provides access to resources and prompts stored in a GitHub repository (or a local filesystem for testing). It reads an index.json that declares available resources and prompts, then serves the corresponding markdown content to Claude and other MCP-compatible tools. With the default setup, you point Claude at a repository, and the server exposes the defined resources and prompts via the MCP interface so that you can browse, list, and prompt the model with structured guidance. The examples show how to run the server via npx and how to reference the repository, user, and repository path so Claude can fetch the correct assets. You can also run the server against a local filesystem to test changes before pushing to GitHub, using the filesystem path option described in the quick start and usage sections.

Prerequisites:

• Node.js and npm installed on your machine (npx is included with npm).
• A GitHub repository (or local directory) following the required structure.

1. Verify Node.js and npm are installed:

   node -v npm -v

2. Prepare your repository:

   • Create a repo with the following structure: your-repo/ ├── index.json ├── resources/ │ └── your-resource.md └── prompts/ └── your-prompt.md

   • Create index.json that defines resources and prompts, for example: { "resources": [{"name": "your-resource", "description": "Description of your resource"}], "prompts": [{"name": "your-prompt", "description": "Description of your prompt"}] }

3. Run the MCP server via npx (GitHub-hosted):

   npx --yes github:cressie176/mcp-server --repository-type github --user your-username --repository your-repo

   If you want to test with a local filesystem instead of GitHub:

   npx --yes github:cressie176/mcp-server --repository-type filesystem --path /path/to/your/data

4. Optional: add the command to your Claude configuration or your automation script to restore the server easily.

5. Validate that Claude can access the resources with the /mcp command or the equivalent API endpoints provided by MCP.

Tips and common issues:

• Ensure index.json is valid JSON and correctly references the resource and prompt files in resources/ and prompts/.
• When using GitHub, provide correct values for --user and --repository; ensure the repository contains index.json and the expected directory structure.
• If you change repository paths or filenames, update index.json accordingly.
• For local filesystem testing, make sure the path points to a directory containing index.json, resources/, and prompts/ with the same structure.
• Log level and log file options are exposed by the underlying MCP server; use --log-level to adjust verbosity and --log-file to persist logs if needed.
• If you encounter MIME or encoding issues with Markdown, ensure resource/prompts are valid Markdown (.md) files.
• The server can be restarted after changes to the repository to refresh the available resources and prompts in Claude.