Mst Mcp

io.github.vipulsutar11Published by GitHub account vipulsutar11v1.0.0Updated Oct 24, 2026

MCP server for the MST Chain ecosystem providing search and retrieval tools for documentation.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Lets an assistant list, read, and keyword-search MST Chain developer documentation files through read-only lookup tools.

What you can do
This server exposes three read-only tools for the MST Chain ecosystem: list_documents lists the available developer documentation files, read_document returns the contents of a named file such as SDK.txt, and search_documents finds a keyword or query across all files and returns matching lines with line numbers. It is intended for looking up API, wallet, transaction, and authentication documentation.
When to use it
Worth adding when an assistant needs to answer questions about MST Chain development and should ground answers in the project's own documentation rather than general knowledge. Useful for looking up wallet integration, transaction structure, or API details during coding work.
Requirements
Runs as a local process over stdio. The README describes a remote SSE endpoint plus a Python bridge script (sse_bridge.py) that developers clone and run, requiring Python and the aiohttp package; the manifest instead lists an OCI image, docker.io/vipulsutar/mst-mcp:1.0.0. No environment variables, headers, or authentication are declared. Network access is needed to reach the hosted endpoint.
Before you install
The README states the bridge script automatically handles a bypass token, so credentials may be embedded in or handled by that script; review it before running. The tools are described as read-only lookups, but documentation content is fetched from a third-party hosted endpoint, so queries and retrieved text pass through that service. The manifest declares no authentication, so anyone reaching the endpoint may be able to read the same documentation.

Installation

In SourceWeft

  1. Open Mst Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

MST-MCP Server

An official Model Context Protocol (MCP) server for the MST Chain ecosystem. This server provides tools for LLMs (like Claude) to search, list, and retrieve MST developer documentation (APIs, wallets, transactions, authentication, etc.).

🚀 Deployed Endpoint

  • Base URL (SSE Transport): https://mst-mcp-xjb5.onrender.com/sse
  • Favicon / Branding: https://mst-mcp-xjb5.onrender.com/favicon.png

💻 How Developers Can Connect (Claude Desktop, Cursor, Antigravity IDE)

Because IDEs require a standard STDIO connection but the server is hosted remotely, developers must use the provided sse_bridge.py script to tunnel the connection.

  1. Developers clone this repository:
    bash
    git clone https://github.com/vipulsutar11/mst-mcp.gitcd mst-mcppip install aiohttp
  2. They configure their IDE (e.g. mcp_config.json or claude_desktop_config.json) to use the bridge script:
    json
    {  "mcpServers": {    "mst-mcp": {      "command": "python",      "args": ["/path/to/cloned/mst-mcp/sse_bridge.py"]    }  }}
    Note: This script automatically handles the Bypass Token and SSE connections.

🛠 Exposed Tools

All tools are read-only lookup tools with custom annotations:

  1. list_documents

    • Description: Lists all available developer documentation files in the server.
    • Annotations: readOnlyHint: true, title: "List Documents"

  2. read_document

    • Description: Reads and returns the contents of a specific documentation file (e.g., SDK.txt).
    • Annotations: readOnlyHint: true, title: "Read Document"

  3. search_documents

    • Description: Searches for a keyword or query across all files and returns matching lines with line numbers.
    • Annotations: readOnlyHint: true, title: "Search Documents"

💡 Example Prompts to Try in Claude

After connecting this server as a connector, you can ask Claude:

  • Example 1 (Listing docs):

    "Check my mcp is in working and list all documentation files."

  • Example 2 (Searching keywords):

    "Search the developer docs for wallet integration details."

  • Example 3 (Retrieving document content):

    "Read the documentation on transaction structure."

🏗 Setup & Deployment

Local Development

To run the server locally:

  1. Initialize virtual environment and install dependencies:
    bash
    pip install -r requirements.txt
  2. Start the server:
    bash
    python server.py

Deploying on AWS EC2

We have provided a dedicated deployment guide for AWS EC2. Please refer to the DEPLOYMENT.md file for comprehensive, step-by-step instructions on setting up your EC2 instance natively or via Docker.

Source: README.md at commit a840c1a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.