{
  "schema_version": 1,
  "connector_name": "PairSync",
  "server_url": "https://mcp.pair-sync.com/mcp",
  "transport": "Streamable HTTP",
  "api_key": {
    "source": "PairSync Terminal > Settings > API Access",
    "placeholder": "psk_live_YOUR_KEY",
    "reusable_across_clients": true,
    "limits": "Connections using the same key share its usage allowance and rate limits.",
    "rotation": "Rotating or revoking the key affects every connection using it."
  },
  "authentication": {
    "oauth": {
      "use_when": "The client supports OAuth and opens the PairSync approval popup, for example Grok in a browser.",
      "connector_fields": {
        "Name": "PairSync",
        "Server URL": "https://mcp.pair-sync.com/mcp",
        "Headers": {}
      },
      "steps": [
        "Choose OAuth if the client asks for an authentication method. Leave custom Headers empty.",
        "Start the connection from the AI client. On mcp.pair-sync.com, paste your existing PairSync key into PairSync API key, then click Approve connection.",
        "Return to the original client and run the verification prompt. Do not put the key in an OAuth Client ID or Client Secret field."
      ]
    },
    "api_key_header": {
      "use_when": "The client supports custom HTTP headers, including desktop apps with a Headers section.",
      "connector_fields": {
        "Name": "PairSync",
        "Server URL": "https://mcp.pair-sync.com/mcp",
        "Headers": {
          "X-Api-Key": "psk_live_YOUR_KEY"
        }
      },
      "steps": [
        "Choose API key or custom headers instead of OAuth, if an authentication selector is offered.",
        "Under Headers, enter X-Api-Key in Key (sometimes called Name). This is a header name, not the connector name or a second API key.",
        "In Value, paste your existing PairSync API key beginning psk_live_. Do not add quotes or a Bearer prefix.",
        "Save or connect, then run the verification prompt. This method does not need the PairSync approval popup."
      ]
    }
  },
  "verification": {
    "prompt": "Get the latest PairSync refit metadata for US.",
    "tool": "get_latest_refit_metadata",
    "arguments": {
      "market": "US"
    },
    "success": "The tool returns US refit metadata, including a refit date. A saved connector alone is not proof of access.",
    "usage": "The verification tool call counts toward your allowance."
  },
  "troubleshooting": [
    {
      "problem": "Already a connector",
      "action": "Check the existing connector instead of adding a duplicate. This message does not mean the API key can only connect one app. Do not remove a working browser connector as your first fix."
    },
    {
      "problem": "Reconnect fails or Failed to load connector",
      "action": "Check the exact server URL and selected authentication method. If browser OAuth works but desktop approval fails, fully quit and reopen the desktop app, check the account, then try header authentication if supported. Capture the exact error with all secrets hidden if it still fails."
    },
    {
      "problem": "Approval popup does not return to the client",
      "action": "Start a fresh connection from the original client and complete its popup in the signed-in browser profile. Do not copy an old approval URL into another browser. Alternatively use headers if supported."
    },
    {
      "problem": "Key rejected",
      "action": "Check the current key under Settings > API Access. Remove extra spaces and confirm it has not been rotated or revoked. Your Terminal password is not an API key."
    }
  ],
  "assistant_safety": [
    "Use one authentication method per connection, not both.",
    "Keep real keys in the client's local credential fields or supported secret store. Never ask the user to paste keys or passwords into an AI conversation or public example.",
    "This public document contains placeholders only and grants no access.",
    "MCP client connectivity does not establish native Bot installation, shared sessions, persistence, or background access."
  ]
}
