StaticMCP STDIO Bridge

A lightweight stdio bridge server that serves StaticMCP files.

How It Works

The StaticMCP Bridge acts as a translation layer between the MCP protocol and your static JSON files:

1. Manifest: A mcp.json file describes available resources and tools
2. Resources: Static JSON files in the resources/ directory
3. Tools: Pre-computed tool responses in the tools/ directory structure
4. Bridge: This server dynamically routes MCP requests to the appropriate JSON files

Learn more about StaticMCP at https://staticmcp.com.

Installation

Rust Version

cargo install staticmcp_stdio_bridge

Node.js Version

npm install -g staticmcp-bridge

Build from source

git clone https://github.com/StaticMCP/stdio_bridge
cd stdio_bridge

# rust version
cargo build --release

# node.js version
npm run build

Quick Start

1. Generate StaticMCP Content

Use a generator like docusaurus-staticmcp to convert your documentation into StaticMCP format:

npx docusaurus-staticmcp ./my-docusaurus-site --output ./my-staticmcp

2. Directory Structure

my-staticmcp/
  ├── mcp.json                       # Manifest file
  ├── resources/
  │     ├── docs/getting-started.json
  │     └── blog/2024-01-15-welcome.json
  └── tools/
        └── list_docs/
              ├── docs.json
              ├── blog.json
              └── all.json

3. Run the Bridge

Rust Version

staticmcp_stdio_bridge ./my-staticmcp

Or serve from a remote URL:

staticmcp_stdio_bridge https://mysite.com/my-staticmcp

Node.js Version

npx staticmcp-bridge ./my-staticmcp

Or serve from a remote URL:

npx staticmcp-bridge https://mysite.com/my-staticmcp

Usage with MCP Inspector

Test your StaticMCP server using the official MCP Inspector:

npx @modelcontextprotocol/inspector staticmcp_stdio_bridge https://yourdomain.com/your-staticmcp
npx @modelcontextprotocol/inspector npx staticmcp-bridge https://yourdomain.com/your-staticmcp

File Path Conventions

The bridge automatically maps MCP requests to file paths:

Resources

• docs://getting-started → resources/getting-started.json
• blog://2024-01-15-welcome → resources/2024-01-15-welcome.json
• docs://docs/getting-started → resources/docs/getting-started.json
• blog://blog/2024-01-15-welcome → resources/blog/2024-01-15-welcome.json

Tools

• list_docs(type="docs") → tools/list_docs/docs.json
• list_docs(type="blog") → tools/list_docs/blog.json
• list_docs(type="all") → tools/list_docs/all.json

Response Format

Resource Responses

{
  "contents": [
    {
      "uri": "docs://getting-started",
      "mimeType": "text/markdown",
      "text": "# Getting Started\n..."
    }
  ]
}

Tool Responses

{
  "content": [
    {
      "type": "text",
      "text": "Tool response text"
    }
  ]
}

Deployment Options

You can deploy your StaticMCP files to any static hosting service:

• Vercel
• Netlify
• GitHub Pages
• AWS S3
• CloudFlare CDN

Building StaticMCP Content

Use docusaurus-staticmcp or your own scripts to generate the required files.

Advanced Features

• Error Handling: Returns MCP error responses for missing files
• CORS Support: Handles CORS headers when serving over HTTP
• Caching: All responses are highly cacheable