Skip to main content

MCP Connector and Google/Slack Integrations

Status

Owner: TBD · Status: draft · Canonical source: flezi.app.frontend.main/src/pages/McpServers.tsx, src/components/mcp-servers/

Who is this for?​

Administrators and members connecting Agents to external tools through Model Context Protocol (MCP). The application screen is named MCP Connector.

What can you do?​

  • Add connectors using Streamable HTTP, SSE (legacy), or STDIO.
  • Run Test Connection to handshake and discover available tools.
  • Bind connectors to Agents, share them by Workspace or direct user grant, and manage per-user OAuth authorization. Organization-wide MCP sharing is not currently verified.
  • Connect the built-in Google Workspace and Slack providers with OAuth 2.0 PKCE.

Transports and statuses​

Transport / statusMeaning
Streamable HTTPDefault transport for modern MCP HTTP servers.
SSE (legacy)SSE transport for older servers that still support it.
STDIORuns an MCP process with a command in the service runtime. The command must be installed and visible to that runtime.
ConnectedConnection succeeded and tools were discovered.
Needs OAuthThe connector requires the current user to authorize an account before testing or loading tools. This can differ between members.
Error / DisconnectedThe latest connection failed or the connector is not connected. Read the card error and try again.

Add a connector​

  1. Select MCP Servers in the sidebar and click Add MCP Connector.
  2. Enter a display name, URL/command, and transport:
    • Streamable HTTP: Use an MCP URL; do not enter a normal REST URL such as /api/v1/....
    • SSE (legacy): Use the MCP server's SSE endpoint.
    • STDIO: Enter a command and arguments. ${ENV_VAR} references are supported; command and arguments are parsed as shell-like tokens but are not executed through a shell.
  3. Click Test Connection. Tool discovery is bounded at 30 seconds, so a server that never lists tools fails rather than leaving the run waiting indefinitely.
  4. Review the discovered tools and click Save.
  5. In Agent Builder, bind a connector that you own or that has been shared with you.
OAuth connectors

For a connector in Needs OAuth, complete Connect OAuth or Sign in with Google/Slack before Test Connection. Each user authorizes separately; your token is never shared with another member.

Google Workspace and Slack​

  • Google Workspace MCP: configure a Google Cloud OAuth App or upload token.json for the current account. Available tools depend on the selected connector.
  • Slack MCP: configure a Slack Client ID/Client Secret at organization level, then authorize an individual Slack account. Do not use a bot token instead of a user token.

Common issues​

  • STDIO command not found: Install the package/executable in the image or service host and check the service runtime PATH, not only an interactive terminal PATH.
  • Needs OAuth: Open Account & OAuth, authorize the current account, and test again. A shared connector still requires separate authorization.
  • Test timeout: Check the URL, transport, and server health. Runtime discovery is limited to 30 seconds.
  • OAuth returns to the UI but is not Connected: Only backend oauth_result=success is treated as success; mcp_connected=1 alone is not sufficient.