MCP Connector Issues

Klarify MCP Connector — Known Issues The Klarify MCP connector authenticates and connects fine, but three endpoints currently fail because the connector's GraphQL queries select fields that no longer exist in the current schema. These are server-side faults — re-authenticating or refreshing the connector does not fix them. Broken endpoints Procedure listing — listprocedures, and describeprocess by name (name lookups use the same query). Error: field 'admin' not found in type: 'procedures'. The ListProcedures query selects an admin block that no longer exists on procedures. Describe-process by ID — describe_process by procedure ID. Error: field 'name' not found in type: 'positions'. The procedure resolves, but the activities query selects name on positions, which is no longer a valid field. Document search — search_documents. Error: internal error (from SearchOrganizationDocuments) — an unhandled server-side failure rather than a schema message. What still works getcurrentuser, listfolders, getprocedure (by ID), getprocess (by ID — returns the full flow and step list), listuserdocuments, listprocessactivities, and listemployees. Impact and workaround Both name-lookup paths are broken, so there's no direct way to turn a procedure name into its ID. Everything works once you have an ID — the gap is only in discovery. Workaround: open a parent process with getprocess (or browse listfolders), read its call-activities to get each linked sub-procedure's documentid, then pull it with getprocedure / get_process.