Frequently Asked Questions about Dune Query MCP

Q: What is Dune Query MCP? A: Dune Query MCP is a bridge that connects Dune Analytics data to intelligent agents through the Model Control Protocol (MCP), allowing AI models to access and interact with blockchain data.

Q: What are the core capabilities of Dune Query MCP? A: The core capabilities include retrieving pre-computed query results (get_latest_result) and executing queries on-demand (run_query), both returning data in CSV format.

Q: What are the system requirements for running Dune Query MCP? A: You need Python 3.10 or higher and a valid Dune Analytics API key.

Q: How do I configure the API access? A: Copy the .env.example file to .env and add your Dune Analytics API key to the .env file.

Q: How do I run Dune Query MCP? A: You can run it as an MCP service using python run.py or as a web server using python flask_app.py.

Q: What is the data format returned by Dune Query MCP? A: All data is returned in CSV format, ensuring universal compatibility and easy parsing.

Q: What is UBOS and how does it relate to Dune Query MCP? A: UBOS is a full-stack AI Agent Development Platform that can orchestrate AI Agents, connect them with enterprise data, build custom AI Agents with your LLM model and Multi-Agent Systems. It provides the infrastructure needed to build and deploy sophisticated AI applications that leverage blockchain data accessed through Dune Query MCP.

Q: Can I contribute to the Dune Query MCP project? A: Yes, contributions are welcome! Fork the repository, create a feature branch, commit your changes, push to the branch, and open a Pull Request.

Q: What do I do if I get an API Key error? A: Ensure the .env file exists and contains a valid Dune Analytics API key.

Q: What do I do if I get a timeout error? A: Increase the timeout for complex queries by setting the DUNE_QUERY_TIMEOUT environment variable.