Connect
Capture
Understand
Act
Measure and forecast
Meet the Stellan agentsKnowledge Agent, AI SDR, Briefer, Deal Monitor and CRM Copilot.See the agents →DevelopersMCPTroubleshoot MCP
Troubleshoot MCP
Fast diagnosis for installation, OAuth, callback, scopes, catalog, and tool calls.
Two-minute checklist
- Confirm that the configured server is exactly https://mcp.aivyro.io/mcp.
- Update the entry with npx @aivyro/mcp@latest setup and reload the client.
- Sign in to Aivyro in the browser and confirm the active organization before authorizing.
- Request tools/list or aivyro.getting_started; do not validate the connection only from the client’s visual status.
Common errors
| Symptom | Likely cause | What to do |
|---|---|---|
| No grantable scopes | The connection requested permissions that the current account, role, or policy cannot grant. | Confirm organization and role; disconnect the old grant; update the client and authorize again. If it persists, an administrator must review account permissions. |
| The browser completes, but the client stays disconnected | The local callback expired, was blocked, or belongs to another attempt. | Close the attempt, start a new connection in the client, and complete only the newest URL. Do not reuse callback links. |
| 401 or repeated login request | Token is missing, expired, or revoked. | Disconnect Aivyro in the client, remove the old authorization, and reconnect. |
| An expected tool is missing | Scope, role, policy, entitlement, or service health does not admit the tool. | Refresh tools/list, check organization and permissions, and do not rely on a cached tool list. |
| The action requests confirmation and does not continue | The client did not complete or does not support the confirmation request. | Approve or decline in the client. If it has no confirmation UI, use a compatible client; Aivyro will not run the action silently. |
| The tool returns 403 | Authentication worked, but the action is not allowed for that user or resource. | Do not retry with different IDs. Check the role and request the correct permission from an administrator. |
| The tool returns 429 | The call limit was reached. | Wait for the indicated time, reduce repeated or aggressive pagination, and try again. |
Rebuild the configuration
Replace codex with your client identifier. Then reload the client and complete a new authorization. Removing local configuration alone does not revoke a previously granted token.
What to send support
- Client name and version and @aivyro/mcp package version.
- Approximate time, affected organization, and tool name.
- Public error code and traceId, when shown.
- The failed step: discovery, browser, callback, tools/list, or tools/call.