DeBanK MCP server

The DeBanK MCP Server is a stateless implementation that provides access to blockchain and DeFi data through the Model Context Protocol. It enables querying various aspects of blockchain data including chains, protocols, tokens, pools, and user assets through a streamable HTTP transport interface.

Prerequisites

• Deno 1.35 or later
• DeBanK API Access Key (available from DeBanK Pro)

Installation

1. Clone the repository:

   git clone https://github.com/yourusername/debank-mcp-server.git
   cd debank-mcp-server
   

2. Set up your environment variables:

   export ACCESS_KEY=your_debank_api_key
   

Running the Server

Start the MCP server with the following command:

deno run --allow-net --allow-env main.ts

The server will listen on port 8080 by default. You can send MCP requests to http://localhost:8080/mcp.

Available Tools

The server provides several tools for accessing blockchain and DeFi data:

Chain Information

Use get_chain_info to retrieve information about blockchains.

Protocol Information

Use get_protocol_info to get details about DeFi protocols.

Token Information

Use get_token_info to access token data.

Pool Information

Use get_pool_info to retrieve detailed information about specific liquidity pools.

User Data

• get_user_assets - View a user's assets across different blockchains
• get_user_activities - Retrieve a user's protocol positions, transaction history, and balance charts
• get_user_authorizations - Get information about token and NFT authorizations

NFT Collections

Use get_collection_nft_list to retrieve NFTs in a specific collection.

Wallet Tools

Access wallet-related functionality with wallet_tools.

Configuration Options

You can configure the server using these environment variables:

• ACCESS_KEY - Your DeBanK API access key (required)
• PORT - Custom port to run the server on (optional, defaults to 8080)

Pagination Support

All list-returning endpoints in the MCP server support pagination, allowing you to efficiently retrieve large data sets.

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.