ask-starknet-mcp-server

Provides a Zed Editor context server/extension that exposes the ask-starknet MCP server tools inside Zed, letting an AI assistant query Starknet blockchain data and (optionally) deploy/interact with smart contracts using configured RPC and LLM provider keys.

Evaluated Apr 04, 2026 (16d ago)

Repo ↗ Infrastructure zed mcp starknet blockchain rust editor-extension ai-agent-tools

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

README shows direct inclusion of a Starknet private key in Zed configuration, which is risky. LLM API keys are also required. The extension’s transport security (TLS) and secret redaction/logging behavior are not described, so scores are conservative. No mention of least-privilege scopes or hardened signing/approval flows.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want to run Starknet tooling from an interactive AI coding environment (Zed) and already have (or are comfortable building) the underlying ask-starknet MCP server.

Avoid When

You need a strict enterprise security posture with auditable key custody and least-privilege signing; this setup appears to accept a raw private key via configuration.

Use Cases

• Ask an AI assistant questions about Starknet (block number, transactions, balances)
• Assist with smart contract deployment and interaction flows from within Zed
• Agentic workflows in Zed that rely on MCP tool calls to Starknet

Not For

• Production custody/signing of large amounts of funds without additional key-management controls
• Environments where you cannot provide or protect private keys and LLM API keys
• Use cases requiring a documented, standalone public API endpoint (this is an editor extension/context server)

Interface

REST API

GraphQL

gRPC

MCP Server

SDK

Webhooks

Authentication

Methods: Anthropic API key OpenAI API key Google Gemini API key

OAuth: No Scopes: No

The README indicates API keys are configured in Zed settings. It also optionally accepts a Starknet private key for transactions, which is a high-risk secret-handling scenario.

Pricing

Free tier: No

Requires CC: No

No pricing details provided; costs likely depend on the chosen LLM provider and Starknet RPC usage.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Agent may trigger transaction-creating tools if a Starknet private key is configured; ensure the assistant has appropriate guardrails
⚠ Configuration requires an absolute ask-starknet path; relative paths may break startup
⚠ Missing/incorrect LLM API key will prevent tool access depending on provider selection
⚠ The setup relies on building ask-starknet locally, which may introduce environment/setup drift

Alternatives

Use ask-starknet directly (as an MCP server) outside Zed Build/host your own Starknet integration using Starknet RPC APIs and an LLM tool-calling layer Use another editor extension or MCP context server that wraps Starknet tooling

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for ask-starknet-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.