{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/workflow-automation.connect-agent/",
    "json": "https://www.anchorterminal.com/niches/workflow-automation.connect-agent/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/workflow-automation.connect-agent/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/workflow-automation.connect-agent/index.min.md"
  },
  "markdown": "Two or three companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 2 | 12 | 35 | 11 | 7 |\n\n## What counts as done\n\nThe MCP or API connection authorises without a browser step after the first, the tool list loads in the client, and a test shows tools outside the grant are absent and a write outside it is refused.\n\nHow agents ask for it: connect Claude to my n8n; add the Activepieces MCP server; give this agent run-only access to two workflows\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Make API + MCP (Celonis, Inc.)**: OAuth at mcp.make.com/v2 with scopes chosen at connect, and scopes decide which tools load; an API key in a header can be limited to an organisation, team or named scenarios (now MCP toolboxes).\n- **Windmill API + MCP (Windmill Labs, Inc.)**: OAuth sign-in picks workspaces and an access level (Build and run, Read and run, Read only, or named scripts and flows as tools, which give the client nothing else), tokens go in a header, and calls outside the user's permissions are refused.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Activepieces API + MCP (Activepieces Inc.)**: OAuth MCP with tool groups toggled per project, but one tool list per project for every client (acc-16), empty protected-resource metadata on self-hosted (acc-17) and a Cloudflare block for ChatGPT (acc-15).\n- **Microsoft Copilot Studio MCP (Microsoft Corporation)**: Since 1.0.4 sign-in persists in an OS-protected cache across chats, but it needs a local desktop browser (no SSH or headless), and access is the user's full role: no grant narrows the tool list.\n- **Gumloop (AgentHub Inc. (doing business as Gumloop))**: Remote MCP at mcp.gumloop.com with 87 tools; a team-scoped connection drops 33 personal-key tools. The only API OAuth scope is gumloop_api, so a grant can't be limited to running named agents.\n- **Kestra (Kestra Technologies SAS)**: Each MCP server lists only flows pointed at it, which narrows tools, but open-source servers take Basic auth only; API_TOKEN and OAuth (needed for Claude web) and RBAC are Enterprise or Cloud.\n- **Kognitos (Kognitos, Inc.)**: OAuth 2.1 or a header API key; keys are scoped to workspaces with All, Read only or Restricted per-resource permissions. The docs don't show the MCP tool list shrinking under a narrow key, and OAuth needs callback port 3777.\n- **n8n API + MCP (n8n GmbH)**: OAuth or a personal token, and API keys take scopes from 2.14.0, but MCP access isn't scoped per client (every client sees every MCP-enabled workflow), Gemini rejected the tool schemas (acc-38), and Chrome flagged the consent page (acc-39).\n- **Node-RED (OpenJS Foundation)**: No MCP server. The Admin API issues tokens by password grant with scope * or read, lasting seven days, so a read-only grant exists, but nothing narrower and no run-only grant.\n- **Paragon ActionKit + MCP (Forge Technology, Inc. (d/b/a Paragon))**: A per-user JWT narrowed by the urn:useparagon:connect:permissions claim limits credentials and call types (ActionKit, Proxy, workflow triggers), but the listing records that the self-hosted MCP server runs in development mode unless NODE_ENV=production is set.\n- **Pipedream API + MCP (Pipedream, LLC)**: Client-credentials OAuth tokens take a scope parameter (default *), and x-pd-app-slug loads one app's tools, but a granular-scope token got 403 on reloadProps where connect:* worked (acc-27).\n- **Microsoft Power Automate (Microsoft Corporation)**: No MCP server on the pages read; Dataverse Web API access runs under the caller's security roles, so a narrow grant is a role, and the agent's tool list is whatever its client builds.\n- **Prismatic (Prismatic Software Inc.)**: Instance- and integration-scoped MCP URLs narrow the tool list, but API tokens carry the creating user's whole role (a guest user is the narrow option), and the dev server needs prism login in a browser once.\n- **Tray.ai API + MCP (Tray.ai, Inc.)**: OAuth2 binds the session to one workspace, and Agent Gateway serves only the tools a builder exposes, with an access list. Headless MCP acts with the user's full permissions, deletes included, and API-token clients need an npm bridge.\n- **Workato API + MCP (Workato, Inc.)**: OAuth uses the signed-in user's permissions in one workspace and environment, but an API token runs as the workspace owner whatever the client role's other privileges, and OAuth needs a browser per workspace.\n\n- not this job: Bind AI (1Fort Inc.): No MCP server, OAuth client registration or scoped agent token is documented; access is a user JWT or an Api-Key header with no scope list.\n- not this job: Cooper (Mandl) (Cooper AI Tech, Inc.): No MCP server, API key or OAuth client for an outside agent.\n- not this job: Motive Agents (Motive Technologies, Inc.): No MCP or API surface for Agents themselves; Motive's MCP server covers fleet data, which is a different listing.\n\n## What stops agents finishing\n\n- OAuth metadata endpoint empty or blocked by a bot check\n- grant cannot be narrower than the server's full scope list\n- one tool list per project for every client\n- browser sign-in after every restart (Copilot Studio)\n- consent page flagged by Safe Browsing\n\n## Around it\n\nBefore: chat.user-asks. After: workflow-automation.build-workflow, workflow-automation.run-workflow-as-tool.\n\n## Where this comes from\n\nWeight 11 of 100 in Workflow automation: 7 of 48 accounts (n8n, Activepieces, Pipedream); MCP OAuth failures in GitHub issues and the n8n forum\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/workflow-automation.connect-agent.json, or the MCP tool get_use_case with id workflow-automation.connect-agent. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Connect an agent to the platform with only the access it needs",
        "url": ""
      }
    ],
    "description": "Connect an agent to the platform with only the access it needs: 2 companies fully do it, 12 with a limit, 35 carry the tag. Every listing in Workflow automation with the reason and a source.",
    "facts": null,
    "h1": "Connect an agent to the platform with only the access it needs",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/workflow-automation.connect-agent/",
    "published": "",
    "section": "agents",
    "title": "Connect an agent to the platform with only the access it needs |…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/workflow-automation.connect-agent/"
  },
  "tokens": {
    "markdown": 1650,
    "slim": 380
  },
  "version": 1
}
