Apply a template
Whentemplates.apply is available in tools/list, supply a published
templateId and an existing spaceId to create all of the template’s resources.
Applications, Automations, and ordinary File copies belong to that Space; Skills belong to the organization. Files use their configured filenames at the Space root and never overwrite existing files. A same-name conflict fails that component while independent components can continue. File completion means the bytes and metadata were durably saved; it does not wait for indexing.
Optionally supply connections as an array of { connector, connectionId }
objects, with at most one connection per provider. Supplied connections must be
accessible, compatible, and already assigned to the Space when required. Omitted
connections leave resources awaiting configuration. The response recommends
eligible connections, or creating a connection when none are available.
Creation runs in a single Trigger.dev task in dependency order, with component
outcomes recorded in the task metadata and output. Automatic retries of the
whole task are disabled; a failed or interrupted task can leave partial resources. The response acknowledges that creation
was queued and includes the planned components and connection recommendations;
it does not confirm that resources have finished creating. Use the resources’
list/get tools to find and inspect them. Successful resources remain if another
component fails.
Applying a template defers executable verification and does not activate or run
its resources. Each apply call is a new creation intent, including retries. Do not repeat
templates.apply to check progress: existing File names conflict, and executable
components may produce additional copies. An unknown write outcome interrupts the
task; inspect the destination before starting another apply. Existing successful
resources are retained, with no whole-task replay or resume binding.
templates.search, templates.get, and templates.apply include ordinary Files,
including templates containing only Files. Customer web summaries currently show
Skills, Automations, and Applications; File-only web setup is deferred. File
results appear in apply progress but cannot be executable dependency references.
File copies use the ordinary resource-file extension policy, per-file size limit,
organization storage quota, and current Space File write permissions. The task
rechecks both the delegated MCP grant and current principal permissions before
writing. A File uses the current published source at creation; later source edits
do not change existing copies. Source previews are available only to verified
platform administrators. Customers read or download their created Space files
through the existing native file tools and permissions.
Before you connect
You need:- A Flowglad account with access to the organization you want to use.
- The Flowglad MCP URL. Use the universal URL or your organization’s 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.
Choose an MCP URL
Flowglad accepts two production MCP URLs. Both expose the same organization tools after you authorize.Universal URL
orgId field that identifies the target organization; when the grant includes multiple accessible organizations, tool calls must supply it. tools/list can also take orgId to discover one organization’s available tools. Every operation checks both that organization’s grant selection and your current permissions.
Joining another organization does not automatically extend an existing grant. Authorize the client again to include it. If you lose access to an organization, the client loses access to it too.
Organization URL
Organization-specific URLs still work:{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. Flowglad skips the organization choice for this URL because the organization is already in the URL.
In Flowglad, open Settings → MCP → Add MCP Connection, choose your client, and copy the MCP server URL shown there. The settings page shows the universal URL.
If you cannot access these settings, ask your Flowglad administrator or support.
A connection-specific URL can expose a narrower tool set and is not interchangeable with the universal or organization URL described here.
Manage grants
Flowglad keeps one active universal grant for each user and client, containing all selected organizations and their individual capabilities.- Reconsent. Authorizing the same client again replaces the organization selections in its existing grant.
- Revocation. Revoking that grant ends the client’s access to every organization included in it. Existing access and refresh tokens cannot authorize MCP operations.
- Reconnect. Connecting after revocation creates a new grant.
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 Customize → Connectors → + Add → Add Custom Connector.
2. Add the Flowglad connector.
Enter Flowglad as the connector name, or choose another name.
Paste the MCP URL into the URL field. Use the universal URL,
https://dashboard.flowglad.com/api/mcp, or your organization URL from Settings > MCP, which looks like 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, choose or 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 from ChatGPT (website)
Watch the ChatGPT website setup video, or follow the steps below.
1. Copy the MCP URL.
Copy the universal URL,
https://dashboard.flowglad.com/api/mcp, or open Settings → MCP → Add MCP Connection → ChatGPT → Website and copy the MCP server URL shown there.
2. Open ChatGPT Plugins.
Go to chat.com/plugins.
3. Create an MCP app.
Select Add in the top right, then select Create MCP App.
4. Add the Flowglad server.
Paste the MCP URL as the server URL and name the plugin Flowglad.
5. Sign in and connect.
Complete the Flowglad login flow. Sign in, choose or confirm the organization, and review the requested access before authorizing it.
Connect another MCP client
Add the universal URL or your 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 theskills.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. Organization admins can see all MCP tool calls made to your organization in Settings > Audit.Troubleshooting
For general security information, see 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.