Add tools to a conversation
3 minute read · Chats & Local Agents
Add a supported external MCP server when your coding agent needs another tool. MCP is a way to connect tools; discovering a server does not make every action it offers safe.
- Connect an external tool server
- Review the trust boundary
- Diagnose and remove a connection
- Try one tool before expanding access
Connect an external tool server
Open the MCP settings for tools used by chats, then add the supported external server configuration. Review its command or endpoint, required environment values and authentication. Keep those values in the protected settings path and preserve unrelated existing agent configuration.
Enable the server for the intended use and check its reported state. Start a small discovery/read task before depending on a mutation. For example, ask the agent to list the tool names and explain which one can inspect your test issue tracker. A server that starts successfully can still require account authorization for a particular tool.
Review the trust boundary
External tools can return untrusted text and may reach a different account or system. A discovered tool is not automatically safe, and its returned instructions do not expand the user's original task. Read the operation details before authorizing writes, messages or deployment.
The selected provider must support the relevant external MCP integration. Do not assume every server feature behaves identically across all five coding agents. Vortex's native confirmation policies and the provider's own permissions may both apply.
Diagnose and remove a connection
If the server is unavailable, inspect the configured executable/endpoint and returned startup error without publishing environment secrets. Distinguish server startup, authentication and individual tool failure. A timeout should not be presented as a successful operation.
Disable or remove the external connection when you no longer want it available. This is distinct from Share Vortex tools, which exposes your saved developer resources to a supported local external agent. Do not turn on that second direction merely to fix a chat-tool connection. Read sharing Vortex tools for its resource and approval controls.
Try one tool before expanding access
After connecting an external MCP server, choose a harmless operation such as listing resources or reading a known sample. Confirm which account and destination the server uses. A tool response can include untrusted instructions or private data; ask the agent to treat returned content as evidence, not a change to your permission rules.
Keep environment values and authentication in the protected configuration. Enable only the servers needed for the conversation. If a server is unavailable, inspect its startup command, connection state and required local service before reinstalling unrelated tools. Removing a server should preserve the client's other configuration.
For Vortex's own saved resources, use Share Vortex tools. The two directions can be used together, but they have different setup and trust boundaries.
Related guides: Share Vortex tools, agent permissions.