Your company already has a standalone document-processing agent and…

Question

Your company already has a standalone document-processing agent and a separate MCP-based records tool server. A new multi-agent solution must reuse both without rewriting them from scratch, while keeping secure integration. What should you do?

Accepted Answer

Integrate the existing agent via Agent2Agent (A2A) where supported and consume the records capabilities through MCP clients, applying authentication and least-privilege scopes at the integration boundaries. — Reuse beats rewrite: plug the existing document agent in through Agent2Agent where supported, then consume the records tools through MCP clients. Keep authentication and least-privilege scopes at the integration boundaries. Copy-pasting SQL usernames into prompts isn’t integration.

Answer

Duplicate all document-processing code into every new agent repository and call the database with shared SQL usernames embedded in prompts.

Answer

Force a full rewrite of both systems into a single monolithic agent before any integration is allowed.

Answer

Ignore existing assets and scrape their UIs with computer-use only, without APIs or protocols.

Your company already has a standalone document-processing agent and a separate MCP-based records tool server. A new multi-agent solution must reuse both without rewriting them from scratch, while keeping secure integration. What should you do?

Short Explanation

Full Explanation