MCP Server
Nected now supports connecting to remote MCP (Model Context Protocol) servers as a first-class integration. Once connected, an MCP server's tools can be pulled directly into a workflow's AI Agent node, letting the agent call external tools (e.g., Notion, internal APIs, custom MCP servers) as part of its reasoning - without you having to hand-wire a REST call for every action the agent might need to take.
This doc covers two things:
Creating an MCP Server connector under Integrations.
Using that connector inside a Workflow, via the AI Agent node's MCP Connectors setting (available when the agent's model provider is Claude / Anthropic).
Where can you find it?
MCP Server is listed alongside REST API under API & MCP Tools on the Integrations page:
Existing MCP Server connectors (once created) show up as cards in this same section, with their environment status (Draft / Staging / Production) just like every other connector type in Nected.
Prerequisites
A running, reachable MCP server endpoint (remote/hosted - not
localhost). If the server sits behind a firewall or allow-list, you'll need to permit Nected's outbound IP (shown in the connector form - see below).OAuth Client ID / Client Secret for the MCP server, if it requires authenticated access. These are optional - leave them blank for MCP servers that don't require auth.
How to Connect your MCP Server?
Open Integrations from the left nav.
Scroll to the API & MCP Tools section and click + Add on the MCP Server card.
A side panel opens, titled MCP Server, with Staging / Production tabs at the top (a connector is configured and tested independently per environment - the panel notes "Here, Integration is only tested in Staging. Click on Production tab to test in Production.").
Fill in the fields:
Name - a unique, identifiable name for this connector (this is the name you'll later pick from the AI Agent node's MCP Connectors dropdown, so name it after the server/purpose, e.g.
Notion MCP,Internal Tools MCP).Server URL - the remote MCP server's endpoint (placeholder text: "Remote MCP server URL").
Client ID (optional) - OAuth client ID, if the server requires authenticated access.
Client Secret (optional) - OAuth client secret, masked like a password field.
If the target server restricts inbound traffic by IP, expand "Expand to see the IP addresses to add to your allow-list" and add the listed IP(s) (e.g.
43.205.43.45) to the server's allow-list before testing.Click Connect.
Click Test Connection to confirm Nected can reach and authenticate against the server.
Once the test passes, click Publish in Staging. Repeat on the Production tab (its own Test Connection + Publish) when you're ready to promote it.
Testing & publishing
Both the connector and the workflow follow Nected's normal Staging → Production promotion flow:
A new MCP Server connector must pass Test Connection in Staging before it can be published to Staging, and the same for Production.
A workflow using an MCP connector should be Test Run in Staging first - this actually invokes the MCP server, so use a non-destructive test prompt if the connected tools can mutate data (e.g. creating/editing pages in Notion).
Only published MCP connectors are selectable from the AI Agent node's MCP Connectors dropdown - a connector left in Draft won't show up there.
Wrap-up
The MCP Server connector slots into Nected's existing integrations model - same Staging/Production lifecycle, same connector-card UI as REST API, databases, and AI providers. The payoff is in the AI Agent node: once a connector is published, Claude can reach for that MCP server's tools mid-conversation, turning a single agent node into a much more capable, tool-using assistant instead of a plain prompt-in/text-out block.
Last updated