MCP server and AI apps
Environments, URLs and client IDs
Which MCP server addresses and Auth0 client IDs exist per environment, and which are live.
Environments, URLs and client IDs
Each environment has its own MCP address, Auth0 tenant and app registrations. Never mix values across environments.
Server addresses
| Environment | MCP server URL | State |
|---|---|---|
| Test | https://platform-test.hockeystickai.com/mcp | Live. The published Claude plugin and the client guide point here. |
| Staging | https://platform-staging.hockeystickai.com/mcp | Auth0 resource and OBO service configured; MCP not switched on. |
| Production | Not yet published | Production tenant created but not provisioned. Give clients the production address only once engineering confirms it. |
Opening the server URL in a browser returns "Authentication required". That is expected. Discovery lives at /.well-known/oauth-protected-resource/mcp on the same host.
Auth0 tenants
| Environment | Tenant |
|---|---|
| Test | dev-07y57ax5d1ykwfj7.au.auth0.com |
| Staging | hockeystickai-staging.au.auth0.com |
| Production | hockeystickai-production (created, not provisioned) |
Test app registrations
| App | Identification | Local callback port |
|---|---|---|
| claude.ai and Claude Desktop | URL only. Claude presents its published identity (CIMD) https://claude.ai/oauth/mcp-oauth-client-metadata. Older connectors using 59vuHN6HW46UVMfl4LoraKzVGM7A9fjz keep working. | Hosted callback |
| Codex, CLI and desktop app | 59vuHN6HW46UVMfl4LoraKzVGM7A9fjz | 6279 |
| Claude Code | IxdjXczduq9i5KVpN9X5dLG1Ts5UmdNd, shipped in the plugin | 6278 |
| MCP Inspector, internal testing only | navOV48W8W40Z9pzDuze7xuJeR9wNqzm | 6276 |
All are public clients with no secret. The retired Codex ID ZIWvJlBMqqFfgFAGCDiVYmXoLLiuoGDw must never be reused.
The Claude plugin
The marketplace CrewAmp/hockeystick-plugins holds one plugin, hockeystick, for claude.ai, Claude Desktop and Claude Code. It carries the Test URL, the Claude Code client ID, port 6278 and the scopes hsai.read hsai.write. Production will get its own plugin entry with a different server name when the production server is live.
Scopes
There are two: hsai.read and hsai.write. Each environment has a scope ceiling. Test allows both. Tools above the ceiling are hidden and refused.