lekkin

Help / Developers

Connecting an AI assistant

DevelopersAnybody who works at a club that allows AI assistants4 min read

If you already use an AI assistant, you can connect it to LEKKIN and ask it to do club work for you, as you: who can play on Saturday, which bookings are unpaid, book the pitch for Tuesday’s training. It can only do what you can do yourself.

What it is

LEKKIN has a connection for AI assistants. You give your assistant one address, sign in, and choose what it may do and at which clubs. After that you can ask it about your club in your own words, and it answers from your club’s LEKKIN records.

It works as you. It can only do what you can do yourself, at the clubs you chose. A secretary’s assistant can’t do a manager’s job, and a manager’s assistant can’t do a secretary’s.

Before you start

You need three things:

  • Your club must allow it. A club admin switches it on in the Club Hub, under Configure → AI assistants. It’s off until they do. See Switching it on for your club below.
  • Your club needs the developer platform add-on. See Pricing.
  • Two-step sign-in on your own account: an authenticator app or a passkey. Set it up from your account at login.lekkin.app, under Account.

Connecting Claude

We’ve tested this with Claude, on claude.ai and in the Claude apps.

  1. In Claude, open Settings → Connectors, press Add, then Add custom connector.
  2. Paste this address: https://mcp.lekkin.app/mcp
  3. Connect it. Claude sends you to the LEKKIN sign-in page. Sign in as you normally would.
  4. A Connect …? screen asks two things:
    • What it can do. See your teams, squads, fixtures and what happened in each match, availability, pitches, bookings and what each is for, and sessions is ticked. Make changes for you: availability, bookings, pitch requests and sessions is not: tick it only if you want the assistant to change things.
    • Which clubs. Only clubs that allow assistants are offered. Choose the ones it may use.
  5. Press Allow. Or press Don’t allow, and nothing is connected.

Other assistants that support MCP connectors with sign-in may also work, using the same address.

What it can do

Not sure what it can do for you? Ask it. It can check your roles at each club and which jobs they let it do, and tell you why it can’t do something before it tries.

It can look up, at the clubs you connected it to:

  • your teams, and a squad, by name and squad number;
  • fixtures and results, and one match in full: the pitch booked for a home game, what happened (goals, cards, substitutions), your team sheet and the player of the match;
  • who has said they can or can’t play in a fixture;
  • training and other sessions;
  • your club’s grounds and pitches, and a pitch’s bookings, each saying which match or training session it’s for;
  • your club’s bookings, including which are unpaid and where a refund is owed.

If you ticked Make changes for you, it can also make the changes below. None of them happens in one step: LEKKIN makes your assistant get a preview first, saying in plain words what will change, and only does it once the assistant comes back to confirm. That’s when your assistant should show you, and wait for your yes.

  • record whether a squad player can play in a fixture, or make a training session;
  • book a pitch, only inside the pitch’s available hours;
  • move or cancel a booking. Cancelling a paid booking records a refund as owed. It never refunds anything itself;
  • ask the club for a pitch for a home match, if you’re a manager;
  • add a training session, if you’re a manager.

What it can never do

These simply aren’t available to it, whatever you tick:

  • create or delete clubs or teams;
  • change who has access, or invite or add people;
  • move money: take payments, refund, or mark something paid;
  • change your club’s subscription;
  • send messages of its own to your club’s members. (Adding a session still tells the squad, and asking for a pitch still tells the club, exactly as when you do it in the app.)
  • change your account or your password.

What it sees about people

As little as it needs. Names and squad numbers, who scored and who played in a match, availability answers (not the notes people add to them), and the name on a booking. Never contact details, dates of birth or addresses.

What it reads is sent to the company that runs your assistant (Anthropic, for Claude). The privacy notice says more.

Checking what it did

Everything it does at your club is recorded in your club’s history, as you, via the assistant.

Disconnecting it

At login.lekkin.app, open Account, find Connected assistants, and press Disconnect. It stops straight away.

It also stops:

  • at a club, straight away, if somebody turns that club’s switch off;
  • at a club, if you lose your role there;
  • everywhere, if you reset your password. Every assistant you connected is disconnected.

Switching it on for your club

For club admins.

In the Club Hub, open Configure, then the AI assistants tab. Switch it on there. It’s off until you do. Your club needs the developer platform add-on.

Switching it off stops every assistant at your club straight away. Each person who connected one still only gets what they can do themselves.

Still stuck? Tell us what you were trying to do.