{
 "categories": [
  "data-exchange",
  "gis",
  "platform"
 ],
 "deployment": "hybrid",
 "evidence": [
  {
   "date": "2026-09-13",
   "fact": "homepage",
   "note": "Safe presents FME as its All-Data, Any-AI integration platform and names FME Flow as the governed MCP integration layer for AI agents, plus the MCPCaller transformer.",
   "source": "https://fme.safe.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "deployment",
   "note": "Safe documents FME Flow Hosted on AWS, customer cloud and on-premises installs, Docker and Kubernetes, and hybrid deployments under one subscription.",
   "source": "https://fme.safe.com/platform/deployments/",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "license",
   "note": "Deployment options are sold as a commercial subscription covering Flow, hosted, and related install paths rather than a no-cost product.",
   "source": "https://fme.safe.com/platform/deployments/",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "status",
   "note": "Downloads list FME Flow 2026.2 as the current release, with 2026.3 as beta, confirming an active product line.",
   "source": "https://fme.safe.com/downloads/",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.api.exists",
   "note": "Safe publishes FME Flow REST API V4 as the stable REST API, with interactive docs and an OpenAPI spec.",
   "source": "https://docs.safe.com/fme/html/fmeapiv4/docs/index.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.api.kinds[0]",
   "note": "V4 is documented as a REST API hosted on each Flow instance at the /fmeapiv4 base path.",
   "source": "https://docs.safe.com/fme/html/fmeapiv4/docs/index.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.api.auth[0]",
   "note": "Token Management creates API tokens with an expiration and either all permissions of the current user or a selected subset, such as running a particular workspace.",
   "source": "https://docs.safe.com/fme/html/FME-Flow/WebUI/Manage-Token.htm",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.api.coverage",
   "note": "The public V4 OpenAPI 3.0 document lists 287 paths across jobs, tokens, repositories, automations, schedules, streams, security, and related tags. Coverage is the documented machine admin surface, not every Web UI control, so it is recorded as partial.",
   "source": "https://docs.safe.com/fme/html/fmeapiv4/docs/schema/static.json",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.api.docs",
   "note": "Safe points developers to the in-product REST API help, https://docs.safe.com/fme/html/FME_REST/apidoc/v4/index.html, and http://<host>/fmeapiv4/docs/index.html.",
   "source": "https://docs.safe.com/fme/html/FME-Flow/DevelopersGuide/REST-API-Method-Reference.htm",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.mcp.first_party",
   "note": "FME Flow Web UI docs describe first-party MCP servers: each server gets a generated client URL, tools run uploaded workspaces, authentication is unauthenticated or OAuth 2.0 with SAML, and servers must be started before clients can connect.",
   "source": "https://docs.safe.com/fme/html/FME-Flow/WebUI/MCP-Servers.htm",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.mcp.verdict",
   "note": "Safe's 2026-07-28 product update states the MCP Server is available in FME 2026.2, exposes workspaces as MCP tools, uses OAuth 2.0, and inherits Flow role-based permissions and audit trail.",
   "source": "https://community.safe.com/product-updates/introducing-fme-flow-s-mcp-server-40673",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.mcp.third_party",
   "note": "Bounded official MCP Registry search for 'fme flow' returned zero servers. First-party coverage is Safe's own docs, not a registry listing.",
   "source": "https://registry.modelcontextprotocol.io/v0.1/servers?search=fme%20flow",
   "tier": "scraped"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.extensibility.scripting[0]",
   "note": "Token permissions include Automations access, create, and per-workflow read, write, run, apps, and webhook rights.",
   "source": "https://docs.safe.com/fme/html/FME-Flow/WebUI/Manage-Token.htm",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.extensibility.webhooks",
   "note": "Automations Webhook triggers accept HTTP POST, PUT, or DELETE bodies, generate a URL on save, and can require Webhooks permission.",
   "source": "https://docs.safe.com/fme/html/FME-Flow/WebUI/Automations-Triggers/Trigger-Webhook.htm",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.data_access.export[0]",
   "note": "V4 job and resource endpoints return JSON records, including job status listings.",
   "source": "https://docs.safe.com/fme/html/fmeapiv4/docs/schema/static.json",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.data_access.export[1]",
   "note": "V4 documents GET /jobs/{id}/result and GET /jobs/{id}/log for retrieving a completed job's result and log.",
   "source": "https://docs.safe.com/fme/html/fmeapiv4/docs/schema/static.json",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.data_access.import[0]",
   "note": "V4 accepts JSON POST bodies for creating jobs, tokens, automations, and other Flow objects.",
   "source": "https://docs.safe.com/fme/html/fmeapiv4/docs/schema/static.json",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "https://fme.safe.com/llms.txt is a crawler allowlist dated 2025-07-24, not an agent tool or API guide, so llms_txt is recorded as false.",
   "source": "https://fme.safe.com/llms.txt",
   "tier": "scraped"
  },
  {
   "date": "2026-09-13",
   "fact": "verdict.scores.api",
   "note": "V4 is a maintained, documented, read/write admin REST API with token scoping and job, automation, and repository coverage. Instance-local hosting and permission configuration keep it in the broad-production tier rather than unusually complete.",
   "source": "https://docs.safe.com/fme/html/fmeapiv4/docs/schema/static.json",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "verdict.scores.mcp",
   "note": "The official MCP path is maintained and useful for invoking published workspaces, but it is not a general Flow API: tools must be published, servers must be started, OAuth needs SAML, and workspaces without an MCP Writer usually return only job status.",
   "source": "https://docs.safe.com/fme/html/FME-Flow/WebUI/MCP-Servers.htm",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as the current FME Flow MCP Servers Web UI reference, including OAuth 2.0, SAML, start/stop, and tool publish behavior.",
   "source": "https://docs.safe.com/fme/html/FME-Flow/WebUI/MCP-Servers.htm",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the current public FME Flow REST API V4 documentation index.",
   "source": "https://docs.safe.com/fme/html/fmeapiv4/docs/index.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as Safe's 2026-07-28 FME 2026.2 MCP Server product update.",
   "source": "https://community.safe.com/product-updates/introducing-fme-flow-s-mcp-server-40673",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "freshness.watch[3].url",
   "note": "Opened and verified as the bounded official MCP Registry query monitored for FME Flow listings.",
   "source": "https://registry.modelcontextprotocol.io/v0.1/servers?search=fme%20flow",
   "tier": "scraped"
  }
 ],
 "freshness": {
  "last_verified": "2026-09-13",
  "volatility": "high",
  "watch": [
   {
    "type": "docs",
    "url": "https://docs.safe.com/fme/html/FME-Flow/WebUI/MCP-Servers.htm"
   },
   {
    "type": "docs",
    "url": "https://docs.safe.com/fme/html/fmeapiv4/docs/index.html"
   },
   {
    "type": "changelog",
    "url": "https://community.safe.com/product-updates/introducing-fme-flow-s-mcp-server-40673"
   },
   {
    "type": "registry",
    "url": "https://registry.modelcontextprotocol.io/v0.1/servers?search=fme%20flow"
   }
  ]
 },
 "homepage": "https://fme.safe.com/",
 "id": "fme-flow",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": false
  },
  "api": {
   "auth": [
    "api-token"
   ],
   "coverage": "partial",
   "docs": "https://docs.safe.com/fme/html/fmeapiv4/docs/index.html",
   "exists": true,
   "kinds": [
    "rest"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "api-json",
    "job-result"
   ],
   "import": [
    "api-json"
   ]
  },
  "extensibility": {
   "scripting": [
    "automations"
   ],
   "webhooks": true
  },
  "integrations": {
   "make": "unknown",
   "n8n": "unknown",
   "power_automate": "unknown",
   "zapier": "unknown"
  },
  "mcp": {
   "first_party": true,
   "third_party": [],
   "verdict": "official"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. FME Flow REST API V4, Automations webhook triggers, and the first-party MCP Server cover job and workspace automation without browser control of the Flow Web UI.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "FME Flow",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "airbyte",
   "fivetran",
   "workato"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Safe Software",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 8,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": 7,
   "overall": 8,
   "rpa": null
  },
  "summary": "FME Flow is automatable today through REST API V4 on a Flow instance the organization already runs, whether self-hosted or FME Flow Hosted on AWS. The public V4 spec is Safe's stable JSON REST surface and documents jobs, tokens, repositories, automations, schedules, streams, security, and related admin resources. Access uses API tokens created in Token Management; tokens can be scoped to a workspace or job rather than inheriting every permission of the creating user. This record is FME Flow only. FME Form desktop authoring is a separate identity. From FME 2026.2, Flow can also host one or more first-party MCP servers that expose published workspaces as MCP tools. OAuth 2.0 is available when SAML is already configured; unauthenticated MCP endpoints are also offered. Servers stay dark until they are started, and workspaces without an MCP Writer typically return only job status. MCP therefore publishes the workspaces an organization chooses, not the full V4 admin API. Automations webhook triggers accept POST, PUT, or DELETE bodies. An official SDK, a first-party CLI, workflow connector catalogs, and computer-use viability were not established.\n"
 }
}