If you cannot add the Swifteq MCP Server to your AI assistant, or signing in fails, this article explains the most common reasons and how to fix them.
In this Article
1. "Callback URL mismatch"
2. There is no Add Custom Connector Option in Claude
3. "Couldn't reach the MCP server"
4. "Couldn't register" or you are Asked for a Client ID
5. You are Sent Back to the Swifteq Homepage after Signing Up
6. Your Password is Not Accepted
1. "Callback URL mismatch"
The full message is "Callback URL mismatch. The provided redirect_uri is not in the list of allowed callback URLs." This is the most common sign-in problem. It happens when your AI assistant uses a callback URL that is not on our allowed list, usually because a command line tool picked a random port.
What to do:
-
Claude Code: add
--callback-port 8080when adding the server, or set"callbackPort": 8080in.mcp.json. Refer to Connecting Claude to the MCP Server. -
Claude Code, after it was already working: run
/mcp, choose Clear authentication for the server, then sign in again. -
Other command line or desktop clients: set the callback to
http://localhost:8080/oauth/callbackorhttp://localhost:8080/callback. Uselocalhost, not127.0.0.1. - Hosted clients: copy the full address of the error page and email it to support@swifteq.com. We will allow the callback URL it contains.
2. There is no Add Custom Connector Option in Claude
This is a Claude setting, not an MCP Server issue.
- Your Claude plan: custom connectors require a paid Claude plan.
- Your organization's policy: on Team and Enterprise plans, an administrator can turn off custom connectors. Ask your Claude administrator to allow them.
While you wait for an administrator, Claude Code does not use the custom connector option, so it may be a quicker way to connect.
3. "Couldn't reach the MCP server"
- Check the URL is exactly
https://mcp.swifteq.com/api/mcp/sse. - In Claude Code, make sure the transport is
http, notsse. - If it worked earlier the same day, your session may have expired. Sign in at agenthelper.swifteq.com, then reconnect.
- Some AI assistants that only accept a strict SSE connection cannot connect. Contact us with the error your AI assistant shows.
4. "Couldn't register" or you are Asked for a Client ID
Your AI assistant could not register itself automatically. You do not need to create anything in Zendesk.
What to do: Try connecting again. If your AI assistant asks for a Client ID, contact us at support@swifteq.com and we will send it. There is no client secret. Refer to Connecting Other AI Assistants and Custom MCP Clients.
5. You are Sent Back to the Swifteq Homepage after Signing Up
You probably signed up from a page for a different Swifteq app.
What to do: Go to https://agenthelper.swifteq.com/auth/mcpserver. If it still happens, contact us so we can check your account.
6. Your Password is Not Accepted
- Reset your password at https://agenthelper.swifteq.com/auth/login.
- If the password field clears while you type, a browser extension such as a password manager is probably interfering. Turn it off and try again.
If you are still having problems, contact Swifteq support using the Live Chat or email support@swifteq.com, and include which AI assistant you use and the exact error message or a screenshot.