SailSync MCP & API
A sailing data layer for your AI agents
Connect your AI assistant to your team’s sailing sessions and a full collection of accessible public racing data. Use SailSync’s MCP tools or HTTP API to upload recordings, review race data, find trends across regattas, and turn the evidence into coaching plans and team stories.
Public tracking opens up new possibilities for competitive analysis. Have your agent study competitors across regattas, compare performance and race execution, and uncover patterns across the fleet—with the underlying race data to support its findings.
Rate-limited API/MCP support on Standard. MCP/API support on Racer and Gold.
Start with the question you want answered
Your agent gathers the permitted data, performs the comparisons, and drafts something your team can use. These are example briefs for a connected agent; cross-session analysis and storytelling happen in your agent’s workflow, using SailSync as the source of sailing data.
Build a picture of the competition
“What can public tracking tell us about our competitors’ strengths, patterns and progress across regattas?”
Have an agent gather accessible public racing data across events and compare competitors’ starts, leg speed, VMG, maneuvers and results. It can look for recurring strengths, course choices and gains or losses, then build a scouting brief with race references and questions for your coach. Public tracking makes this evidence available; an agent helps turn a collection of races into competitive analysis that would be difficult to assemble manually.
Track progress across regattas
“Which of our team’s sailors are improving from regatta to regatta?”
Have an agent match your sailors to their tracks, gather accessible event days, and compare saved results, starts and leg performance over time. It can build a progress summary with links to the sessions, accounting for fleet and conditions rather than treating every finishing place as directly comparable.
Separate boat speed from race execution
“Who has boat speed comparable to the leaders but is still losing places?”
Ask an agent to compare speed and VMG on similar legs, then examine start statistics, tracks, maneuvers and race outcomes. It can identify where to investigate tactics or execution and prepare questions for a coaching debrief. GPS and results provide evidence; tactical explanations still need context and coach review.
Turn patterns into a practice plan
“What does the team need to work on next?”
Bring several training sessions and regattas into one review. An agent can look for recurring start, speed or maneuver patterns, separate individual needs from team trends, and draft practice priorities with examples from the data.
Build a story for supporters
“Which sailors’ progress should we feature on social media, and what story can we tell donors from their results?”
Ask an agent to find improvement arcs, breakthrough races and consistent performances, then draft a shortlist of stories with supporting results and session links. Combine that evidence with the coach’s knowledge of each sailor to prepare social posts or donor updates for review.
Prepare a team’s session uploads
“Can you organize these GPS files into sessions and get them ready for our debrief?”
An agent with file-processing tools can inspect raw recordings, flag data issues and normalize supported source data into SailSync’s CSV import format. With write permission, it can create named sessions with a boat class, time window and timezone, upload tracks and measured wind, and request recalculation of finished sessions. Race setup assistance can be requested from SailSync staff.
From recordings to a team decision
- Gather and prepare. Find owned sessions and accessible event days, or prepare raw recordings and import them into new sessions with write permission.
- Compare with context. Match sailors, retrieve GPS and available saved analytics, and compare similar boat classes, wind conditions and race segments. Flag missing data.
- Make it useful. Draft a debrief, training plan, progress report, social post or donor story with supporting results and session references.
- Review and act. Have a coach review conclusions and story selections. Save notes in your team’s own tools, and use permitted SailSync writes for imports and recalculation.
What agents can access and manage today
- Sessions and GPS tracks
- Discover sessions you own, identify their tracks, and download full-resolution recorded GPS positions within the session window.
- Public event discovery and permitted event data
- Browse public events and their day and fleet assignments, then read session data using your account’s existing event access. An agent can work across a collection of accessible regattas.
- Saved sailing analytics
- Read configured wind, saved race results, start statistics and available per-leg speed, VMG, distance, timing and maneuver comparisons. Agents can use these records and GPS to calculate their own comparisons and trends.
- Session creation and imports
- Create sessions you own, import normalized CSV tracks and measured wind, request staff help with race setup, and follow import receipts. Existing wind replacement requires explicit consent.
- Recalculation and FLO conversations
- With the relevant permissions, request recalculation of a finished session you own or ask FLO about a session. Check job status and retrieve FLO answers, citations and credit usage.
Imports do not automatically recalculate analysis. Race setup is not fully automated, and reading saved results does not generate a new report. See the import and compute guide and API reference for supported operations and current limits.
MCP and API questions
What is SailSync MCP support?
SailSync provides a local Model Context Protocol (MCP) bridge that lets compatible AI clients use its sailing data and session tools. The HTTP API gives scripts and custom applications access to the same documented operations. Standard includes rate-limited API/MCP support; Racer and Gold include MCP/API support. Operations remain subject to account access, token permissions and available features.
Can I connect my own AI agent?
Yes. Connect a compatible AI agent through SailSync’s local MCP bridge or HTTP API to explore your sessions, find trends and build your own sailing coach. Your connection uses your account’s data access and token permissions. Questions? Reach out to jeff@sailsync.ai.
Can I build my own frontend to visualize my sessions?
Yes. Let SailSync be your backend and build your favorite frontend on top of it. Use the API to visualize your sessions, GPS tracks and available race analysis in your own dashboards and debrief tools. Questions? Reach out to jeff@sailsync.ai.
Can an agent analyze a team across multiple public regattas?
Yes. An agent can discover public events and read the event sessions and saved analysis your account is permitted to access. It can combine that data into cross-regatta comparisons. You may need to confirm sailor identities across boat names and sail numbers; public event discovery does not grant unrestricted access to every event’s data.
Can an agent clean up files and add coaching notes?
An agent with local file tools can inspect and clean source data before importing a normalized CSV into an owned session. It can also draft coaching notes, trend reports and stories in your own documents or connected tools. The current SailSync API cannot save session notes or lineup comments, change track trims, or edit existing GPS points in place.
How do I connect an AI assistant to SailSync?
Create a named personal integration token in SailSync’s API & agent connections page, download the local MCP bridge, and configure a compatible client that can launch a local Node.js process. Put the token in the client’s secret environment. Hosted remote MCP and OAuth are not currently available.
Which permissions and credits do agent workflows use?
Read access uses your existing account permissions. Session creation and imports, recalculation, and FLO each require explicit opt-in token permissions and feature availability. Read-only requests do not spend report allowance or FLO credits. FLO conversations use your account’s FLO credits. Check your connection’s account response for enabled capabilities.
Let SailSync be your backend
Build your favorite frontend or your own sailing coach on top of SailSync. Questions? Reach out to jeff@sailsync.ai.
Start with a read-only token and your own sessions. Add write or FLO permissions when your workflow needs them. The developer portal has setup instructions, agent recipes and a walkthrough using real ILCA Worlds event data.