Troubleshoot HERE Location Reasoning
Resolve common problems connecting to HERE Location Reasoning, authenticating, and calling tools. Match the symptom to its likely cause, then follow the recommended solution.
Troubleshoot MCP client issues
Troubleshoot issues encountered when signing in through an MCP client or making tool calls.
| Issue | Root cause | Solution |
|---|---|---|
| Sign-in succeeds but tool calls fail | The account you authorized is not provisioned for HERE Location Reasoning. | Sign in with an account that is provisioned, or ask the owner of your subscription to invite you to their organization. |
| The sign-in window does not open | The browser blocked the pop-up. | Allow pop-ups for your client, then reconnect to trigger sign-in again. |
Troubleshoot issues with M2M credentials
Diagnose token-generation and MCP-session issues when authenticating with machine-to-machine credentials.
| Issue | Root cause | Solution |
|---|---|---|
invalid_client on token request | The client_id is not the APP ID, or the JWK was registered for another application. | Use the APP ID as client_id and confirm the application is active. |
| Signature or key error on token request | The JWT kid does not match the registered KEY ID, or private-key.pem is not the pair of the registered public key. | Set kid to the registered KEY ID and sign with the matching private key. |
| Session initialization fails | The bearer token is missing, expired, or invalid. | Generate a new token and retry the initialize request. |
| Later requests fail after initialization | The Mcp-Session-Id header is missing. | Include the session ID returned by the initialize response in subsequent requests. |
| The server returns an MCP error | The request is invalid or the tool is unavailable. | Review the error code and message, then verify the request against the schema returned by tools/list. |
| Tool call fails | The tool name or arguments do not match the tool schema. | Call tools/list and verify the tool name and required arguments. |
Next steps
- For steps on how to authenticate your own application with HERE OAuth 2.1 machine-to-machine (M2M) credentials, see Authenticate a custom application with M2M credentials.
- For information on how to connect from MCP clients such as VS Code or Kiro, see Get started with HERE Location Reasoning.
Updated 11 days ago
Did this page help you?