If your AI assistant regularly asks you to reconnect the Swifteq MCP Server, or reports that the connection is closed, this article explains why and what you can do.
In this Article
Why you Need to Sign in Again
Reconnecting
Scheduled and Unattended Work
When it is Not Expected
Why you Need to Sign in Again
The MCP Server connection uses a sign-in session that expires after a period of time. Sessions usually last one to two days, and up to about seven days, depending on your AI assistant. When the session expires, you may see messages such as "connection closed" or "no longer connected", or the connector stops responding.
This is expected. The session length cannot currently be changed, and there is no API key or long-lived token you can use instead. A longer or configurable session is one of our most requested improvements.
Reconnecting
- Sign in at agenthelper.swifteq.com.
- In your AI assistant, open the connector settings and click Connect for the MCP Server. In Claude Code, run
/mcpand select the server. - Start a new chat.
Scheduled and Unattended Work
If you run weekly reports or other scheduled work through your AI assistant, the session has often expired by the time the job runs. Plan to reconnect before each run.
When it is Not Expected
If the connection drops several times a day, or in the middle of a session you just started, that is not expected. Refer also to The MCP Server Cannot Access Zendesk - Common Causes and How to Fix Them.
If the problem continues, contact Swifteq support using the Live Chat or email support@swifteq.com, and include which AI assistant you use and when the connection dropped.