Starknet MCP Server

The Starknet MCP Server bridges the gap between AI assistants and the Starknet blockchain by exposing a rich set of tools, resources, prompts, and sampling mechanisms through the Model Context Protocol. It solves a common pain point for developers: enabling natural‑language powered agents to read, write, and transact on Starknet without having to embed complex SDK logic directly into the assistant’s code. By handling address resolution, transaction signing, and network communication behind the scenes, the server lets AI agents focus on higher‑level reasoning while still performing precise blockchain operations.

At its core, the server offers a unified interface for state queries, token management, NFT interactions, and smart‑contract execution. Developers can ask an assistant to “check my ETH balance on Sepolia” or “transfer 10 STRK to alice.stark”, and the server will resolve StarknetID names, construct the appropriate calls via Starknet.js, sign transactions with a managed wallet, and return structured results. This abstraction removes boilerplate from the assistant’s prompt logic and ensures consistent error handling, retry policies, and logging.

Key capabilities include:

• Full network support for Mainnet and Sepolia, with automatic chain‑ID detection.
• StarknetID resolution that translates human‑readable domain names into on‑chain addresses and vice versa.
• Native token operations for ETH and STRK, including balance queries and transfers.
• ERC‑20 and NFT tooling that fetches metadata, checks ownership, and performs transfers.
• Smart‑contract interaction with read‑only calls, write transactions, and storage inspection.
• Dual transport modes (stdio or HTTP) to fit diverse deployment environments.

Real‑world scenarios range from building a voice‑controlled wallet assistant that can read balances and send payments, to creating an automated compliance bot that audits NFT ownership across collections. In all cases, the MCP server encapsulates low‑level Starknet intricacies, allowing AI workflows to remain declarative and maintainable.

What sets this server apart is its AI‑ready design: every tool accepts both raw addresses and StarknetID names, ensuring that prompts remain natural. The consistent MCP schema also means that new features—such as additional token standards or cross‑chain bridges—can be added with minimal impact on existing agents. For developers, this translates into faster prototyping, fewer integration bugs, and a smoother developer experience when building AI assistants that interact with Starknet.