This looks like a remote custom connector issue with https://airfield.directory/mcp on the macOS desktop app.

Please try these quick checks first:

Confirm the MCP Server URL starts with https:// exactly as entered.
Remove and re-add the connector from a fresh app session.
If the connector uses OAuth or API key auth, re-authenticate after adding it.
If you control the MCP server, validate its MCP responses with the MCP Inspector tool, especially the tools/list JSON-RPC response. Perplexity expects a valid response with an id field and a tools array.

Hat wer geschafft den MCP-Server in Perpelxity zu verbinden?