Connect Claude, Cursor, or Grok

This MCP setup guide connects an AI agent to your flight school in Sky Schedule. A school admin creates the connection in Sky Schedule once, then adds it to Claude, Claude Desktop, Cursor, or Grok. Each client needs the same two things: the server URL and your school's API key.

Before you start

• You need to be an admin of the school.
• The MCP server and the REST API share one key per school. If your school already uses the REST API, connecting an agent uses that same key. Rotating it to see the full key again breaks your REST scripts until you update them. See API authentication.
• If your school doesn't have API access on its plan yet, Connect opens checkout first.

Step 1: Get your connection details from Sky Schedule

1. Sign in at https://app.skyschedule.io as an admin.
2. Open Settings and choose Integrations.
3. Click the Connect with your agent card below the list of integrations.
4. Click Connect. Sky Schedule creates the school's API key and copies setup text to your clipboard: the Claude steps plus a JSON config for Cursor and Grok. If the school already has a key, there is no Connect button; the panel opens on the connection details instead.

The panel then shows three sections you can expand any time:

• Connection details: the endpoint, the API key, and the daily write limit.
• Claude cloud, Custom connector: the exact values to type into Claude.
• Grok Bot / Cursor, JSON config: the JSON to paste.

Copy for LLM copies all of it again. The full key only shows in the browser where it was created. On another device the panel asks you to rotate, which issues a new key and turns off the old one.

The JSON config looks like this, with your key in place of the placeholder:

{
  "mcpServers": {
    "sky-schedule": {
      "type": "http",
      "url": "https://app.skyschedule.io/api/mcp",
      "headers": {
        "Authorization": "Bearer ss_live_YOUR_API_KEY"
      }
    }
  }
}

Step 2: Add Sky Schedule to your client

Claude on the web (claude.ai)

Claude uses a custom connector, not the JSON config.

1. In Claude, open Customize, then Connectors.
2. Click +, then Add custom connector.
3. Name: Sky Schedule
4. MCP server URL: https://app.skyschedule.io/api/mcp
5. Authentication: No sign-in
6. Under request headers, add a header named Authorization with the value Bearer ss_live_YOUR_API_KEY.
7. Click Add.

Don't paste the JSON config into the URL field, and don't pick an OAuth option. The server uses your school's key, not a sign-in. On a Claude Team or Enterprise plan, an owner may need to add custom connectors for the organization.

To test it, start a new chat and ask: "Using Sky Schedule, list tomorrow's reservations."

Claude Desktop

Claude Desktop uses the same custom connector. In the desktop app, open Customize, then Connectors, and follow the same steps as Claude on the web.

Cursor

1. Open (or create) ~/.cursor/mcp.json to use Sky Schedule in every project, or .cursor/mcp.json inside one project.
2. Paste the JSON config from Step 1. If the file already lists other servers, add the "sky-schedule" entry inside the existing mcpServers object.
3. Save the file, then check Cursor's MCP settings to confirm sky-schedule is enabled and shows its tools.

If you use a project file, add .cursor/mcp.json to .gitignore so the key never lands in your repository.

Grok

Add Sky Schedule as a custom MCP server in Grok and paste the JSON config from Step 1. If Grok asks for fields instead of JSON, enter the server URL and add the Authorization header with Bearer ss_live_YOUR_API_KEY.

Other MCP clients

Any client that supports remote Streamable HTTP servers with custom headers can connect. Use the server URL and send the key in Authorization: Bearer ... or X-SkySchedule-API-Key. Clients that read the server's protected resource metadata will see that it expects a bearer header and has no OAuth server. Details are in the MCP server overview.

Rotate or disconnect

• Rotate in Connect with your agent issues a new key and turns off the old one right away. Update every client and every REST script that used it.
• Disconnect removes the key. Connected agents and REST scripts both stop working until you connect again.

Troubleshooting