MCP Reference
Understand local and remote tool connections, installation, and authorization.
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.
For ordinary web queries, start with Web search. These are examples of connection types; use the client's current catalog for availability.
Connection examples
Nexts Canvas
- Purpose: lets the Nexts Agent inspect and arrange Canvas, create nodes, connect inputs, and prepare parameters. The user starts each model generation manually in Canvas.
- 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
- Enter keys and tokens only in dedicated authorization forms, not chat, project files, or screenshots. Local and cloud-managed connections store credentials differently.
- 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 for authorization, multiple accounts, and troubleshooting.