Skip to main content
Glama
README.md
# Alchemy MCP Plugin

[![smithery badge](https://smithery.ai/badge/@itsanishjain/alchemy-sdk-mcp)](https://smithery.ai/server/@itsanishjain/alchemy-sdk-mcp)

This MCP plugin provides integration with the Alchemy SDK for blockchain and NFT operations.

## Features

- Get NFTs for a wallet address
- Get NFT metadata
- Get latest block number
- More endpoints can be added as needed

## Setup

### Installing via Smithery

To install alchemy-sdk-mcp for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@itsanishjain/alchemy-sdk-mcp):

```bash
npx -y @smithery/cli install @itsanishjain/alchemy-sdk-mcp --client claude
```

### Manual Installation
1. Install dependencies:
```bash
npm install
```

2. Build the project:
```bash
npm run build
```

3. Configure your Alchemy API key:
   - Get an API key from [Alchemy](https://www.alchemy.com/)
   - Update the `ALCHEMY_API_KEY` in `settings.json`

4. Start the server:
```bash
npm start
```

## Available Endpoints

### 1. Get NFTs for Owner
```typescript
POST /getNftsForOwner
{
    "owner": "wallet_address"
}
```

### 2. Get NFT Metadata
```typescript
POST /getNftMetadata
{
    "contractAddress": "contract_address",
    "tokenId": "token_id"
}
```

### 3. Get Block Number
```typescript
POST /getBlockNumber
```

## Error Handling

All endpoints include proper error handling and logging. Errors are returned in the format:
```json
{
    "error": "Error message"
}
```

## Logging

The server implements comprehensive logging using console.error for better debugging:
- [Setup] logs for initialization
- [API] logs for API calls
- [Error] logs for error handling



$env:ALCHEMY_API_KEY="KRdhdsBezoTMVajIknIxlXgBHc1Pprpw"; node dist/index.js

TDQS

B3.2/5.0

Scored across 22 tools

Disambiguation4/5

Most tools have distinct purposes, but there is some overlap between get_nfts_for_owner and get_contracts_for_owner, as well as between get_asset_transfers, get_transfers_for_contract, and get_transfers_for_owner, which could cause minor confusion. However, descriptions help clarify the specific focus of each tool.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores, such as get_block_number, estimate_gas_price, and lookup_address. There are no deviations in naming conventions, making the set highly predictable and readable.

Tool Count3/5

With 22 tools, the count is on the higher side for a blockchain-focused server, bordering on heavy but still manageable. It covers multiple aspects like NFTs, tokens, transactions, and events, but may feel slightly bloated compared to more streamlined sets.

Completeness5/5

The tool set provides comprehensive coverage for blockchain interactions, including data retrieval (blocks, transactions, NFTs, tokens), metadata access, transfers, ownership queries, and event subscriptions. There are no obvious gaps, and it supports full lifecycle operations for the domain.

Maintenance

ActivityInactive
ResponsivenessNo issues