Algorand MCP Implementation

Created By
GoPlausiblea year ago
Algorand Model Context Protocol (Server & Client)
Overview

What is Algorand MCP?

Algorand MCP is a Model Context Protocol implementation designed for seamless interactions with the Algorand blockchain, providing both server and client packages for developers.

How to use Algorand MCP?

To use Algorand MCP, developers can install the server and client packages via NPM or utilize the server on Smithery for integration with AI tools. The server is fully operational, while the client is still in progress.

Key features of Algorand MCP?

  • Complete capabilities for Algorand blockchain interactions.
  • Extensive wallet management system.
  • Comprehensive transaction handling and blockchain state querying.
  • Built-in security features.
  • Support for integration with AI tools like Claude Desktop and Cursor.

Use cases of Algorand MCP?

  1. Integrating Algorand blockchain functionalities into applications.
  2. Managing wallets and signing transactions securely.
  3. Querying blockchain states and handling transactions efficiently.

FAQ from Algorand MCP?

  • Is the client package fully functional?

No, the client package is still a work in progress, but the server package is fully operational.

  • What are the requirements to run Algorand MCP?

Node.js v23.6.1 or later and npm v10.2.4 or later are required.

  • Can I use Algorand MCP with AI development environments?

Yes, Algorand MCP can be integrated with AI tools like Claude Desktop and Cursor.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
GoPlausible
Star
31
Language
TypeScript
License
MIT license

Recommend Servers

View All
Payai X402 Tools

2 hours ago
Payai X402 Tools

2 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago