Skip to content
The AI connector: what it is and how a staff uses it

The AI connector: what it is and how a staff uses it

November 16, 2026

The pages on this site are the folder. Spray charts, scouting reports, packets, cards, bullpen sheets, and stat books are already built. You open them, you print them, you hand them to an assistant.

The connector is the conversation. You ask a question in plain English, in Claude, ChatGPT, or Grok, and the answer comes back from this league’s stats. You do not export a spreadsheet first. You do not tell the chat what OPS means. You name the school, you name the player, and you ask the job.

This post is the map: what that connection is, how to turn it on, what it can answer, and how a staff would actually use it on a Thursday night.

What an MCP is

MCP stands for Model Context Protocol. That is a fancy name for a plug. The chat app is good at language. It is not good at inventing your conference’s home-run leader. The plug lets the chat look up the real numbers, then write the answer in the voice you asked for.

Think of it as a graduate assistant who already has the books open. You say, “Who carries the offense at the school we play Friday, and how have our left-handed hitters done against their starter?” A good assistant checks the stats, then talks. Sometimes they answer from memory anyway. The reply is confident, and the schools are not yours. That is when you give more direction: “Use the StatsDawg MCP to answer baseball questions.” Then ask the job again. You are pointing them at the books, not scolding them.

What you need

  • An unexpired Basic plan on this site. That is the same seat as the charts and the game-prep pages.
  • The Connect Claude page in the menu. That is where this site hands your chat app permission to ask questions.
  • One of the chat apps: Claude, ChatGPT, or Grok. You do not install StatsDawg software on the laptop for this. The pages stay in the browser. The questions happen in the chat.

If the plan lapses, the plug stops answering. Renew, then ask again. If a key or a sign-in ever leaks, revoke it on the Connect page and make a new one. Treat that like a password. Do not paste it into a group text.

How to connect

Claude

Claude is the simplest path for most staffs.

  1. Open Claude’s connectors (Customize, then Connectors).
  2. Add a custom connector. Name it for this league, so you never confuse it with the other one. “NAIA baseball” or “D3 baseball,” not just “Stats.”
  3. When it asks how people connect, choose Sign in. Do not choose “no sign in,” and do not paste a key into Claude.
  4. Sign in with the StatsDawg account for this site.
  5. In the conversation, turn the connector on from the plus menu before you ask a stats question.

A team or enterprise Claude plan can add the connector once for the staff. Each coach still signs in with their own StatsDawg account.

First question, so you know it is the right league: “Use the StatsDawg MCP to answer baseball questions. What season is loaded?” If the answer is a guess, say the first sentence again and ask once more.

ChatGPT

ChatGPT also wants a sign-in, not a pasted key.

  1. On the web, open Plugins and add a custom MCP server.
  2. Name it for this league.
  3. Authentication: Sign in, or OAuth. Not “no authentication.”
  4. Sign in with the StatsDawg account for this site.

Grok

Grok’s custom connector has a name and a web address. It does not have a separate box for a password. The Connect page on this site shows you the address to paste. That address is the password. Do not post it, and do not email it to the whole roster.

If a second screen asks you to build an OAuth app, you are in the wrong place. Go back to the address from the Connect page.

How to ask so the answer is about the right player

The connector is literal. A few habits keep it from mixing up two kids with the same last name.

  • Name the school the way the schedule prints it. Centenary (LA) is not Centenary (NJ). Judson (IL) is not another Judson. The parenthetical is part of the name.
  • Name the player and the school together. “A. Smith” is a different person on every roster.
  • If you mean an old year, say the year. “This year” means the season the connector is treating as current. Loaded seasons go back more than one spring. Ask which seasons are loaded if you are not sure.
  • Ask one job, then the next. “Scout their Friday starter, then tell me who on our bench hits left-handed pitching” works better than a paragraph with six requests buried in it.
  • If the answer is smooth and the names are wrong, or there are no names at all, stop. Say, “Use the StatsDawg MCP to answer baseball questions.” Then ask again. A good assistant still needs a nudge.
  • A short sample is not a tendency. If the answer says the split is thin, do not put it on the card. Fifteen plate appearances is a start of a conversation, not a scouting report.
  • The everyday nine is who plays, ranked by games started. It is not the batting order. If you need the order from a specific game, ask who came up in that game, on that date.

You can ask it to write the answer as a dugout card, a text to an assistant, or a paragraph for the pregame meeting. The numbers should stay the numbers. The voice is up to you.

What you can ask

You do not need to learn tool names. Ask the question. This is the ground the connector covers, grouped the way a staff actually works.

The roster and the season

  • What season is loaded, and which earlier seasons can I ask about?
  • Find this school. Find this player on this school.
  • Give me the official season line for a hitter or a pitcher. That line is the school stat sheet.
  • Show me that same player in every season we have, at this school. Do not blend a kid who transferred and shares a name.
  • Team report: offense, pitching, record, and who to know.
  • Leaderboards for a conference or one roster. Hitting: average, on-base, slugging, OPS, home runs, RBI, steals, hits. Pitching: ERA, WHIP, strikeouts per nine, walks per nine, strikeouts, saves, innings, wins. Ask for a cutoff if you want the rate list to mean something. Thirty plate appearances and ten innings are sensible floors. Say a higher bar if you are ranking the league.

The opponent, before you play them

  • Everyday nine, rotation, closer, and bullpen. Again: the nine is games started, not the card they will turn in.
  • A series packet: their record, who carries the club, and how your own players have done against them. You have to name both schools.
  • Win chance and expected runs for your club against that opponent. This is a scouting card. It is not a betting line.
  • Schedule, with scores, and the games still blank if the log has them.
  • Where the team puts the ball in play: left, center, right, and ground balls. Left and right are the field, from the plate looking out. They are not “pull” and “opposite.”
  • How deep their starters go, and when the bullpen usually enters.
  • Who on their bench has a bat worth a pinch-hit look. That list is the hitters who are not everyday starters and still have a real sample.
  • How the club hits left-handed pitching versus right-handed pitching, as a team or for one player.
  • Head-to-head between two schools: who was batting, who they faced, and what the games looked like.

One player, in detail

  • Write a scouting report. You get a fresh report in the reply, built for that player, not a canned paragraph from last month.
  • Spray, as percentages, and the picture: all hits, hard hits, ground balls, soft hits, outs, reached safely, versus left, versus right, or the weather map. Ask for the image when you want the image. Ask for the percentages when you want the table.
  • Recent form: the last several games, from the games themselves, not from the season line. Ten games is a window. Do not treat it as the year.
  • How a hitter does with the bases empty, with runners on, and with runners in scoring position. Scoring position means a runner on second or third. A thin sample is not a label.
  • Other situations: bases loaded, runner on third, two outs.
  • Which opponents a player has struggled against, and what those clubs’ records were. Conference versus non-conference is in the same answer.
  • One of your hitters against one of their pitchers, this year or across the seasons we have. Under a real sample, it is a note. It is not a career verdict.

Your own staff and your own week

  • Bullpen rest: last outing, days since, innings in the last two and three appearances.
  • Who carries your offense, and who carries the staff. That share is not WAR. It is who has produced the runs and the innings.
  • Record splits: home and road, one-run games and blowouts, games you scored a bunch, games you barely allowed anything, the last ten, the streak.
  • How many games the run differential says you should have won, and whether you are a few ahead or a few behind that. A few games is noise. It is not proof of clutch, and it is not proof the bullpen is cursed.
  • Schedule strength, and the same luck check beside it.
  • Runners left on base, for the club, including the ones stranded in scoring position. That belongs to the inning, not to one hitter. Do not pin the LOB on the number-eight hitter because he made the last out.
  • When you score: which innings the runs show up in.
  • Fielding line from the stat sheet: chances, errors, fielding percentage. Compare players who do similar work. A catcher and a left fielder do not field the same number of balls.

After the game

  • Who played on a date: hitters in the order they came up, pitchers in the order they entered, starter marked.
  • Every batter one pitcher faced in that game, with the inning and the result.
  • Replay the game. Ask for the story, not a dump of every pitch. The connector has the plays. The chat can tell it like a newspaper lede if you ask it to.
  • The swings that changed the win chance the most. Those are the plays that mattered, not every single.

Conference and evaluation boards

  • Conference race: winning percentage, run differential, and whether each club is ahead of or behind the record its runs suggest.
  • Rank a conference by how teams hit with runners in scoring position.
  • Hitting value that puts a player next to the league, not just next to his own average. On-base, power, and a run-weighted line where 100 is average for this league, this season. Ask for a plate-appearance floor.
  • Pitching value the same way: strikeouts, walks, WHIP, and a run-prevention line scaled so 100 is average here, not in the big leagues.
  • Run value of a hitter’s plate appearances, when you want more than the box-score line.
  • Park factors: which home parks have been producing more runs than a neutral park in this league. That is measured from the games played there. It is not a tape-measure of the fences.

Derived numbers are fit to this league and this season. A 100 is average among the clubs in this connector, not a major-league average pasted onto a college Saturday. If you quote one in a meeting, say it that way.

Friday game prep

You play somebody Friday. The pages already have the packet and the cards. The connector is for the questions the packet does not answer in one click.

The examples start with the nudge, because that is the habit. “Use the StatsDawg MCP to answer baseball questions.” You do not have to say it every time the assistant is already in the books. You say it when they start freelancing, and you can say it again on the next question if the first nudge did not stick.

Start with the schools named in full.

Use the StatsDawg MCP to answer baseball questions. We are [your school]. Friday we play [their school]. Give me their everyday nine, their rotation, their closer, and who carries the offense. Then tell me our win chance and expected runs against them. This is a scouting note, not a betting line.

