MCP Server

Description

This integration connects Nussknacker to an external MCP server, so that the AI Agent component can call the tools that server offers. You add it in Integrations (at /configurator), as an integration of the MCP Server type. The AI Agent component appears in the Components Palette once at least one MCP integration is defined.

When the agent runs with a supported AI integration (e.g. Bedrock, Mistral, OpenAI), the model decides when to invoke these tools.

note

This is Nussknacker acting as an MCP client. To publish your own Request-Response scenarios as tools that external AI agents call, use the MCP item in the side menu instead - see MCP servers.

Parameters and configuration

Parameter names follow standard HTTP terminology. If unsure, refer to an HTTP reference such as MDN Web Docs.

Name	Description
Integration name	Unique name for the integration
URL	The target URL for the request. The URL should contain scheme - typically http or https.
Headers	HTTP request headers. Often used for content types, authentication, or custom metadata.