Starknet MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Starknet MCP Server?

Starknet MCP Server is a comprehensive Model Context Protocol (MCP) server designed for the Starknet blockchain, enabling AI agents to interact with Starknet networks, query blockchain data, manage wallets, and interact with smart contracts.

How to use Starknet MCP Server?

To use the Starknet MCP Server, you can run it directly using npx or install it globally. It can operate in two modes: stdio mode for CLI tools and HTTP mode for web applications.

Key features of Starknet MCP Server?

  • Full integration with Starknet blockchain using Starknet.js
  • Supports both Mainnet and Sepolia testnet
  • Resolution of Starknet IDs to addresses and vice versa
  • Native token support for ETH and STRK
  • Smart contract interaction capabilities
  • Designed for use with AI assistants like Claude and GPT

Use cases of Starknet MCP Server?

  1. Querying blockchain state such as balances and transactions.
  2. Interacting with smart contracts on the Starknet blockchain.
  3. Managing token transfers and NFT operations.
  4. Resolving Starknet IDs for user-friendly address management.

FAQ from Starknet MCP Server?

  • What networks does the server support?

    The server supports Starknet Mainnet and Sepolia testnet.

  • Is there a way to run the server without installation?

    Yes, you can use npx to run the server directly without installation.

  • Can I use this server with AI assistants?

    Yes, it is designed to be compatible with AI assistants like Claude and GPT.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT 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)

a day ago