OpenDota MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is OpenDota MCP Server?

OpenDota MCP Server is a Model Context Protocol (MCP) server implementation that allows access to OpenDota API data, enabling LLMs and AI assistants to retrieve real-time Dota 2 statistics, match data, player information, and more through a standard interface.

how to use OpenDota MCP Server?

To use the OpenDota MCP Server, clone the repository, set up your environment, and run the server. You can also create an OpenDota API key for enhanced functionality.

key features of OpenDota MCP Server?

  • Access player profiles, statistics, and match history
  • Retrieve detailed match information
  • Look up professional players and teams
  • Get hero statistics and rankings
  • Search for players by name
  • And more!

use cases of OpenDota MCP Server?

  1. Retrieving player statistics for analysis
  2. Accessing match data for research purposes
  3. Integrating Dota 2 data into AI applications

FAQ from OpenDota MCP Server?

  • How do I set up the server?

You can set up the server by cloning the repository and following the installation instructions provided in the documentation.

  • Is an OpenDota API key required?

While it's optional, having an API key is recommended for accessing certain features.

  • What programming language is used?

The server is implemented in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago