Skip to main content
Connect an MCP-compatible agent to Flowglad to work with your organization’s business knowledge and operational context. The connector can find and edit Pages, read files and connected records, create Tasks, manage reusable Skills, and create or run Automations. Available tools depend on the connected identity, granted permissions, and enabled product features.

Before you connect

You need:
  • A Flowglad account with access to the organization you want to use.
  • Your organization’s production MCP URL.
  • An agent or client that supports a remote MCP server over Streamable HTTP and OAuth.
  • The organization and Space permissions needed for your intended work.
  • Any source Connection or file already available to the relevant Space.
The published pricing section on the Flowglad homepage includes MCP in Free, Plus, and Max. Organization and Space permissions, the OAuth grant, and connected-source access still apply. Connections to outside business systems must be configured in Flowglad and exposed to the intended Space before the agent can use them. See Connectors and Spaces.

Find your organization URL

The production connector uses an organization-specific URL:
Replace {orgId} with your actual Flowglad organization ID. Preserve the complete ID, including its org_ prefix. Do not enter the braces or a made-up organization ID. In Flowglad, open SettingsMCPAdd MCP ConnectionClaudeWebsite. Copy the organization MCP URL shown there. Use the Website instructions for a remote URL; the separate Desktop app tab contains command-line setup instructions. If you cannot access these settings, ask your Flowglad administrator or support. Use the organization URL for this connector. A connection-specific URL can expose a narrower tool set and is not interchangeable with the organization URL described here.

Connect from Claude Desktop

Watch the Claude Desktop setup video, or follow the steps below.
Use Claude Desktop’s custom connector flow to add Flowglad and authorize access to your account. 1. Open the custom connector form. In Claude Desktop, navigate to CustomizeConnectors+ AddAdd Custom Connector. 2. Add the Flowglad connector. Enter Flowglad as the connector name, or choose another name. Paste your complete organization MCP URL into the URL field (you can grab it from Settings > MCP). It should look like this: https://dashboard.flowglad.com/api/mcp/orgs/org_... Do not change any other connector settings. Select Add to continue. Claude Desktop may label this button Continue in some versions. 3. Grant Claude Access to Flowglad. Continue through the connection flow to authorize Claude to access your Flowglad account. When prompted, sign in, confirm the intended Flowglad organization, and review the requested access before authorizing it. When the flow completes, return to Claude Desktop and confirm that the Flowglad connection is available. Ask Claude to check the Flowglad connection and list the Spaces you can access. OAuth Dynamic Client Registration is the intended connection method. Do not add a password, access token, API key, or client secret to the server URL. These instructions describe connecting Flowglad directly as a custom connector; directory availability is separate.

Connect another MCP client

Add the same organization URL as a remote Streamable HTTP MCP server. Complete the client’s OAuth flow with your Flowglad account, then verify the organization and available tools. Client support varies. A successful server connection does not mean the client imports Flowglad Skills automatically. The Skill discovery extension and the skills.list tool are different interfaces. See Skills for supported discovery and package-management behavior.

Data handling

Use of the Flowglad MCP is governed by the Flowglad Privacy Policy. For organization admins, you can see all of the MCP tool calls made to your organization in Settings > Audit

Troubleshooting

For general security information, Security and our Trust Center. If you are having any trouble connecting, contact us. When contacting support, include the time, client, affected tool, safe error code, and request ID if available. Never include passwords, bearer tokens, cookies, signed upload/download URLs, or customer data.