Then the starter you actually expect.

Use the StatsDawg MCP to answer baseball questions. How deep does their Friday starter usually go? When does the bullpen usually enter? Who on their staff has thrown the last two times out, and how many days of rest does each arm have?

Then your own pen, because availability is your problem, not theirs.

Use the StatsDawg MCP to answer baseball questions. For [your school], who is rested? Last outing, days of rest, and innings over the last two and three appearances. Write it as a list I can read to the pitching coach.

Then one matchup you care about.

Use the StatsDawg MCP to answer baseball questions. How has [your hitter] at [your school] done against [their pitcher] at [their school]? If the sample is thin, say so and do not call it a tendency.

If you want the picture for the meeting, ask for the spray chart image of their three middle hitters, all hits and ground balls. Pin those. Do not ask the chat to draw a field from memory.

Scouting a hitter

A transfer visit, a conference rival, or the kid who beat you twice. Same shape every time.

Use the StatsDawg MCP to answer baseball questions. Write a scouting report on [player] at [school]. Include the season line, the spray, how he does with runners in scoring position, and how he has done against left-handed pitching. If any split is under 15 plate appearances, leave it off the card.

Follow-ups that are worth a second question, not a footnote:

  • Last 10 games, and do not blend that into the season line.
  • Which clubs he has struggled against, and what those clubs’ records were.
  • Year by year at this school only.
  • The weather map, so the catcher can see the season in one picture.

Ask for the report as six lines a coach can text. Then ask for the same report as a paragraph for the hitters’ meeting. Same facts. Different room.

Scouting a pitcher

Use the StatsDawg MCP to answer baseball questions. Scout [pitcher] at [school]. Season line, how deep he goes when he starts, where he is hit, and how he has done against left-handed hitters versus right-handed hitters. Compare his ERA and his strikeout and walk rates to the league, where 100 is average here.

Then the usage question, which is the one that changes Friday:

Use the StatsDawg MCP to answer baseball questions. Is he a starter or a reliever in the games we can see? Last three outings: date, innings, and days between them.

If you are preparing your own hitters, ask which of your bats have seen him, and stop there if the list is a handful of at-bats.

Player evaluation

Evaluation is where coaches over-read a hot month. Ask for the season, the prior season, and the league, in that order.

Use the StatsDawg MCP to answer baseball questions. I am evaluating [player] at [school] for a role next year. Season line this year and last year, at this school only. Then place him on the conference hitting board with a real plate-appearance cutoff. Tell me if he is a regular, a bench bat, or a small sample. Who else on his own roster carries more of the offense?

For a pitcher you might start, or might move to the bullpen:

Use the StatsDawg MCP to answer baseball questions. Evaluate [pitcher] at [school]. Innings, ERA, strikeouts, walks, and how that compares with the league. How deep does he go when he starts? Has the role changed from last season to this one?

For your own midweek meeting, the useful question is contribution, not a highlight.

Use the StatsDawg MCP to answer baseball questions. Who carries our offense, and who is on the bench with enough at-bats to be a pinch-hit option? Separate the everyday nine from the rest. Do not call the nine a batting order.

If you are arguing about a park, ask whether home games at your place have been a high-run environment or a low one, compared with the rest of this league. Then stop. Fences are not in the answer.

A Monday after a loss

Use the StatsDawg MCP to answer baseball questions. Replay [your school] on [date]. Tell it as a short game story. Name the starter, the go-ahead run, and the inning we left the most runners on. Then list the two or three plays that changed the win chance the most.

If it was a doubleheader, say which game. Then ask who your starter faced, in order. That is the film session without the film.

The conference race

Use the StatsDawg MCP to answer baseball questions. Standings for [conference], with run differential and whether each team is ahead of or behind the record its runs suggest. Then the home-run leader and the ERA leader in that conference, with a real cutoff. Then which of those clubs hit best with runners in scoring position.

Use the luck line the way you would use a weather report. It tells you the week has been strange. It does not tell you to change the bunt sign.

What to keep in the meeting, and what to leave in the chat

  • Keep the everyday nine, the starter’s recent innings, the one matchup with a real sample, and the spray picture.
  • Leave a 6-for-12 split in the chat. Say “small sample” out loud if a player asks.
  • Do not read a win-probability number as a betting line. It is a way to compare two clubs’ seasons.
  • Do not let the connector pick the lineup. It can tell you who has hit. You still write the card.
  • If two schools come back for one name, stop and pick. Do not let it choose the first one on the list.

Pages and questions, side by side

Use the menu when you want the same artifact every week. Packet, cards, bullpen sheet, stat book, series preview. Those do not require a chat.

Use the connector when the question is specific. One hitter against one pitcher. Last outing for your own pen. The replay of Saturday. A conference board with a cutoff you name. A report written as a text, not as a PDF.

Both sit on the Basic plan. Connect Claude is in the menu. Sign in, ask what season is loaded, and then ask about the school you play next.