Can AI agents automate IBM FileNet Content Manager?

IBM FileNet Content Manager is automatable today through the Content Services GraphQL API and a first-party MCP server that calls that API. GraphQL is a separately deployed Content Services application. IBM documents BASIC authentication on the deployed content-graphql.war, a ping URL at /content-services/ping, and GraphQL queries against a Content Platform Engine object store. The product page names low-code tools and GraphQL APIs for embedding FileNet services. Coverage is end-user runtime work — documents, folders, search, metadata — not a claim that every Content Platform Engine administrative surface is exposed. The IBM Core Content Services MCP Server, listed on IBM/mcp and published at ibm-ecm/ibm-content-services-mcp-server, is a vendor-owned Python server. Its 1.0.0 changelog calls the release general availability; 1.0.4 is dated 2026-03-25. Required configuration is SERVER_URL (GraphQL endpoint), USERNAME, PASSWORD, and OBJECT_STORE. The core server documents 26 tools for document lifecycle, folder filing, class metadata, and search. Optional companion servers add property extraction, legal hold, and AI Document Insight tools. AI insight requires FileNet 5.7.0 IF003 or later plus Persistent Text Extract and Content Assistant. Core, legal-hold, and property-extraction tools need FileNet 5.5.8 or later and a live CS-GQL deployment. This record is FileNet Content Manager. It is not SharePoint and not M-Files. iPaaS connectors were not opened. Computer-use viability is unassessed. API and MCP both score 7; API is the best path because the MCP server is a GraphQL client and the same CS-GQL deployment, credentials, and object-store grants are required either way.

Best path today: api · Overall automatability: 7/10