troubleshooting
Here are solutions to the most common configuration and execution issues developers face when running Andromity.
This error occurs when the LLM attempts to invoke an MCP tool, but the connected MCP server does not support that specific method.
- Check if the MCP server has been updated to support the new schema.
- Verify tool naming inside your configuration. Run
/mcpin the TUI to double-check spelling. - Re-index MCP servers: restart Andromity to force cached tool index updates.
The connection between the Andromity TUI and the background MCP process terminated unexpectedly.
- Verify execution paths: Ensure commands like
npxorpythonare available on your systemPATH. - Test server independently: Try running the MCP server command directly in your shell (e.g.
npx @modelcontextprotocol/server-sqlite --db mydb.db) to see if it starts successfully or throws an error. - Environment variables: If the server requires secret tokens (such as
GITHUB_PERSONAL_ACCESS_TOKEN), ensure they are set in the shell before launchingandromity.
Andromity timed out waiting for responses from the LLM routing bridge.
- API rate-limits: Verify that your provider credentials have not expired or reached active rate limits.
- Network proxy: If behind a corporate firewall, set the
HTTPS_PROXYenvironment variable so LiteLLM can route outbound requests successfully. - Local performance: If running local Ollama models, verify that the local LLM is responsive. Slow system hardware can cause response timeouts.