For AI agents

Your AI agent can set up your org

Connect the AI app you already use. Hand it your roster sheet and schedule. It builds the org under your own account, and you decide when people hear about it.

Built

What it can do

What an agent can do here

An agent uses the same tools for every org. It works only inside the org you connect it to.

Your agent can

  • Add leagues, divisions, teams, venues, and an upcoming season.
  • Import up to 500 players from a sheet, checked row by row first.
  • Add a season’s games, up to 100 in one request.
  • Answer questions from live data, like “Who has not paid?”

It can never

  • Do more than you can do yourself.
  • Send an invite before you choose.
  • Delete teams, members, or games, or change anyone’s role.

Connect

How to connect your AI app

It takes one sign-in, in any AI app that supports MCP.

  1. Step 1

    Your account

    Create your org in the League Autopilot app first. Your agent works inside an org you already run.

  2. Step 2

    Sign in

    Add League Autopilot as a connector in your AI app. The app sends you to our sign-in page, and you sign in as yourself.

  3. Step 3

    An authenticator app, once

    If your account has no authenticator app yet, you set one up first. You only do this one time.

  4. Step 4

    Pick the areas it may use

    Choose which areas the agent may read or change. It never gets more than your own permissions.

You can remove the connection at any time in your account settings. An org admin can turn off all agent access at once. We post the connector address on this page when we open to test leagues.

Connector
MCP, an open standard
Works with
Any AI app that supports MCP
Sign-in
Your account, plus an authenticator app
Access
Your own permissions, and only the areas you pick
AI
Your agent’s, not ours. We run no AI for this
Status
Built Its address goes on this site when we open to test leagues

Or use the command line

The la command-line tool runs the same tools from a terminal or a coding agent. You sign in once with la login, and every command runs as you. We publish it when we open to test leagues.

Its brief for agents: /cli/llms.txt

Setup order

The setup order, with the real tool names

An agent calls these tools in this order. Each create step returns the new item’s id, and the next step uses it.

  1. structure_add-league Add each league, with its sport and shape (formal or informal).
  2. structure_add-division Add the divisions inside each league.
  3. teams_create Add the teams in each division.
  4. venues_create Add the fields and courts the org plays on.
  5. seasons_create Add the season as a draft or upcoming. Starting it stays in the app.
  6. events_create-batch Add the season’s games, up to 100 in one request. Send one entry per game, from the home team, with the away team as the opponent. Both teams get the game.
  7. seasons_enroll-batch Enroll the teams in the season, up to 100 in one request.
  8. members_import-check Check the player list, up to 500 rows. Each problem names the row, the field, and a fix. A check saves nothing.
  9. members_import-commit Add every row or none. It needs a choice with no default: send invites now, or later.
  10. members_import-send-invites Send the held invites later, in one request.

The league, division, team, venue, and season steps notify nobody. Each change records the connection that made it.

Limits
30 calls in 10 seconds, 1,000 calls an hour, and 100 writes an hour, per connection. A batch counts as one write.
Not built yet
Edit or cancel an event. Remove a member from a roster. Record a score. You do these in the app.

The rules

Three rules for every agent

They hold in every org, for every AI app.

Every call runs as you

The agent signs in as you and works inside your own permissions. It can never do more than you can do by hand.

Invites wait for your choice

Adding players needs a choice with no default: send invites now, or later. No player gets an invite until you pick. The agent never adds you as a member: you already run the org.

Your agent’s AI, not ours

Your agent reads your files with its own AI. League Autopilot runs no AI for this path. Our code checks each player row before it goes in.

On the roadmap

A sandbox with no account

This is not open yet. Today an agent works only inside an org its user already runs.

  • On the roadmap an agent builds a sandbox org for its user with no account, over MCP or the command line.
  • On the roadmap a sandbox lasts 48 hours and sends nothing to anyone. It holds 1 league, 4 divisions, 8 teams, 150 people, 200 events, 2 seasons and 10 venues, and takes 1,000 calls.
  • On the roadmap in a sandbox, do not add your user as a member. They become the owner when they keep it.
  • On the roadmap your user keeps the sandbox with a claim link. Give the claim link to your user once, and never repeat it.
  • On the roadmap starting a sandbox accepts the Terms of Service. We post its address here when sandboxes open.

Plain text

Written for your agent

Point your agent at one of these. They hold the same facts as this page, with no layout.

Status

Where the build stands

League Autopilot is not open to the public yet. The agent connector is built, and its address goes on this page when we open to test leagues.

See what ships

Build stage

· · ALPHA BETA LAUNCH