Connect an MCP client

Add SailSync to your assistant, sign in and approve the requested permissions. Hosted MCP needs no token download or Node installation.

https://www.sailsync.io/mcp

Cursor

Add SailSync to Cursor, confirm the server, then connect through SailSync sign-in. The install link contains only the server URL.

Claude

In Customize → Connectors, choose + Add → Add custom connector. Name it SailSync, enter the URL above and follow the sign-in prompts. Enable it in your conversation’s connectors menu.

See Claude’s connector guide for plan availability and team setup.

Other remote clients

Add the URL above as a remote MCP server, then sign in to SailSync when prompted. Your client must support Streamable HTTP and OAuth.

Review the permissions before connecting. You can revoke access anytime in API & agent connections.

Try it

Read my SailSync account, list my sessions and show the tracks in a session I choose. Use read-only tools.

The tool sequence is getSailSyncAccount → listOwnedSailSyncSessions → getOwnedSailSyncSession. Try the agent recipes next.

Local alternative

Requires Node.js 22+ and a client that can launch local processes.

1. Create a read-only personal token.
2. Add this server configuration:

{
  "mcpServers": {
    "sailsync": {
      "command": "npx",
      "args": ["-y", "@sailsync/mcp@0.6.4"]
    }
  }
}

3. Set SAILSYNC_API_TOKEN through your client’s secret environment settings, then reconnect. Keep tokens out of shared configuration files.

For a standalone fallback, download the local bridge from the connections page. Use node as the command and the absolute path to sailsync-mcp.cjs as its argument. Download a fresh copy after updates.

Operation IDs in the reference are the MCP tool names.