| Symptom | What to do |
|---|---|
| The app cannot reach FIRCY | Confirm the URL is exactly https://mcp.fircy.com/mcp. Confirm AI connections are enabled for your organisation. If it persists, contact support. |
| The app asks for an API key or client secret | Check that you selected the remote MCP connection with OAuth. Personal connections use browser sign-in. |
| Sign-in returns to the wrong browser or expires | Restart Connect from the AI app and complete the steps in the same browser. Do not share sign-in links. |
| Access was approved but nothing happens | Return to the AI app and enable FIRCY for the conversation. Ask it to check the connection. |
| There are no results | Check the requested time range and whether your organisation has matching data. An empty result is valid. |
| A tool is missing | Check the permissions you approved and currently hold. Additional read access may require your organisation administrator. |
| You must reconnect | The connection may have expired, been revoked or lost permissions. Restart Connect and approve current access. |
| Verification is temporarily unavailable | Wait briefly and retry. An infrastructure or identity-provider problem does not require a new API key. |
| Your organisation has disabled connections | Ask your FIRCY organisation administrator about its policy. |
What to send support
Include the AI app and version, the approximate time with time zone, the failed step, and the error text. You can include a screenshot after removing customer data.
Never send passwords, API keys, access or refresh tokens, authorisation codes, sign-in links, or a browser session export. Contact support.
Existing integrations
These guides cover personal connections from AI apps. For API-key access, see the API documentation in the FIRCY portal.