Direct answer: Finta's Aurora catalog lists a bearer-authenticated Zapier MCP endpoint at https://mcp.zapier.com/api/mcp/v1/mcp. Zapier's current MCP product requires a user to create a server, connect app accounts, and explicitly choose the actions exposed as tools before an AI client can call them.
This guide is for teams using Finta as relationship intelligence around a capital, investor, customer, or company-building workflow. Zapier remains the source system for its records. Aurora can use only the context and actions exposed to the connected account.
Current connection note: Zapier expects each user to configure a personal MCP server and enabled actions. The page does not represent the catalog URL as a universal server or claim that all Zapier apps are enabled.
How the Zapier connection works
| Connection detail | Current Finta guidance |
|---|---|
| Classification | Catalog MCP |
| Configured endpoint | https://mcp.zapier.com/api/mcp/v1/mcp |
| Authentication and transport | User-supplied bearer or personal access token; Streamable HTTP |
| Source of truth | Zapier 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
- Expose only the Zapier actions and connected accounts selected by the server owner.
- Run a configured single action in a connected app after required inputs are supplied.
- Use Zapier's app catalog to bridge a reviewed Aurora handoff to an existing system.
- Keep each tool's name and description specific so Aurora can select it intentionally.
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 Zapier
Route an approved fundraising lead
Outcome: Run the action only after approval and verify the destination record.
- Configure one Zapier MCP action for the exact destination and account.
- Prepare the lead fields from verified Finta context.
- Show the destination, mapped fields, and action to the owner.
- Run the action only after approval and verify the destination record.
Human decision: A generic request to sync everything is not sufficient. The exact Zapier action, account, record, and field mapping must be approved.
Create an internal follow-up handoff
Outcome: Run the action and verify the resulting task or notification.
- Select a configured Zapier action for the team's task or notification system.
- Prepare a concise follow-up with source link, owner, and due date.
- Ask the owner to approve the external write.
- Run the action and verify the resulting task or notification.
Human decision: Do not send an investor email, post publicly, or create a high-impact record through an indirectly configured action without a clear human confirmation.
How to connect Zapier to Aurora
- In Zapier MCP, create or select a server and connect only the app accounts needed.
- Add the exact actions Aurora should be able to call and give each a specific description.
- Obtain the server connection URL and bearer credential without placing the secret in page content or prompts.
- In Aurora, select Zapier and complete the catalog bearer connection.
- Confirm discovered tools match the intended Zapier server before running a safe test action.
Open the official Finta apps directory to confirm the catalog entry before authorizing a provider account.
Permissions and approval boundary
Zapier can reach many third-party apps, so the security boundary is the configured server, connected account, selected actions, and bearer credential. Expose the minimum actions, protect the URL and token, and require approval before outbound communication, public posting, CRM mutation, payments, or other consequential writes.
Limitations to understand
- Zapier MCP exposes only actions explicitly added to the user's server; it is not automatic access to every Zapier app.
- Zapier documents action-oriented calls, not a guarantee of arbitrary multi-step or background automation from one MCP request.
- The catalog's shared-looking endpoint and bearer flow must be reconciled with the server-specific URL Zapier generates for the connected account.
- Tool behavior, fields, rate limits, and side effects depend on each configured app action.
Verification checklist
- Reconcile the catalog endpoint with the exact Zapier MCP server URL and bearer flow generated for the test account.
- Capture the server owner, connected apps, selected actions, and Aurora-discovered tools.
- Run one low-risk test action against a controlled destination and retain both source and destination receipts.
- Confirm no unapproved actions or accounts are exposed.
- Record action-specific fields, side effects, rate limits, 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
- Zapier official MCP documentation (docs.zapier.com)
- Zapier official MCP documentation 2 (docs.zapier.com)