This article is for connecting AI assistants other than Claude and ChatGPT to the Swifteq MCP Server for Zendesk, including developer tools, agent platforms and your own internal AI tools.
Any client that supports MCP with OAuth can work with the MCP Server, as long as its sign-in callback URL is on our allowed list.
In this Article
Connection Details
Callback URLs
Notes for Specific Clients
If you are Building your Own Client
Connection Details
-
MCP Server URL:
https://mcp.swifteq.com/api/mcp/mcp. If your client is already set up withhttps://mcp.swifteq.com/api/mcp/sse, that URL keeps working. - Transport: Streamable HTTP. Every request is an HTTP POST answered with a single JSON response. The server does not open a server-sent events stream and does not use sessions.
- Authentication: OAuth 2.0 authorization code flow with PKCE (S256).
-
OAuth Client ID:
pglNl9dRatAnsoaxZzc76aKwH8NDffAg. Most clients register themselves automatically and do not need it. Enter it only if your client asks for a Client ID. - Client secret: none. The MCP Server uses a public client, so leave any client secret field empty.
-
Authorization URL:
https://auth.swifteq.com/authorize -
Token URL:
https://auth.swifteq.com/oauth/token -
Scopes:
openid profile email offline_access
Clients that support automatic discovery can read these values from https://mcp.swifteq.com/.well-known/oauth-authorization-server.
There is nothing to create in Zendesk and no OAuth app to register.
/api/mcp/register, skip automatic registration and enter the Client ID above in your client's settings instead.Callback URLs
At the end of sign-in, the MCP Server sends you back to your client's callback URL. The URL must match an allowed URL exactly, including the host, port and path.
-
Desktop and command line clients: use
http://localhost:8080/oauth/callbackorhttp://localhost:8080/callback. These are already allowed. Uselocalhost, not127.0.0.1. - Hosted clients such as agent platforms and internal tools: email the full callback URL to support@swifteq.com and we will add it. This is usually done the same day.
If sign-in fails with "Callback URL mismatch", copy the full address of the error page and send it to us. It contains the callback URL that needs to be allowed.
Notes for Specific Clients
| Client | Note |
|---|---|
| Microsoft Copilot Studio | Use the built-in MCP wizard with OAuth 2.0 dynamic discovery and no client secret. Do not create a custom connector, as that path requires a client secret and fails. |
| VS Code and GitHub Copilot | Enter the Client ID from Connection Details in mcp.json. The callback URLs 127.0.0.1:33418 and https://vscode.dev/redirect are already allowed. |
| Cursor | Cursor uses its own callback port. Send us the callback URL from the error message and we will allow it. |
| n8n, LibreChat, Guru and similar platforms | Work once we have allowed their callback URL. |
For the full list of supported and unsupported AI assistants, refer to Requirements and Supported AI Assistants for the MCP Server.
If you are Building your Own Client
Use one fixed callback URL for all your deployments and ask us to allow that URL. The registration endpoint accepts the callback URLs you send, but it does not add them to the allowed list, so a different callback URL for each customer or deployment will not work.
If you need help, please contact Swifteq support using the Live Chat or email support@swifteq.com.