Skip to main content
Glama
borakilicoglu

iddaa-mcp

README.md
<p align="center">
  <img alt="iddaa-mcp cover" src="./public/cover.svg" />
</p>

<p align="center">
  <b>Real-time iddaa sportsbook data for your MCP workflows.</b>
</p>

<p align="center">
  <a href="https://www.npmjs.com/package/iddaa-mcp"><img alt="npm version" src="https://img.shields.io/npm/v/iddaa-mcp"></a>
  <a href="./LICENSE"><img alt="license" src="https://img.shields.io/github/license/borakilicoglu/iddaa-mcp"></a>
  <a href="https://www.npmjs.com/package/iddaa-mcp"><img alt="npm downloads" src="https://img.shields.io/npm/dt/iddaa-mcp"></a>
  <a href="https://packagephobia.com/result?p=iddaa-mcp"><img alt="install size" src="https://packagephobia.com/badge?p=iddaa-mcp"></a>
</p>

---

## ⚔ What is iddaa-mcp?

`iddaa-mcp` is an MCP server that gives you structured access to:

- live and upcoming sportsbook events
- competitions and leagues
- detailed match data
- highlighted events
- historical league fixtures

šŸ‘‰ Built for AI agents, automation, and developer workflows.

---

## šŸš€ Quick Start

Run instantly:

```bash
npx iddaa-mcp --stdio
```

---

## 🧠 What you get

- clean, structured sportsbook data
- MCP-compatible tools
- ready-to-use endpoints for agents
- localized responses (`tr`, `en`)

---

## šŸ”„ Why use it?

Instead of:

- scraping sportsbook data
- handling inconsistent APIs
- writing custom parsers

šŸ‘‰ just plug into MCP and use ready tools.

---

## ⚔ Available Tools

- `get_competitions`
- `get_events`
- `get_detailed_events`
- `get_highlighted_events`
- `get_league_fixture`

---

## 🧠 Example

```json
{
  "tool": "get_highlighted_events",
  "arguments": {
    "limit": 5,
    "locale": "en"
  }
}
```

---

## šŸ“Š League Fixture + Strategy

`get_league_fixture` supports:

- full season data
- weekly queries
- comeback analysis (`1→2`, `2→1`)
- optional strategies:
  - `martingale`
  - `fibonacci`

Example:

```json
{
  "tool": "get_league_fixture",
  "arguments": {
    "league": "Bundesliga",
    "strategy": "martingale"
  }
}
```

---

## 🌐 Transport Options

### stdio (default)

Best for local MCP clients like Cursor:

```json
{
  "mcpServers": {
    "iddaa-mcp-stdio": {
      "command": "npx",
      "args": ["iddaa-mcp", "--stdio"]
    }
  }
}
```

---

### HTTP (remote / local server)

Start server:

```bash
npx iddaa-mcp --http --port 4200
```

Connect:

```json
{
  "mcpServers": {
    "iddaa-mcp-http": {
      "url": "http://localhost:4200/mcp"
    }
  }
}
```

---

## šŸŒ Language Support

- default: `tr`
- optional: `en`

```json
{
  "locale": "en"
}
```

---

## āš™ļø Features

- MCP-native tool system
- stdio + HTTP support
- structured and predictable outputs
- type-safe schemas (`zod`)
- league fixture analysis
- strategy simulation
- AI-ready responses

---

## šŸ“¦ Install

```bash
npm install -g iddaa-mcp
```

or:

```bash
npx iddaa-mcp --stdio
```

---

## 🧠 Use Cases

- AI betting assistants
- sports data automation
- odds analysis pipelines
- MCP-based agents
- research & strategy testing

---

## šŸ’” Philosophy

> Give AI and developers clean, structured access to sportsbook data.

---

## ā¤ļø Support

If this tool helps you:

⭐ Star the repo  
ā˜• Support via GitHub Sponsors

https://github.com/sponsors/borakilicoglu

---

## šŸ”— Links

- GitHub: https://github.com/borakilicoglu/iddaa-mcp
- npm: https://www.npmjs.com/package/iddaa-mcp

TDQS

B3.1/5.0

Scored across 5 tools

Disambiguation3/5

get_events, get_detailed_events, and get_highlighted_events all fetch event data, with the latter two being specialized variants. While descriptions differentiate them, the generic get_events overlaps conceptually with get_detailed_events, requiring careful reading to choose correctly.

Naming Consistency5/5

All tools follow a consistent get_<resource> pattern with snake_case, making the API predictable and easy to navigate.

Tool Count5/5

Five tools is an appropriate size for a focused sportsbook API client, covering core data types without unnecessary bloat.

Completeness2/5

The tool set provides competition and event data, but lacks odds or market information, which is a core component of a sportsbook. This creates a notable gap for users expecting betting-related functionality.

Maintenance

ActivityInactive
ResponsivenessNo issues