Skip to main content
FlowFn
IntegrationsTemplatesPricingDocsBlogSign inStart free
All documentation

MCP connections on platform tools

UpdatedMay 28, 2026Reading time2 min read

Model Context Protocol (MCP) is an open standard that lets an AI agent talk to an external service through a single, structured interface — the service exposes the actions it supports and the agent calls them by name. When a platform tool supports MCP, you have two ways to expose it to your agent:

  • Action mode. Pick individual actions on the platform tool (e.g. "create card", "list cards"). Same as before MCP existed.
  • MCP mode. Pick the platform tool itself; the agent talks to the MCP server and discovers what actions are available at runtime.

Tools that ship with MCP out of the box

These tools publish a hosted MCP server and authenticate via the OAuth connection you already have on file. You don't enter a URL or token — just connect via OAuth as usual and the agent picker shows them as MCP-bindable automatically:

  • Notion
  • Linear
  • Asana
  • PayPal
  • Intercom
  • Sentry
  • Canva

The list grows as vendors publish official MCP endpoints. Each tool's detail page shows an MCP server capability chip when MCP is enabled.

Self-hosted MCP (Custom MCP tool)

  1. From Platform tools connect the Custom MCP tool.
  2. Fill in your MCP server URL plus the authentication (bearer token, custom headers, or none) the server expects.
  3. Hit Test connection. The engine performs an SSRF check on the URL and rejects private / loopback / cloud-metadata addresses.
  4. Save. Your team's connection is ready to bind from any agent.

Overriding the MCP URL on a hosted tool

If you self-host a fork of a hosted tool (e.g. a private Notion-compatible MCP server), open your existing connection editor and set the MCP server URL (override) field. The platform-default URL is used when this field is blank.

Notes

  • Only the agent owner's connection is used at runtime, not the connection of the end-user triggering the agent.
  • Per-day MCP call caps are enforced by your plan.
  • v1 supports the streamable HTTP transport. SSE and stdio are reserved for future releases.
  • MCP calls show up on the BYOK activity page — same audit log as platform actions and AI model calls.

Spotted an issue or have feedback?

support@flowfn.com
Back to docs hub →