Dune Analytics MCP Server
A mcp server that bridges Dune Analytics data to AI agents.
Features
- Tools:
get_latest_result: Fetch the latest results of a Dune query by ID.run_query: Execute a Dune query by ID and retrieve results.
- CSV Output: All results are returned as CSV-formatted strings for easy processing.
Prerequisites
- Python 3.10+
- A valid Dune Analytics API key (get one from Dune Analytics)
Installation
Installing via Smithery
To install Dune Analytics for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @kukapay/dune-analytics-mcp --client claude
Manual Installation
-
Clone the Repository:
git clone https://github.com/kukapay/dune-analytics-mcp.git cd dune-analytics-mcp
-
Set Up Environment Variables: Create a
.envfile in the project root:DUNE_API_KEY=your_api_key_hereAlternatively, set it as a system environment variable:
export DUNE_API_KEY="your_api_key_here"
Usage
Running the Server
-
Development Mode:
mcp dev main.py
This starts the server with hot reloading for development.
-
Install for Claude Desktop:
mcp install main.py --name "Dune Analytics"
Installs the server as a service for use with Claude Desktop.
Tool Usage
-
get_latest_result(query_id)- Description: Retrieves the latest results of a specified Dune query.
- Input:
query_id(int) - The ID of the Dune query. - Output: CSV-formatted string of the query results.
- Example:
get_latest_result(query_id=4853921)
-
run_query(query_id)- Description: Executes a Dune query and returns the results.
- Input:
query_id(int) - The ID of the Dune query to run. - Output: CSV-formatted string of the query results.
- Example:
run_query(query_id=1215383)
Example Commands in Claude Desktop
- "Get latest results for dune query 1215383"
- "Run dune query 1215383"
License
This project is licensed under the MIT License - see the LICENSE file for details.
Metadata
Release files for iflow-mcp_dune-analytics-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_dune_analytics_mcp-0.1.0.tar.gz | 3.8 kB | Without provenance | Details for iflow_mcp_dune_analytics_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_dune_analytics_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_dune_analytics_mcp-0.1.0-py3-none-any.whl |
Total release size: 8.4 kB
Release files / iflow_mcp_dune_analytics_mcp-0.1.0.tar.gz
| Download URL | iflow_mcp_dune_analytics_mcp-0.1.0.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1f0e6deb04fd6b02766ce5b74540e9eedac07f477aa5be85b09e88dad1034f06
|
|
BLAKE2b-256 checksum How to use checksums |
29b7a3977ede064a8f926b85c1c968729ca7a0ea06c8be7b4081d485e7a3f59e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.9
|
Release files / iflow_mcp_dune_analytics_mcp-0.1.0-py3-none-any.whl
| Download URL | iflow_mcp_dune_analytics_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5abaeac15a689e897f2cfed9277cd174dcdb73e4cd8a5be4e53cbe3b4e4d15e2
|
|
BLAKE2b-256 checksum How to use checksums |
b90f0bf7fd54d2fa91eee075adab00dc364327af6aa0294f447404e3d773d9a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.9
|
Security for iflow-mcp_dune-analytics-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.