Generate a Model Context Protocol URL you can paste into Claude,
ChatGPT, Cursor and other MCP clients. Sign-in goes through your
real Halo login, and your tokens are saved only in the AI client —
the server is a reverse proxy with no backend storage.
1Halo URL2Register app3Client ID4Connect
What's your HaloPSA URL?
The base URL of your Halo instance, e.g. https://halo.yourcompany.com.
1Halo URL2Register app3Client ID4Connect
Register a Halo Connect application
In your Halo instance, go to
Configuration → Integrations → API and click
New. Configure as follows:
Application Name:MCP for AI assistants
(anything you like)
Authentication Method:Authorization Code (PKCE)
Allowed Logins: check
Allow Agent Logins. Leave the others unchecked.
Redirect URI:
https://tools.iusehalo.com/auth/callback
This is the universal callback for every iusehalo tool —
Outlook, MCP and any future ones. Register once and never
touch this list again.
Permissions / Scopes: pick one below and grant the
same scope on the Connect app — they must match or sign-in fails.
The signed-in agent's own Halo permissions always apply on top, so
the assistant can never do more than that user can — regardless of
scope. And in Claude, every tool has its own approval control, so
you stay in charge of each individual action.
Save the application, then copy the generated
Client ID for the next step.
CORS isn't required for MCP. The MCP server
handles token exchange server-to-server, so the Halo Connect
CORS whitelist can stay empty unless you also run the Outlook
add-in (which needs https://tools.iusehalo.com).
1Halo URL2Register app3Client ID4Connect
Paste the Client ID
From the API application you just registered.
1Halo URL2Register app3Client ID4Connect
Your MCP URL is ready. Paste it into any MCP
client. The first time you connect, you'll be sent through your
Halo login.
MCP connector support varies by ChatGPT plan and is rolling out
gradually — if you don't see the option, your account may not
have it enabled yet.
Any MCP client that supports HTTP transport with OAuth 2.0
(Streamable HTTP, MCP spec 2025-03-26 or later) can use this
URL directly. Discovery is via the standard
.well-known/oauth-protected-resource +
.well-known/oauth-authorization-server at the URL
above.
Halo Tools
· MCP server setup