Troubleshooting

Confirm the branch and that the latest scan completed. Check that your framework is supported in Inside the code scanner. Custom routers may only be found with AI scanning, which is off by default for new connections (repo connect --ai in the CLI).

Confirm the file is OpenAPI 2.0, 3.0, or 3.1 in JSON or YAML, and check the endpoint count on the collection. A Postman collection must be imported through the Postman importer, not as a spec file.

Reconnect GitHub in Elva and grant access to the repository. A revoked GitHub token is recorded in Workspace logs.

Elva's hosted services only reach public addresses. Localhost, private IPs, and internal-only hosts are blocked. Point the server's base URL at a publicly reachable staging environment.

Check the credential, its scopes, and the upstream account's permissions. For OAuth, compare the redirect URI registered with your provider to the one Elva shows. Reconnect the client after any change to authentication settings.

A draft MCP server is not callable. A rescan or reimport updates the collection but does not republish tools: review the change, publish the MCP server or its parent contract, then reconnect the client.

Follow the client-specific steps in Connect your MCP client. If the install page is Private, you need its password to view the instructions; the password does not authorize tool calls.

The workspace is at its repository, hosted MCP server, or MCP monitor limit. Drafts and the demo resources don't count. See Plans and usage limits.

The workspace is on Free and has used its 1,000 calls this month. Calls resume at 00:00 UTC on the 1st, or upgrade in Settings → Billing.

Check the exit code: 2 is a usage error, 3 means authentication is missing or invalid (run elva auth login), 4 is a validation failure or failed quality gate, and 5 is an API error, including plan limits. Run elva whoami to confirm the identity and workspace.