RootData MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@RootData MCP Server search for projects related to decentralized finance"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
RootData MCP Server
Introduction
这是一个基于 Model Context Protocol (MCP) 的服务器,用于集成 RootData API,提供加密货币和区块链项目的数据查询功能。
它允许 Claude 和其他 AI 助手通过 MCP 接口直接获取项目信息、机构详情和搜索结果。
Related MCP server: Flow MCP Server
Available Tools
本服务器提供以下 MCP 工具:
search: 根据关键词搜索项目/VC/人物的简要信息
get_project: 根据项目 ID 获取项目的详细信息
get_organization: 根据机构 ID 获取风投机构的详细信息
Setup
Prerequisites
Python 3.10 或更高版本
uv 包管理器(推荐)
Installation
克隆此仓库:
git clone https://github.com/jincai/rootdata-mcp-server
cd rootdata-mcp-server如果你还没有安装 uv,可以安装它:
# macOS/Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
# Windows
curl -LsSf https://astral.sh/uv/install.ps1 | powershell安装依赖:
# 创建虚拟环境并激活
uv venv
source .venv/bin/activate # Windows 上: .venv\Scripts\activate
# 安装依赖
uv add "mcp[cli]" httpx python-dotenv设置环境变量:
# 创建 .env 文件存储 API 密钥
cp .env.example .env
# 在 .env 文件中设置 API 密钥
ROOTDATA_API_KEY=your-rootdata-api-key运行服务器:
uv run server.pyConnecting to Claude Desktop
安装 Claude Desktop(如果你还没有安装)
创建或编辑 Claude Desktop 配置文件:
# macOS
mkdir -p ~/Library/Application\ Support/Claude/
nano ~/Library/Application\ Support/Claude/claude_desktop_config.json添加以下配置:
{
"mcpServers": {
"rootdata": {
"command": "/path/to/uv",
"args": [
"--directory",
"/absolute/path/to/rootdata-mcp-server",
"run",
"server.py"
]
}
}
}将 /path/to/uv 替换为 which uv 的结果,将 /absolute/path/to/rootdata-mcp-server 替换为此项目的绝对路径。
重启 Claude Desktop
现在你应该能在 Claude Desktop 的工具菜单(锤子图标)中看到 RootData 工具
尝试向 Claude 提问,例如:
"搜索以太坊相关的项目"
"获取项目 ID 为 12 的详细信息"
"查询机构 ID 为 219 的风投机构信息"
License
MIT
Available Tools
3 toolsget_organizationC
Obtain VC details according to VC ID.
Args:
org_id: Organization ID
include_team: Whether to include team member information, default is false.
include_investments: Whether it includes investment project information, default is false.
Inputs: org_id (required), include_team, include_investments. Returns: result
get_projectB
Obtain project details according to the project ID.
Args:
project_id: The unique identifier for the project.
include_team: Whether to include team member information, default is false.
include_investors: Whether to include investor information, default is false.
Inputs: project_id (required), include_team, include_investors. Returns: result
searchB
Search for Project/VC/People brief information according to keywords.
Args:
query: Search keywords, which can be project/institution names, tokens, or other related terms.
Inputs: query (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_organization retrieves VC details, get_project retrieves project details, and search performs keyword-based searches across multiple entity types. There is no overlap in functionality, and an agent can easily differentiate between them based on their specific objectives.
All tool names follow a consistent verb_noun pattern: get_organization, get_project, and search. The naming is uniform, using snake_case throughout, with clear and predictable verbs that accurately describe each tool's action.
With only 3 tools, the server feels thin for a data-focused domain like VC and project details. While the tools cover basic retrieval and search, the scope suggests that additional operations (e.g., listing, filtering, or updating) might be expected, making the count borderline for comprehensive coverage.
The server provides read operations (get and search) but lacks create, update, or delete tools, which are typical for data management. This creates notable gaps in lifecycle coverage, as agents cannot modify or add data, limiting the server to query-only functionality.
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Hosted Web Crawler MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Pageform is an AI-native data room platform with a remote MCP server for Claude and other MCP-compatible clients. Upload and organize documents, generate structured data rooms with AI, audit missing materials, create secure share links, and analyze investor engagement directly from your AI assistant. Built for fundraising, investor relations, diligence, and deal workflows. Connect securely through Pageform OAuth. Website: https://pageform.io Documentation: https://pageform.io/docs/integrations/claude
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server utilizing Claude AI for generating intelligent queries and offering documentation assistance based on API documentation analysis.15 npm3MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to access Flow blockchain data and perform operations such as checking balances, resolving domains, executing scripts, and submitting transactions.1MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that connects Claude to Heurist Mesh APIs, providing access to various blockchain and web3 tools including cryptocurrency data, token security, Twitter intelligence, and web search capabilities.2067MIT

Blockscout MCP Serverofficial
FlicenseAqualityCmaintenanceA server that exposes blockchain data (balances, tokens, NFTs, contract metadata) via the Model Context Protocol, enabling AI agents and tools to access and analyze blockchain information contextually.1846-