Skip to main content
n8n supports MCP as both a client and a server. For KonbiniAPI, the useful part is n8n’s MCP client support, which lets your workflows and AI agents call KonbiniAPI tools from the hosted remote MCP.

​
Use KonbiniAPI in regular workflows

Use the MCP Client node if you want MCP tools to behave like normal steps in an n8n workflow.
1

Add an MCP Client node

In your workflow, add the MCP Client node.
2

Set the remote MCP URL

Configure:
  • MCP Endpoint URL: https://mcp.konbiniapi.com
  • Server Transport: choose the HTTP transport your n8n version exposes for MCP client connections
3

Authenticate

In the node credentials, choose one of these:
  • OAuth2 if you want n8n to complete the browser-based OAuth flow
  • Bearer if you want to use a KonbiniAPI API key directly
4

Pick the tool and map inputs

Select the KonbiniAPI tool you want to call, then map the inputs from your workflow data.

​
Use KonbiniAPI with n8n AI agents

Use the MCP Client Tool node if you want KonbiniAPI to appear as tools for an n8n AI Agent.
1

Add an MCP Client Tool node

Add MCP Client Tool and connect it to your AI Agent.
2

Set the endpoint

Use https://mcp.konbiniapi.com as the MCP server URL.
3

Choose auth

Use OAuth2 or Bearer credentials, depending on whether you want an OAuth login flow or a direct KonbiniAPI API key.
4

Expose the tools

Include all tools, or select only the KonbiniAPI tools you want the agent to use.
  • Use search_endpoints first to find the right endpoint
  • Use call_endpoint to fetch the social media data
  • Parse the returned JSON string in the next step if your workflow needs fields individually
Official sources: