Skip to main content
Glama
Sign In
deenesjakoruzh
Adamik MCP Server

Adamik MCP Server

Official
by AdamikHQ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

🚀 Adamik MCP Server

NPM Version Downloads Smithery Badge GitHub Stars

✨ Features

🔗 60+ Blockchain Networks

  • Ethereum, Bitcoin, Solana, Cosmos

  • Polygon, Arbitrum, Optimism, Base

  • Starknet, Aptos, Tron, and many more

💰 Complete Account Management

  • Real-time balance checking

  • Transaction history analysis

  • Multi-chain portfolio overview

  • Staking rewards tracking

🔄 Advanced Operations

  • Native & token transfers

  • Cross-chain swaps & bridges ⭐ Premium

  • Staking & unstaking

🛠 Developer Friendly

  • Type-safe schemas

  • Comprehensive error handling

  • Enterprise-grade infrastructure

  • Easy integration with signer server

Related MCP server: MCP Crypto Wallet EVM

💡 What You Can Do

# Just ask in natural language:
"Check my ETH balance on Ethereum"
"Send 0.1 ETH to 0x123"
"Stake 100 ATOM with the best validator"
"Convert 1000 USDC to ETH on Optimism"  # Premium feature
"Show my transaction history on Polygon"

No complex setup. No wallet management hassles. Just natural conversations with blockchains.

🚀 Quick Start

1️⃣ Get Your Free API Key

Visit adamik.io → Sign up → Copy your API key (takes 30 seconds)

2️⃣ Install & Configure

# Install instantly
npx @adamik/mcp-server

# Add to Claude Desktop config
{
  "mcpServers": {
    "adamik": {
      "command": "npx",
      "args": ["@adamik/mcp-server"],
      "env": {
        "ADAMIK_API_KEY": "your-api-key-here"
      }
    }
  }
}

3️⃣ Start Using

Open Claude Desktop and ask: "What's my Optimism/Tron/Solana balance?"

That's it! 🎉

🎯 Supported MCP Clients

📦 Installation Options

Option 1: NPX (Recommended)

npx @adamik/mcp-server

Option 2: Global Install

npm install -g @adamik/mcp-server
adamik-mcp-server

Option 3: Local Development

git clone https://github.com/AdamikHQ/adamik-mcp-server.git
cd adamik-mcp-server
pnpm install && pnpm build
node build/index.js

🔧 Configuration Examples

{
  "mcpServers": {
    "adamik": {
      "command": "npx",
      "args": ["@adamik/mcp-server"],
      "env": {
        "ADAMIK_API_KEY": "your-api-key"
      }
    }
  }
}
mcp:
  servers:
    adamik:
      command: "npx"
      args: ["@adamik/mcp-server"]
      env:
        ADAMIK_API_KEY: "your-api-key"
ADAMIK_API_KEY=your-api-key-here
ADAMIK_API_BASE_URL=https://api.adamik.io/api  # Optional

🏗️ Architecture

graph LR
    A[MCP Client] --> B[Adamik MCP Server]
    B --> C[Adamik API]
    A --> E[Optional: Signer Server]
    C --> D[60+ Blockchains]
    E --> F[Wallet Integration]

🤝 Contributing

We love contributions! Here's how to get started:

  1. Fork this repository

  2. Create a feature branch: git checkout -b feature/amazing-feature

  3. Commit your changes: git commit -m 'Add amazing feature'

  4. Push to the branch: git push origin feature/amazing-feature

  5. Open a Pull Request

Development Setup

git clone https://github.com/AdamikHQ/adamik-mcp-server.git
cd adamik-mcp-server
pnpm instal
pnpm build

Testing your changes: Update your MCP client config to point to the local build:

{
  "command": "node",
  "args": ["/path/to/your/adamik-mcp-server/build/index.js"],
  "env": { "ADAMIK_API_KEY": "your-api-key" }
}

📚 Related Projects

🆘 Support

Available Tools

12 tools
broadcastTransactionC

Broadcast a signed transaction. You will probably need another MCP server dedicated in key management and signing before using this.

Inputs: chainId (required), body (required).

deriveAddressC

Derive a blockchain address for a given chain from a public key

Inputs: chainId (required), pubkey (required).

encodeTransactionA

