MCP Tool Configuration
Connect Model Context Protocol (MCP) servers to AionUi so your AI agents can use external tools and context. Full guide: Wiki: MCP Configuration Guide.
What is MCP?
MCP lets AI models interact with external tools—databases, APIs, file systems, and more. By configuring MCP servers in AionUi, you extend what your agents can do.
Setup
In AionUi go to Settings and add MCP servers according to the wiki. Each server has its own configuration (command, env, args, etc.).
Most MCP servers are local processes AionUi launches on your behalf; they inherit your user permissions, so only install servers you trust—same caution as running arbitrary CLI tools.
What MCP unlocks
- Databases & APIs – Let the model query structured sources through controlled tools instead of pasting secrets into chat.
- Filesystem helpers – Specialized readers or converters that complement AionUi’s built-in file management.
- Org-specific glue – Internal ticketing, docs search, or CI status when your team ships a custom MCP server.
Conceptual background: MCP tools integration.
Debugging tips
- Verify the server runs standalone in a terminal before wiring it into AionUi.
- Watch for PATH differences: GUI apps on macOS may not see the same env as your shell—set explicit env vars in MCP config.
- After upgrading Node/Python runtimes, restart MCP processes so they pick up new binaries.