MCP: Connect Tool Servers
Install catalog tools or configure local and remote MCP servers, then verify and use the connection.
Open: activity bar → Plugins → MCP. For your own service, choose Create custom MCP server from the add menu.
MCP is a way for AI to call external tools. Nexts connects to a tool server and discovers its capabilities. Start with a catalog entry when possible; manual server configuration is for services you are connecting yourself.
What is in this category?
| Feature or connection | What it does | How to use it |
|---|---|---|
| Catalog MCP | Install services with a provided setup form | Choose an entry and complete installation or authorization |
| Local MCP | Run a tool program on your computer | Supply its command, arguments, and environment variables |
| Remote MCP | Access a provider's tool server | Supply its service URL and authentication |
| JSON import | Reuse an existing configuration | Import → Paste configuration → Review and confirm |
| CLI configuration import | Discover existing local MCP configurations | Choose a source → Scan → Review and import |
| Connection checks | Verify that a service starts and responds | Check availability in the server list |
For example, Nexts Canvas uses a local tool connection to help the assistant organize a canvas. Search MCP servers can return web information. See MCP Reference. The desktop client normally prepares the Canvas connection for you.
Install from the catalog and try it
- Open MCP and find the tool you need.
- Review its instructions, runtime location, and required credentials.
- Complete the setup form, save, and enable it.
- Check that the connection is available.
- Return to chat and explicitly ask to use the tool for a small task.
Use the search tool I just connected to find this project's official documentation.
List the page titles and source links.Result: Nexts can discover and call the tool, returning actual results.
What does manual setup require?
| Connection | What to prepare |
|---|---|
Local stdio | The provider's command, arguments, and environment variables; install runtimes such as Node.js or Python when required |
Remote Streamable HTTP | The full server URL and required authentication headers |
Remote SSE | Use this only when the provider specifies an SSE endpoint and authentication |
Use the provider's documented configuration. A regular website homepage is not an MCP endpoint. Put credentials only in dedicated configuration fields; keep secret-bearing JSON out of chat and screenshots.
How is MCP different from Connected Apps?
MCP specifies the tool server used to call a capability. Connected Apps manages which service and account you authorize. Some connected apps use MCP internally, so the two can work together, while account authorization and tool startup remain separate steps.
If the connection fails
- Local: check the command, runtime, arguments, and permissions.
- Remote: check the server URL, network, and authentication.
- Available but no tools: check what the service exposes and whether the current Agent has enabled it.
- No longer needed: disable or remove the configuration and revoke provider credentials when appropriate.