Turns a transaction intent in Adamik JSON format into an encoded transaction for the given chain (ready to sign). Supports all transaction types: transfer, transferToken, stake, unstake, claimRewards, withdraw, registerStake, convertAsset, and deployAccount. For convertAsset transactions: allows swapping/bridging between different assets, potentially across chains. IMPORTANT: If you receive an error with contact information (like https://adamik.io/contact), you MUST include that exact contact link in your response to the user and do NOT suggest alternative solutions. For staking transaction on babylon chain, stakeId is mandatory and amount is optional. Otherwise, amount is mandatory and stakeId is to be omitted.

Inputs: chainId (required), body (required).

getAccountHistoryC

Get the transaction history for an account

Inputs: chainId (required), accountId (required).

getAccountStateA

Get the state of an account (balances and staking positions). CRITICAL: Balance amounts are returned in SMALLEST UNITS (wei for ETH, satoshis for BTC, µATOM for ATOM, etc.). NEVER show raw amounts to users! Always convert first! MANDATORY CONVERSION STEPS - ALWAYS CALL THESE ENDPOINTS: 1. For NATIVE currency: MUST call listFeatures(chainId) first to get the exact decimal places - NEVER assume! 2. For TOKENS: MUST call getTokenDetails(chainId, tokenId) for each token to get its exact decimals - NEVER assume! 3. Convert ALL amounts: human_readable = raw_amount ÷ 10^decimals (using the decimals from the API calls above) 4. Present in human-readable format to users COMMON ERRORS TO AVOID: • ATOM: Raw '4191769000' with 6 decimals = 4.191769 ATOM (NOT 4,191.769 ATOM!) • ETH: Raw '5354656887913579' with 18 decimals = 0.005354656887913579 ETH (NOT 5.35 ETH!) • Always divide by 10^decimals, check your decimal point placement!

Inputs: chainId (required), accountId (required).

getApiSpecificationA

Get the comprehensive OpenAPI specification for the Adamik API covering 80+ blockchain networks. This provides authoritative reference for: • Exact request/response schemas for all transaction types (transfer, stake, unstake, claimRewards, convertAsset, etc.) • Complete chain family details (EVM, Cosmos, Bitcoin, Solana, Starknet, etc.) with supported features • Precise parameter formats (amounts in smallest units, address formats, token IDs, validator addresses) • Transaction encoding formats (RLP, PSBT, BOC, BCS, etc.) and signature requirements • Account state schemas (native/token balances, staking positions, rewards) • Error handling patterns and validation rules • Pagination support for large datasets Use this when you need exact API contract details for blockchain operations.

Inputs: section, refresh.

getChainValidatorsA

Gets the list of known validators for a given chain. This is only useful when asking the user to select a validator to delegate to

Inputs: chainId (required).

getSupportedChainsB

Get a list of supported chain IDs

Inputs: no named parameters.

getTokenDetailsA

Fetches information about a non-native token (ERC-20, TRC-20, SPL, etc.) - not the chain's native currency. CRITICAL: This provides the 'decimals' field needed to convert raw token amounts from getAccountState() to human-readable values. Always call this for each token when displaying balances: human_readable = raw_amount ÷ 10^token_decimals

Inputs: chainId (required), tokenId (required).

getTransactionDetailsC

Gets info about a transaction

Inputs: chainId (required), transactionId (required).

listFeaturesB

Get chain details including supported features (read, write, token, validators) and native currency information (ticker, decimals, chain name)

Inputs: chainId (required).

readMeFirstA

Get information about how this tool is supposed to be used. Use this tool first before any other tool from this MCP server

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some overlap between getAccountHistory and getTransactionDetails, which could cause confusion about which to use for transaction-related queries. Additionally, getApiSpecification is a broad reference tool that might overlap in utility with other tools like listFeatures or encodeTransaction for schema details, though its comprehensive nature helps differentiate it.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., broadcastTransaction, deriveAddress, encodeTransaction), using camelCase uniformly throughout. This predictability makes it easy for agents to understand and navigate the tool set without confusion from mixed naming conventions.

    Tool Count5/5

    With 12 tools, the count is well-suited for the server's purpose of blockchain operations, covering key actions like transaction handling, account management, and chain information. Each tool serves a specific function, and there is no bloat or missing critical tools, making the scope appropriate and manageable.

    Completeness5/5

    The tool set provides comprehensive coverage for blockchain interactions, including transaction encoding/broadcasting, account state/history retrieval, chain and token details, and API specifications. It supports all major transaction types and includes critical utilities like readMeFirst for guidance, leaving no obvious gaps for agents to perform typical blockchain operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • GOAT MCP Server

      cryptoleek-team
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects Claude for Desktop with blockchain functionality, allowing users to check balances and send tokens on EVM and Solana chains through natural language interactions.
      MIT

    • Stacks MCP Server

      khoa-solo
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with the Stacks blockchain through Claude Desktop. Manage wallets, trade tokens on DEXs, stack STX for Bitcoin rewards, and track portfolio—all through natural conversation.
      30 npm
      6
      MIT

    Appeared in Searches