Direct answer: Finta's Aurora catalog includes Make's MCP server at https://mcp.make.com with dynamic OAuth. Make documents tools for running active or on-demand scenarios and, on supported paid plans and scopes, working with scenarios, connections, webhooks, data stores, teams, and organizations.
This guide is for teams using Finta as relationship intelligence around a capital, investor, customer, or company-building workflow. Make remains the source system for its records. Aurora can use only the context and actions exposed to the connected account.
How the Make connection works
| Connection detail | Current Finta guidance |
|---|---|
| Classification | Catalog MCP |
| Configured endpoint | https://mcp.make.com |
| Authentication and transport | Provider OAuth through Aurora; Streamable HTTP |
| Source of truth | Make remains authoritative for provider records, permissions, and action results. |
| Human control | Review external communication, record changes, financial actions, publishing, deletion, and other consequential work before execution. |
What you can use it for
- Run an active or on-demand Make scenario that has been intentionally exposed to MCP.
- Supply the inputs defined by the scenario and retrieve its documented output.
- Inspect or manage supported Make resources when the connected plan and OAuth scopes allow it.
- Limit access to a selected organization or team and the scopes required for the workflow.
- Use precise scenario names, descriptions, inputs, and outputs to reduce unintended execution.
These uses summarize the current provider documentation and Finta catalog purpose. The exact tool inventory varies by provider version, plan, workspace, user permissions, region, and authorization scopes.
Relationship intelligence workflows for Make
Run an approved investor-research enrichment scenario
Outcome: Run only after approval and verify every destination the scenario changes.
- Select the exact active or on-demand Make scenario built for enrichment.
- Validate the target company or investor inputs and permitted data sources.
- Show the scenario name, inputs, expected outputs, and downstream writes to the owner.
- Run only after approval and verify every destination the scenario changes.
Human decision: Aurora does not inspect or guarantee every internal module side effect. The scenario owner must approve the scenario and its destinations.
Handoff an approved investor update
Outcome: Require human approval before a run with communication side effects.
- Choose a scenario that has been designed for the update handoff.
- Prepare the approved content, audience identifier, and source links.
- Confirm whether the scenario drafts, stores, or sends anything externally.
- Require human approval before a run with communication side effects.
Human decision: Do not describe the workflow as sending an update unless the exact connected scenario has been inspected and tested.
How to connect Make to Aurora
- In Make, identify the organization, team, and scenarios intended for Aurora.
- Ensure each callable scenario is active or on-demand and has clear MCP-facing inputs, outputs, and descriptions.
- In Aurora, open Apps and select Make, then authorize https://mcp.make.com.
- Choose only the OAuth scopes required for scenario execution or management.
- Confirm discovered scenarios and tools, then run a low-risk controlled scenario.
Open the official Finta apps directory to confirm the catalog entry before authorizing a provider account.
Permissions and approval boundary
A Make scenario can hide many downstream actions. Limit OAuth to the intended organization, team, scopes, and scenarios. Require approval before any run that sends communication, mutates CRM data, posts publicly, changes files, spends money, or triggers another automation.
Limitations to understand
- Scenario-run tools and management tools have different plan and scope requirements.
- Make's OAuth scenario call can time out while the scenario continues in the background.
- The outcome depends on each scenario's modules, inputs, connections, error handling, and current state.
- The catalog entry does not prove any specific Finta fundraising scenario is installed or tested.
Verification checklist
- Confirm endpoint, OAuth organization, team, scopes, plan, and exposed scenario inventory.
- Inspect each test scenario's modules, inputs, outputs, destinations, and side effects.
- Run one low-risk controlled scenario and retain Make execution and destination receipts.
- Test timeout behavior and confirm whether a timed-out call continues running.
- Record plan gates, unavailable management tools, and verification date before publication.
Verification status: On 2026-08-22, Finta confirmed that this connector appears in the enabled production Aurora catalog and reviewed the configured endpoint, authentication type, and first-party sources listed below. This is not a claim that every provider tool or an authenticated end-to-end action has been tested for every account.
Official provider sources
- Make official MCP documentation (developers.make.com)
- Make official MCP documentation 2 (developers.make.com)