MCP directory
Browse current Nexts MCP servers and understand automatic connections, API keys, and local data boundaries.
MCP (Model Context Protocol) lets Nexts use structured tools to retrieve live information or perform actions. Most people can select the matching connected app and ignore the protocol; MCP details matter mainly during installation, authorization, and troubleshooting.
Current directory
Nexts Canvas
- Purpose: lets the Nexts Agent inspect and operate the current canvas, create nodes, connect workflows, and trigger image or video generation.
- Runtime: a local
stdioMCP that the desktop app prepares and enables when Canvas opens. - Account setup: no separate API key; the current Nexts session is securely shared with the embedded canvas.
- Get started: follow the complete Nexts Canvas tutorial.
Zhipu Web Search
- Purpose: uses Zhipu's official remote MCP to return current web titles, summaries, links, and publication times.
- Runtime: remote HTTPS Streamable HTTP.
- Account setup: requires a Zhipu API key; enter the complete
Bearer ...credential requested by the installation form. - Example: “Search for updates published today and list the date and link for every source.”
Distribution types
| Type | Where it runs | What to verify |
|---|---|---|
| Official/community npm | Starts a publisher package locally | Package, publisher, version, Node.js/npm, and network access |
| NEXTS Hub | Installs a versioned adapter maintained by Nexts | Release URL, version compatibility, and requested permissions |
| Remote MCP | Connects to a publisher's HTTPS service | Domain, authentication headers, and what selected data leaves the device |
Use MCP safely
- Keep API keys and tokens in local secure storage; do not paste them into ordinary conversations, project files, or screenshots.
- Installation makes tools available but does not pre-approve every read or write.
- Before sending, creating, changing, or deleting external data, verify the service, account, destination, and content.
- When removing an integration, delete its local credentials and revoke provider authorization if necessary.
See Connected Apps and MCP for distribution and troubleshooting details.