MCP Connector
Governed end-to-end M&A execution — directly from your AI agent
Connect your AI agent to smartmerger.com and execute M&A deals end-to-end. Securely access live deal data across workstreams, risks, findings, tasks, documents and decisions — all within your governance framework. Secure collaborative, Smart structured data, human with agentic AI.
smartmerger.com MCP connector
The smartmerger.com MCP connector lets AI agents (for example Claude, ChatGPT, Microsoft Copilot, n8n, and custom enterprise agents) work with live deal data in smartmerger.com. Deal teams can ask in natural language and get answers grounded in their projects, playbooks, and workstreams—without copying spreadsheets into the chat.
What agents can help with
- Project overview — “Give me an overview of my projects.”
- Playbook intelligence — Summarise structure, tasks, Smart Fields, and workflow context for a workstream playbook.
- Workstream items — Risks, issues, findings, synergies, todos, and similar SmartTodo apps (where your tenant uses them).
- Diligence and review — Filter by status, assignee, or workstream; drill into nodes and linked apps.
- Communications context — Related comms on nodes or content (read; and create/update where your permissions allow).
- Workflow and reporting — Status models, history, curated reports, and playbook node reports for executive-style summaries.
How it works (governance)
- Access follows the same roles and permissions as the smartmerger.com web application for the authenticated identity / tenant key.
- Agents can read broadly where the user may read, and create or update only where the underlying APIs and roles allow (playbook nodes, todos, communications, Smart Field inputs, workflow status, and comments—subject to permission checks on the platform).
Tools (by area)
| Area | Examples |
|---|---|
| Identity & projects | get_current_user, list_projects |
| Playbooks | list_playbooks, get_playbook_content, get_playbook_node, search_playbook, get_playbook_report, get_playbook_nodes_report, get_smartfield_value_report, get_playbook_related_apps |
| Composite overview | get_project_status_snapshot |
| SmartTodo | list_todo_apps, list_todo_items, list_all_todo_items_by_client, list_todo_items_report, get_todo_item, create/modify items and comments where permitted |
| Communications | get_related_communications, get_comm_item, create/modify items and comments where permitted |
| Smart Fields | get_smart_fields, text/numeric input and field comments where permitted |
| Workflow | get_workflow_statuses, set_node_status, set_todo_status, get_status_history |
| Reporting | list_reports, get_report_data |
(Exact tool names match the MCP server description string: “projects, playbook, SmartTodo, communications, workflow, and reporting” — see McpServerInstructions.cs / SmartmergerTools.cs.)
How to connect
- Open your agent’s connector or custom MCP configuration.
- Connect smartmerger.com using the method you publish (for example OAuth via the connector, or tenant v2api key on each request for HTTP MCP—see your deployment guide).
- Access is limited to projects and data your account is allowed to see.
Security & compliance (verify with your legal/compliance team)
- TLS for traffic; hardened MCP host behaviour as documented in your MCP server README (HTTPS enforcement outside development, request size limits, no upstream error body leakage to clients).
- Scoped access to the authenticated user/tenant.
- [Optional, if formally approved] GDPR posture, subprocessors, region (e.g. Microsoft Azure EU)—only include sentences your DPA / privacy team has approved.
Requirements
- Active smartmerger.com subscription (or equivalent contractual access).
- Connector behaviour must match your actual auth model (OAuth vs API key).