Troubleshooting — MCP

The terminal appears idle.

The command is waiting for MCP messages on stdin. Configure it in your editor instead of using it as an interactive terminal command.

The server does not start.

Check Node.js 20+, npm connectivity and whether your editor can find npx. Allow enough time for the first download, then restart the MCP connection. On Windows, try the cmd.exe configuration in Connect your editor.

The tools are missing.

Confirm that the server is enabled and that the command ends with mcp. Check the editor's MCP status and logs. The server exposes exactly three tools.

A catalog request fails.

Check access to https://www.aperveil.com and retry after connectivity returns. Catalog requests time out after 10 seconds. If an error reports an incompatible API schema, update the CLI version in your editor configuration.

A Pro item has no install command.

Pro items are currently coming soon. MCP can describe them, but Pro access and sales are closed. Free items need no login; do not add an APERVEIL_TOKEN to MCP configuration.

For local API development, set APERVEIL_API_URL=http://localhost:3000 in the MCP server's environment. This selects the catalog API, not a hosted MCP endpoint. Remote API origins require HTTPS.