Algorand▌

by goplausible
Interact with the Algorand blockchain using a robust TypeScript toolkit for accounts, assets, smart contracts, and trans
Provides a robust toolkit for Algorand blockchain interactions, enabling AI agents to create accounts, manage assets, deploy smart contracts, and execute transactions through a TypeScript-based implementation.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / Blockchain developers building on Algorand
- / AI agents managing crypto transactions
- / DeFi applications requiring automated trading
capabilities
- / Create and manage Algorand wallet accounts
- / Deploy and interact with smart contracts
- / Execute payments and asset transfers
- / Build and submit atomic transaction groups
- / Compile and disassemble TEAL code
- / Access Tinyman AMM for swaps and liquidity
what it does
Connects AI agents to the Algorand blockchain for creating accounts, managing assets, deploying smart contracts, and executing transactions. Features secure wallet management with spending controls and daily limits.
about
Algorand is a community-built MCP server published by goplausible that provides AI assistants with tools and capabilities via the Model Context Protocol. Interact with the Algorand blockchain using a robust TypeScript toolkit for accounts, assets, smart contracts, and trans It is categorized under finance, developer tools.
how to install
You can install Algorand in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Algorand is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
Algorand MCP Server
A comprehensive Model Context Protocol (MCP) server that gives AI agents and LLMs full access to the Algorand blockchain. Built by GoPlausible.
Algorand is a carbon-negative, pure proof-of-stake Layer 1 blockchain with instant finality, low fees, and built-in support for smart contracts (AVM), standard assets (ASAs), and atomic transactions.
What is MCP?
Model Context Protocol is an open standard that lets AI applications connect to external tools and data sources. This server exposes Algorand blockchain operations as MCP tools that any compatible AI client can use — Claude Desktop, Claude Code, Cursor, Windsurf, and others.
Features
- Secure wallet management via OS keychain — private keys never exposed to agents or LLMs
- Wallet accounts nicknames, allowances, and daily limits for safe spending control
- Account creation, key management, and rekeying
- Transaction building, signing, and submission (payments, assets, applications, key registration)
- Atomic transaction groups
- TEAL compilation and disassembly
- Full Algod and Indexer API access
- NFDomains (NFD) name service integration
- x402 and AP2 toolins for Algorand
- Tinyman AMM integration (pools, swaps, liquidity)
- ARC-26 URI and QR code generation
- Algorand knowledge base with full developer documentation taxonomy
- Per-tool-call network selection (mainnet, testnet, localnet) and pagination
Requirements
- Node.js v20 or later
- npm, pnpm, or yarn
Installation
From npm
npm install -g @goplausible/algorand-mcp
From source
git clone https://github.com/GoPlausible/algorand-mcp.git
cd algorand-mcp
npm install
npm run build
MCP Configuration
The server runs over stdio. There are three ways to invoke it — pick whichever suits your setup:
| Method | Command | When to use |
|---|---|---|
| npx (recommended) | npx @goplausible/algorand-mcp | No install needed, always latest version |
| Global install | algorand-mcp | After npm install -g @goplausible/algorand-mcp |
| Absolute path | node /path/to/dist/index.js | Built from source or local clone |
No environment variables are required for standard use. Network selection, pagination, and node URLs are all handled dynamically per tool call.
OpenClaw
No manual configuration needed — install the @goplausible/openclaw-algorand-plugin npm package and the Algorand MCP server is configured automatically:
npm install -g @goplausible/openclaw-algorand-plugin
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Using npx:
{
"mcpServers": {
"algorand-mcp": {
"command": "npx",
"args": ["@goplausible/algorand-mcp"]
}
}
}
Using global install:
{
"mcpServers": {
"algorand-mcp": {
"command": "algorand-mcp"
}
}
}
Using absolute path:
{
"mcpServers": {
"algorand-mcp": {
"command": "node",
"args": ["/absolute/path/to/algorand-mcp/dist/index.js"]
}
}
}
Claude Code
Create .mcp.json in your project root (project scope) or ~/.claude.json (user scope):
{
"mcpServers": {
"algorand-mcp": {
"type": "stdio",
"command": "npx",
"args": ["@goplausible/algorand-mcp"]
}
}
}
Or add interactively:
claude mcp add algorand-mcp -- npx @goplausible/algorand-mcp
Cursor
Add via Settings > MCP Servers, or edit .cursor/mcp.json in your project root:
{
"mcpServers": {
"algorand-mcp": {
"command": "npx",
"args": ["@goplausible/algorand-mcp"]
}
}
}
Windsurf
Add via Settings > MCP, or edit ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"algorand-mcp": {
"command": "npx",
"args": ["@goplausible/algorand-mcp"]
}
}
}
VS Code / GitHub Copilot
Edit .vscode/mcp.json in your workspace root, or open Settings > MCP Servers:
{
"servers": {
"algorand-mcp": {
"type": "stdio",
"command": "npx",
"args": ["@goplausible/algorand-mcp"]
}
}
}
Cline
Add via the MCP Servers panel in the Cline sidebar, or edit ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json (macOS):
{
"mcpServers": {
"algorand-mcp": {
"command": "npx",
"args": ["@goplausible/algorand-mcp"],
"disabled": false
}
}
}
OpenAI Codex CLI
Create .codex/mcp.json in your project root or ~/.codex/mcp.json for global scope:
{
"mcpServers": {
"algorand-mcp": {
"command": "npx",
"args": ["@goplausible/algorand-mcp"]
}
}
}
Open Code
Edit ~/.config/opencode/config.json:
{
"mcp": {
"algorand-mcp": {
"type": "stdio",
"command": "npx",
"args": ["@goplausible/algorand-mcp"]
}
}
}
Any MCP-compatible client
The server speaks the standard MCP stdio protocol. For any client not listed above, configure it with:
- Command:
npx(oralgorand-mcpif globally installed, ornode /path/to/dist/index.js) - Args:
["@goplausible/algorand-mcp"](for npx) - Transport:
stdio
Network Selection
Every tool accepts an optional network parameter: "mainnet" (default), "testnet", or "localnet". Algod and Indexer URLs are built-in for mainnet and testnet via AlgoNode.
Example tool call:
{ "name": "api_algod_get_account_info", "arguments": { "address": "ABC...", "network": "testnet" } }
If no network is provided, tools default to mainnet.
Pagination
API responses are automatically paginated. Every tool accepts an optional itemsPerPage parameter (default: 10). Pass the pageToken from a previous response to fetch the next page.
Secure Wallet
Architecture
The wallet system has two layers of storage, each with a distinct security role:
| Layer | What it stores | Where | Encryption |
|---|---|---|---|
| OS Keychain | Mnemonics (secret keys) | macOS Keychain / Linux libsecret / Windows Credential Manager | OS-managed, hardware-backed where available |
| Embedded SQLite | Account metadata (nicknames, allowances, spend tracking) | ~/.algorand-mcp/wallet.db | Plaintext (no secrets) |
Private key material never appears in tool responses, MCP config files, environment variables, or logs. The agent only sees addresses, public keys, and signed transaction blobs.
How it works
Agent (LLM) MCP Server Storage
────────── ────────── ───────
│ │ │
│ wallet_add_account │ │
│ { nickname: "main" } │ │
│ ──────────────────────────► │ generate keypair │
│ │ store mnemonic ──────────► │ OS Keychain (encrypted)
│ │ store metadata ──────────► │ SQLite (nickname, limits)
│ ◄─ { address, publicKey } │ │
│ │ │
│ wallet_sign_transaction │ │
│ { transaction: {...} } │ │
│ ──────────────────────────► │ check spending limits │
│ │ retrieve mnemonic ◄────── │ OS Keychain
│ │ sign in memory │
│ ◄─ { txID, blob } │ (key discarded) │
│ │ │
- Account creation (
wallet_add_account) — Generates a keypair (or imports a mnemonic), stores the mnemonic in the OS keychain, and stores metadata (nickname, spending limits) in SQLite. Returns only address and public key. - Active account — One account is active at a time.
wallet_switch_accountchanges it by nickname or index. All signing and query tools operate on the active account. - Transaction signing (
wallet_sign_transaction) — Checks per-transaction and daily spending limits, retrieves the key from the keychain, signs in memory, discards the key. Returns only the signed blob. - Data signing (
wallet_sign_data) — Signs arbitrary hex data using raw Ed25519 via the@noble/curveslibrary (no Algorand SDK prefix). Useful for off-chain authentication. - Asset opt-in (
wallet_optin_asset) — Creates, signs, and submits an opt-in transaction for the active account in one step.
Spending limits
Each account has two configurable limits (in microAlgos, 0 = unlimited):
allowance— Maximum amount per single transaction. Rejects any transaction exceeding this.dailyAllowance— Maximum total spend per calendar day across all transactions. Automatically resets at midnight. Tracked in SQLite.
Platform keychain support
The keychain backend is provided by @napi-rs/keyring (Rust-based, prebuilt
FAQ
- What is the Algorand MCP server?
- Algorand is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Algorand?
- This profile displays 48 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.8 out of 5—verify behavior in your own environment before production use.
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★48 reviews- ★★★★★Carlos Ghosh· Dec 20, 2024
Algorand reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Soo Tandon· Dec 12, 2024
According to our notes, Algorand benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Omar Khan· Dec 4, 2024
Algorand has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Soo Srinivasan· Nov 27, 2024
We wired Algorand into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Charlotte Gupta· Nov 23, 2024
Algorand reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Amelia Rao· Nov 11, 2024
Algorand has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Amelia Patel· Oct 18, 2024
According to our notes, Algorand benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Henry Park· Oct 14, 2024
I recommend Algorand for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Sofia Bhatia· Oct 2, 2024
Strong directory entry: Algorand surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Yash Thakker· Sep 25, 2024
Algorand reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
showing 1-10 of 48