Skip to content
intelliHoops
Join waitlist →
AI connector · MCP

Let your AI run the office, as you

The intelliHoops connector is an official MCP server. Claude, Cowork and Claude Code sign in as a member of your club, read what that person can read, propose changes a person approves, and send only what a person confirms.

The first job: keep Exposure Events in sync

Clubs that play in Exposure Events tournaments retype the operator's schedule into their own calendar on Wednesday, again when it changes on Friday, then the results and the next day's bracket on Saturday night. A wrong time in that retyping — 8 AM on the family calendar for a 1 PM game — is the one mistake a club cannot afford.

With the connector, Cowork reads the operator's schedule page and hands intelliHoops the words on it. The server works out the time zone, which side you are on, which gym and court, and whether the card is a game you already have. What comes back is a review sheet: every new game, every moved time, every score, with a confidence you can read and one click to apply it through the same door a hand entry uses.

Setting it up

  1. Ask intelliHoops to switch the connector on for your club. It is off for every club until then.
  2. In Claude, Cowork or Claude Code, add a custom connector and paste the connector URL below.
  3. Sign in with your intelliHoops account when the app asks, and pick the club. That consent screen is the only place a connection is made.
  4. Open a tournament in intelliHoops, link its Exposure Events schedule page on the Sync tab, and confirm which line on that page is which of your teams.
  5. Paste the one-line prompt from the Sync tab into Cowork. It reads the page and sends what it saw; every proposal lands on the review sheet for your approval.

Connector URL:

https://api.intellihoops.com/mcp
Open settings →

How it stays safe

It signs in as a person

Every connection is one member’s sign-in, in one club, with the permissions that person already has. Nothing an admin cannot do by hand, the AI can do through the connector.

It proposes; a person approves

A sync never writes a game. It files proposals — what it read, what would change, and how sure it is — and the change is applied only when someone clicks Approve on the review sheet, through the same door a hand entry uses.

Confidence is computed, not claimed

The server scores every proposal by rules: did the time carry AM/PM and the right zone, is the venue on file, did the card match a game we already have, were families already sent this day. Anything uncertain, and every cancel, takes its own click.

Sends are previewed, then confirmed

Releasing a schedule or finalizing a day is a two-step call: a preview names every team, what would go out and to how many families; the confirm runs only the previewed arguments, once, within ten minutes.

Every action is on the record

Each tool call is logged. A schedule change made through the connector is stamped as such in the audit trail, with the confirmation it acted on, so “what did the AI do last night” has an answer.

Off by default, off in one click

The connector is switched on per club by intelliHoops. Any member can disconnect their own AI app from Settings; a club admin can disconnect anyone’s; switching the club off stops every connection at once.

What it can do today

Three permissions, chosen when you connect: Read the club,Propose schedule changes for review, andSend schedules to families after a confirmation. Each tool needs one of them.

whoami

Who is signed in, in which club, with which permissions.

Read
list_teams

The club’s teams, with their divisions and seasons.

Read
list_tournaments

Upcoming and recent events, and whether each is linked to an Exposure page.

Read
list_event_games

Every game on one event, as the schedule has it.

Read
list_venues

The club’s venues and courts, so a page’s “Court 4” can be matched.

Read
get_rsvp_summary

Yes / no / maybe / unanswered per team on one event.

Read
get_event_sync_context

Opens a sync run: the linked page, the team maps, the games already on file, and the reading guide.

Propose
submit_sync_observations

Hands over what was read on the page, card by card. The server interprets it and files proposals — it never writes a game.

Propose
preview_team_map / confirm_team_map

Say which line on the page is which of the club’s teams — confirmed once, then remembered.

Propose
preview_stage_action / confirm_stage_action

Release a preliminary schedule, finalize a day, or send an urgent change — previewed with every family it would reach, then confirmed.

Send

For the technically curious

  • • Model Context Protocol over Streamable HTTP, stateless, one endpoint.
  • • OAuth 2.1 with PKCE (S256). Clients identify themselves by a metadata document URL, or register dynamically.
  • • Short-lived access tokens, rotating refresh tokens, revocable from Settings at any time.
  • • Every write tool is a preview-then-confirm pair; a confirmation is single-use and bound to the previewed arguments.
  • • Discovery at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server on the API host.