# Squiggle [Health: Active]

**Category:** 🏃 Sports  
**Repository:** https://github.com/pipeworx-io/mcp-squiggle  
**GitHub Stars:** 0  
**npm Downloads (last month):** 480  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/squiggle

## Description
AFL (Australian Football League) fixture, ladder, and crowd-sourced tips

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "squiggle": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-squiggle"]
  }
}
```

## Documentation

## What the Squiggle MCP server does

The Squiggle MCP server exposes Australian Football League data from Squiggle’s API through the Model Context Protocol. It covers team lists, scheduled and completed games, competition standings, registered tipping sources, game-by-game tips, and source-specific projected ladders.

The service is keyless, so no API credential is needed for the documented connection methods. It is suitable for agents that need to answer questions about AFL fixtures, past results, current or historical ladders, or crowd-sourced predictions.

## How it works

The hosted connection uses the Pipeworx gateway at `https://gateway.pipeworx.io/squiggle/mcp`. MCP clients can discover and call the Squiggle tools through that URL. The underlying data source is `https://api.squiggle.com.au`; Squiggle’s terms request that clients identify themselves with a descriptive user agent.

The hosted pack endpoint lists the six Squiggle tools along with shared Pipeworx meta-tools. These include routing and discovery functions such as `ask_pipeworx`, `discover_tools`, and `search_within`, plus memory-related tools. The exact scope is returned during MCP initialization. A full Pipeworx gateway connection is also available at `https://gateway.pipeworx.io/mcp` and lists the wider catalog directly.

## Setup and configuration

For a remote MCP setup, add the Squiggle endpoint to a compatible client:

```json
{
  "mcpServers": {
    "squiggle": {
      "url": "https://gateway.pipeworx.io/squiggle/mcp"
    }
  }
}
```

The Squiggle MCP server also runs locally without a Pipeworx account or gateway round trip. Use the npm package with a stdio configuration:

```json
{
  "mcpServers": {
    "squiggle": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-squiggle"]
    }
  }
}
```

The local process communicates over stdin and stdout and exposes only the pack’s own tools. HTTP clients can call individual gateway tools directly through endpoints such as `/v1/tools/squiggle_teams`.

## Tools and capabilities

- `teams(year?)` returns the team list, optionally for a specified year.
- `games(year?, round?, complete?)` provides fixtures and results, with optional year, round, and completion filters.
- `standings(year?, round?)` returns the ladder for a selected year and round.
- `sources()` lists registered tipping sources.
- `tips(year?, round?, source?)` returns tips for each game from an optional source.
- `ladder(year?, round?, source?)` returns a projected ladder associated with an optional tipping source.

The gateway’s `ask_pipeworx` tool can accept a plain-language question and select a tool and arguments automatically, including questions about Squiggle data.

## Limitations and notes

The hosted pack endpoint currently includes shared gateway tools in addition to the Squiggle tools. If an agent needs only this pack’s schemas, use the standalone stdio package instead. If several pack endpoints would create unnecessary duplicate meta-tools, the full gateway provides the catalog through one connection.

The source is AFL-specific and does not provide general sports data through the documented pack tools. The package is licensed under MIT. No environment variables or account credentials are required by the documented setup examples.

_Full upstream README: https://allmcps.com/mcp/squiggle/readme_