Skip to main content
Glama
Fantopy-ai

@fantopy/fantopy-mcp

Official
by Fantopy-ai
README.md
# Fantopy MCP — hosted connector migration

> **Deprecated local package:** this repository preserves the historical
> `@fantopy/mcp-server` source. Do not install or run this package for the current
> Fantopy game. The current connector is hosted and requires OAuth.

## Premier League fantasy for the agent era

Fantopy is free-play Premier League fantasy football. Play in the app or connect
an assistant to the **same account and 15-player team**. Start with read-only
access; team changes and friends' competition management are optional and limited
to the permissions the owner approves in Fantopy. Points and awards are virtual,
not cash or crypto. Your AI runtime is not included.

- Website: https://fantopy.ai
- Play: https://app.fantopy.ai
- **Remote MCP URL: `https://mcp.fantopy.ai/mcp`**
- **Authentication: OAuth, with user sign-in and consent in Fantopy**

The old World Cup prediction game, `/arena` onboarding, anonymous-agent creation,
wallet authentication and local npm/stdin-stdout setup are not the current path.

## Connect safely

1. In a client that supports remote MCP with OAuth, add
   `https://mcp.fantopy.ai/mcp` as the server URL. Configuration screens and formats
   vary by client; a skill or URL alone does not install a working connector.
2. Complete sign-in and consent in Fantopy's browser flow. Start with view/read
   permissions. Never hand passwords, one-time codes, recovery codes, wallet keys
   or bearer tokens to the assistant or paste them into chat or repository files.
3. After consent, discover the available tools. Begin with `get_context`, then
   `read_squad`, to inspect rules, deadlines, permissions and your existing team.
4. Ask for an explanation or proposal first. Only request changes you actually
   want, within the approved permissions and current deadline/version checks.
   Do not grant write access merely to test the connection.

Example first prompt:

> Read my Fantopy context and squad. Summarize my Premier League team, deadlines
> and approved permissions. Do not create a team, enter competitions or change
> anything.

## Verification and limitations

A protocol-level read-only acceptance test on **October 11, 2026** completed
browser consent, OAuth token exchange, MCP initialization, an 18-tool catalog,
`get_context` and `read_squad`. That is a dated protocol snapshot, **not proof of
acceptance in any branded client**. Discover the live catalog after consent;
availability depends on the current server and grant.

An unauthenticated request to the MCP URL returns HTTP 401 with OAuth discovery
metadata. This is expected, not evidence that the server has no tools.

## Local-test release candidate

[Fantopy Gameweek Manager plugin/skill](plugins/fantopy/README.md) is a
**local-test release candidate**, not a marketplace-approved release or proof of
acceptance in any named client. For local testing, copy only `plugins/fantopy/`
(including its `.cursor-plugin` directory), not this legacy repository root.
See its [remaining in-app acceptance checklist](plugins/fantopy/TESTING.md).
The root marketplace manifest only locates this plugin; it is not a submission
or approval. The deprecated package and source below remain historical.

## Historical repository

The TypeScript source, package manifest and lockfile are preserved for history.
This repository is not the current hosted server source or a deployment guide.
Do not publish a new version of the legacy npm package to connect to Fantopy.

[API_REFERENCE.md](API_REFERENCE.md) and [SPEC.md](SPEC.md) describe the retired
wallet/contest-era implementation, not the current service contract. Their
historical examples must not be used as current onboarding or action instructions.

For current integrations, use the hosted OAuth URL above and the live authorized
MCP tool schemas. Third-party listings may lag behind this migration notice.

## License

MIT

TDQS

A3.7/5.0

Scored across 12 tools

Disambiguation5/5

Each tool targets a distinct action: agent registration, contest entry, lineup management, results, payouts, and player/contest queries. The only potential overlap is between submit_lineup and update_lineup, but they are clearly differentiated by initial submission vs. updates. All other tools serve unique purposes.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., claim_payout, get_agent_info, list_contests). No mixing of styles, and the verbs clearly indicate the action (get, list, submit, update, register, enter, claim).

Tool Count5/5

12 tools is well-scoped for a fantasy football contest platform. It covers agent management, contest lifecycle, lineup operations, player data, and payouts without being overwhelming or too sparse. Each tool has a clear role.

Completeness4/5

Core CRUD-like operations are present: agent registration, contest entry/list, lineup submit/update, results retrieval, and payout claim. Missing features like wallet balance check or contest cancellation are minor gaps; the main workflows are supported.

Maintenance

ActivityMaintained
ResponsivenessNo issues