Skip to main content

Use Copilot from Claude, Cursor and other AI apps

FlowCall Copilot is available as a remote MCP server, so you can work with it from an AI app that supports MCP connectors, such as Claude, ChatGPT, Cursor or VS Code. The app talks to Copilot for you: it starts Copilot conversations, answers Copilot's questions, checks the saved configuration and, when you ask, saves and publishes task changes.

The app acts as you. It can only reach the accounts you can reach and do what your role allows, and the conversations it starts appear in your Copilot history in the dashboard.

Connect an AI app to FlowCall Copilot​

You need Copilot enabled for your user. Then:

  1. In your AI app, add a custom MCP connector (it may be called a remote MCP server or custom connector) with this URL:

    https://api.flowcall.co/mcp

  2. When the app asks you to sign in, it opens FlowCall in your browser. Sign in if needed.

  3. On the Authorize Copilot access page, check that Client is the app you just connected and Returns to is that app's address (for example claude.ai), then choose Authorize. The browser returns to the app.

The connection lasts 30 days. After that the app asks you to authorize again. An authorization page that is left open expires after 10 minutes; connect again from the app to get a new one.

Only authorize a request you started yourself. If you open an authorization page you didn't expect, choose Deny.

What an AI app can do with Copilot​

Through the connector, the app can:

  • list the accounts you can use and start or continue Copilot conversations on them;
  • send your requests to Copilot, answer its questions and read its replies, plan and proposals;
  • read the saved configuration to check Copilot's work: tasks, FAQs, workflows, data points, sample data, Custom APIs, and whether saved tasks match what's live;
  • accept or reject Copilot's task proposals, and publish a saved task to its live flow;
  • for account admins, read debugging evidence for a reported issue or a customer message.

Other proposals, such as data points, Custom APIs, FAQs, templates and tests, are reviewed in the dashboard. The app gives you a link that opens the same conversation in Copilot.

Long Copilot requests keep running in FlowCall while the app waits. The app checks back for the reply instead of sending the request again, so a slow request is never applied twice. If you type or save something in the same conversation in the dashboard, the app reads those new messages before it sends anything else.

Saving and publishing changes from an AI app​

The app only saves or publishes when you ask it to. FlowCall applies the same checks as the dashboard:

  • Simple changes (wording, triggers, flags, dispositions) are saved directly.
  • Logic changes (objectives, conditions, transitions, possible values) save directly only when the task's linked tests pass. Otherwise FlowCall asks the app to get your explicit confirmation first, and the app should show you the reasons.
  • Validation errors are never skipped. Nothing is saved, and the app sends the problems back to Copilot to fix.

Accepting a task proposal saves it to your business context. It goes live only when it's published. Data points and Custom APIs work differently: they take effect for linked tasks as soon as they're saved in the dashboard.

Never paste API keys, tokens or passwords into the AI app. Enter them in the integration's settings in the dashboard.

Troubleshooting the Copilot connector​

  • "AI Copilot is not enabled for your user": ask an admin on your account to turn on Copilot for you, then try again.
  • An account is missing from the list: the app only sees accounts you can open in the dashboard. Check that you can switch to it there.
  • The authorization page says the code is invalid or expired: the request was already used, denied, or left open for more than 10 minutes. Remove and add the connector again, or use the app's reconnect option.
  • The app stops working after a month, or after you revoked it: connections last 30 days. Reconnect and authorize again.
  • Saving or publishing is refused: the app shows why. Validation problems go back to Copilot to fix; logic changes without passing tests need your explicit go-ahead. See Saving and publishing changes from an AI app.

Revoke an AI app's access​

Open https://dashboard.flowcall.co/personal-api/authorize while signed in to FlowCall. Your Copilot credentials lists every connected app and Copilot helper with when it was last used. Choose Revoke to disconnect one immediately.

Copilot MCP connection details for developers​

These details are for building or configuring an MCP client yourself. Most AI apps only need the URL.

  • MCP endpoint: https://api.flowcall.co/mcp, Streamable HTTP. Requests are POST; the server does not offer a separate event stream or sessions.
  • Sign-in: OAuth 2.1 authorization code flow with PKCE (S256 only), for public clients without a client secret. Clients register themselves through dynamic client registration.
  • Discovery: an unauthenticated request to the endpoint returns 401 with a WWW-Authenticate header that points to https://api.flowcall.co/.well-known/oauth-protected-resource/mcp. Authorization server metadata is at https://api.flowcall.co/.well-known/oauth-authorization-server.
  • Scope: copilot. Access tokens last 30 days and there are no refresh tokens, so clients authorize again when a token expires.
  • Who the token acts as: the teammate who authorized it, with their current permissions. Account access tokens from Settings → Integrations don't work with the Copilot connector.