MCP clients find shared tools in the right workflow

AI assistants connecting to AmpliFlow through MCP can now read what each tool may do before it is used. OpenAI-compatible information distinguishes reading, changes, destructive actions, external network access, and sign-in behavior.

Older MCP clients can also connect again when they omit the newer OAuth resource parameter.

AI assistants using the compact MCP beta can now find shared helpers directly in every relevant workflow.

Improvements

MCP

• ChatGPT and other OpenAI-compatible clients receive clear safety markers for every MCP tool. The client can see whether an action only reads data, changes something, can delete content, or may contact an address supplied by the user.
• The client receives machine-readable rules for the information each tool accepts. Arguments that the tool does not support are rejected.
• If the MCP session is missing or has expired, the client receives a machine-readable prompt to reconnect. The prompt remains tied to AmpliFlow’s MCP service.
• Your existing AmpliFlow permissions continue to control what each user can see and do. The update adds no new rights or broader access, and existing result formats remain available.

Fixed bugs

MCP

• The compact MCP beta now shows shared helpers in every workflow where they are used. For example, the Improvements workflow can retrieve impact grading options without switching to another feature catalog. Existing permissions, safety checks, and approval flows still apply.
• Older MCP clients, including existing Microsoft Copilot Studio connections, can sign in again even when they omit the OAuth resource parameter. AmpliFlow then selects the full MCP connection and keeps access bound to it. The compact beta still requires explicit selection.

Want to use AmpliFlow with ChatGPT or another MCP client? Read about the MCP connection or contact support.