Maestro MCP Server

Created By
maestro-orga year ago
Maestro MCP Server for Bitcoin
Overview

What is Maestro MCP Server?

Maestro MCP Server is a Model Context Protocol (MCP) server designed for interacting with Bitcoin through the Maestro API platform. It provides tools for exploring various aspects of the Bitcoin blockchain, including blocks, transactions, and addresses.

How to use Maestro MCP Server?

To use the Maestro MCP Server, you need to install the required dependencies, set up a virtual environment, and configure the Claude Desktop application to connect to the server. After setup, you can launch Claude and use it to prompt for various Bitcoin-related queries.

Key features of Maestro MCP Server?

  • Interaction with Bitcoin blockchain via Maestro API
  • Support for various endpoints to fetch blockchain data
  • Integration with Claude Desktop for user-friendly interaction

Use cases of Maestro MCP Server?

  1. Fetching the latest Bitcoin block information.
  2. Retrieving transaction details from the Bitcoin blockchain.
  3. Exploring addresses and their associated UTXOs.

FAQ from Maestro MCP Server?

  • What are the system requirements for Maestro MCP Server?

Python >=3.10 and Python MCP SDK >= 1.2.0 are required.

  • How do I configure the server?

You need to edit the Claude Desktop configuration file with the absolute paths and Maestro API key.

  • Where can I find the API specifications?

All Maestro API specifications can be found in the Postman workspace.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
maestro-org
Star
0
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
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)

2 days ago