← Documentation
PLUXIX GUIDE
MCP connections
Extend the Agent with approved external tools while keeping credentials, scope and health visible.
What MCP provides
An MCP connection exposes named tools and resources from an approved server. PLUXIX keeps the connection configuration separate from the task text and presents tool activity as part of the conversation evidence.
- Use read-only access for discovery and analysis whenever possible.
- Name servers by their purpose so tool calls remain understandable.
- Test a connection before using it in a production task.
Configure a server
Open MCP settings in the Agent, choose the supported transport and enter the server configuration. Review the command, URL, environment variables and credential fields before saving.
- Use HTTPS for remote servers.
- Keep secrets in the protected credential store; never paste them into a prompt.
- Remove unused servers and rotate credentials after access changes.
- Disable a server when its tools are not needed for the current project.
Health and failure
A disconnected server does not mean the entire Agent is offline. Check the individual health state, server logs and tool error. Retry after fixing the server or continue with a task plan that does not require it.