The AmpliFlow MCP server now lets AI assistants work with much more of AmpliFlow. If you connect ChatGPT, Claude, Copilot Studio, or another MCP client to your tenant, the assistant can now help in more real workflows, from projects and tasks to risks, processes, controls, and business records.

This update also makes the hosted connection more stable: it is clearer which tools an assistant can use, and it is easier to reconnect after a restart.

What’s new

AI assistants can work with many more AmpliFlow workflows through MCP. The MCP server now covers more of AmpliFlow, including projects, tasks, comments, task files, subtasks, blockers, milestones, tags, project files, and project discussions.
More management-system workflows can be handled by an assistant. MCP support now also includes goals with measurements, processes and process steps, checklists, risks, improvements, controls with evidence files and SoA export, news, and custom lists.
Compliance and business records have broader MCP support. Assistants can now read and, when write mode is enabled, update more records for legal requirements, customer requirements, training plans, environmental aspects, suppliers, stakeholders, customers, and items.
Project lists can be filtered to favorite projects. MCP clients can ask for only favorite projects when the user wants to work in their closest project view.
OAuth setup is smoother. You can connect with a short tenant name, a custom hostname, or a full HTTPS tenant URL. That removes an unnecessary step when you connect a new MCP client.
Hosted MCP connections survive restarts better. A hosted connection can reconnect after a restart without forcing the user to restart registration.

Improvements

Read-only mode is stricter when it is enabled. A deployment can start the MCP connection in read-only mode when the assistant should only read. In that mode, write tools such as create, update, archive, and delete are not shown to the client, while list, show, and search tools remain available.
MCP clients get clearer responses. Many tools now return structured responses while keeping the previous text JSON version. This helps clients such as ChatGPT, Claude, and Copilot Studio understand the result and continue correctly.
The tool list describes safety more clearly. Every MCP tool has clearer names, descriptions, and safety markings for reading, writing, deleting, and local file access. That makes it easier for clients and administrators to understand what an assistant can do.
Project and task actions are safer. MCP references for tasks, blockers, tags, milestones, and related project actions are checked inside the same project. That reduces the risk of an assistant changing the wrong record.
MCP references are clearer to reuse. The client should reuse the exact reference returned by a list or search tool. That makes follow-up actions more predictable.
Hosted MCP access is safer by default. Requests without a valid login are rejected, and expired credentials are never silently reused.
MCP works with more clients. The server handles more client connection formats, so the connection works in more tools.

Fixed bugs

Dynamic client registrations remain after restarts. Hosted clients no longer need to register again only because the server restarted.
The OAuth flow shows permissions more clearly. Users get better information about what the MCP connection can do before they approve the connection.
OAuth connections are kept more clearly apart. This reduces mix-ups when several clients or environments are in use.
MCP tasks handle files and details more completely. Assistants can now list, upload, and delete task files, and processes can be shown with more of their detail information.

One compatibility question we are looking at now is Microsoft Copilot Studio. In our tests, Copilot Studio can currently limit an MCP connection to 70 tools, so we are reviewing how AmpliFlow’s tools can be packaged smarter for that environment. If you have concrete Copilot Studio scenarios, please tell support.

Related updates: the previous changelog added custom controls, calendar input for time reporting, and faster project work. The next changelog continued with faster timesheets, clearer AmpliFlow Box logs, and better barcode validation.

If you want help connecting AmpliFlow to your AI assistant, contact support.

This page is also available in Swedish.