Symbol MCP Server (REST API tools)

Created By
husqvalunaa year ago
Symbol MCP Server. (REST API tools)
Overview

what is Symbol MCP Server?

Symbol MCP Server is a server that enables the use of the Symbol blockchain's REST API as Model Context Protocol (MCP) tools.

how to use Symbol MCP Server?

To use Symbol MCP Server, run the following command in your terminal:

{
  "mcpServers": {
    "symbol": {
      "command": "npx",
      "args": [
        "-y",
        "tsx",
        "/path/to/your/mcp/symbol-mcp-server/src/index.ts"
      ]
    }
  }
}

key features of Symbol MCP Server?

  • Provides access to Symbol blockchain's REST API.
  • Supports Model Context Protocol (MCP) tools for enhanced functionality.
  • Easy integration with existing applications using REST API.

use cases of Symbol MCP Server?

  1. Integrating Symbol blockchain functionalities into applications.
  2. Developing decentralized applications (dApps) using Symbol's blockchain.
  3. Accessing blockchain data for analytics and reporting.

FAQ from Symbol MCP Server?

  • What is the purpose of Symbol MCP Server?

It allows developers to interact with the Symbol blockchain using REST API, facilitating the development of blockchain applications.

  • Is Symbol MCP Server free to use?

Yes! Symbol MCP Server is open-source and free to use.

  • What programming language is used in Symbol MCP Server?

The server is developed using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
husqvaluna
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago