How to integrate Unify with Cursor
To integrate Unify with Cursor, install Unify’s official plugin from a team marketplace or use the individual setup path in Unify’s documentation. Restart Cursor, enable the plugin, and sign in to Unify. Use the connection when an operations or development task needs current account context and a traceable sales action.[1][3]
- Connection
- Official MCP
- AI assistants
- Tool
- Cursor
- Unify-documented client setup
- Data flow
- Cursor ↔ Unify
- Tool calls and returned results
At a glance
- Use the Unify-documented Cursor setup
- Use tool calls and returned results instead of an outbound Play payload
- Check the final Agent result before treating the task as complete
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
An internal sales tool can be technically correct while relying on the wrong account assumptions. Cursor provides a place to develop the interface or process, while the Unify connector supplies requested business context. Keep the research run distinct from application changes. That lets the operator review what informed the implementation without assuming that connecting the plugin deployed anything.
A good fit when
Teams building internal GTM tooling in Cursor and wanting access to Unify research and account context in their development workflow.
Reconsider the plan when
Unify documents a team marketplace route and a user-local setup script. The Cursor administrator can restrict local imports; a missing plugin may be an access-policy issue.
Design the handoff
Use this framework to agree on the input, the next action, and who owns the result.
Suggested workflow design, based on the documented capabilities below.
| Stage | Decision to make |
|---|---|
| Client and account | Cursor with team marketplace access or permission to import a user-local plugin |
| First task | Suggested prompt: “Use Unify to research example.com and list the facts relevant to our account-review interface. Keep product assumptions separate from research findings. Do not update live records.” |
| Execution | Define whether the request is research-only or includes a specific authorized action. Keep the run ID for follow-up. |
| Result | Review the final output and unresolved questions before using the result in a sales decision. |
Explore the scenarios
Choose the situation that fits your team and work through the proposed plan.
Open a scenario to explore its plan. Checklists track your selections in this page only.
Ground an internal account-review tool
A developer needs realistic business context before deciding what an internal interface should show.
Use Unify research to inform the design without presenting proposed fields as measured facts.
- Choose a controlled account-review question
- Read the completed Unify research
- Separate observed facts from proposed interface behavior
Make the team connection repeatable
Several operators need the same supported Unify plugin in Cursor.
Standardize installation while preserving each person’s own Unify authorization.
- Have an administrator add the official marketplace
- Install the plugin for an eligible user and restart
- Confirm that user’s workspace and tool access
Illustrative workflow, not a preconfigured automation. Complete these checks in your own account.
Define success before launch
Inspect the data and the intended outcome separately. Connection status is only the first check.
Expected, not tested
After the connection is authorized, Cursor can identify the intended Unify user and retrieve the completed output of the controlled research task.
Inspect get_me, the requested task, the final run status, and read_agent_results together. A discovered tool or a run ID confirms a different stage from a completed result. For any explicitly requested write, inspect the actual destination record as well.
Documentation-based reference. This workflow has not been tested end to end. Use a record or event you control before enabling live activity.
Questions answered
Common decisions when connecting Unify and Cursor.
How do I connect Unify to Cursor?
For a team marketplace, ask the Cursor administrator to add unifygtm/agent-plugins. Then find Unify in Settings → Plugins and install it. For an individual installation, follow the official setup script linked in Unify’s guide.[1][3]
Do I need a Cursor team marketplace to use Unify?
Unify documents both an administrator-managed team marketplace and an individual local setup script. Local imports must be allowed by your Cursor organization.[1][2][3]
How is MCP different from a Play webhook?
An MCP client can invoke Unify tools and retrieve their documented results. The Play Webhook action sends an external request and does not pass its response into downstream Play steps. They are separate connection mechanisms.[2][5]
Does a run ID mean the task succeeded?
No. run_agent starts background work. Check the run with poll_agent, handle any clarification, and call read_agent_results after the run reaches READY or ERROR.[2]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
- Unify documents a team marketplace route and a user-local setup script. The Cursor administrator can restrict local imports; a missing plugin may be an access-policy issue.[1][3]
- Unify permissions and Agent usage limits still apply[1][2]
- A completed research result does not itself authorize sending, enrollment, or CRM updates
- No authenticated end-to-end execution has been performed
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + Cursor workflow.
The assistant requests work from Unify and retrieves its result using the connected user’s permissions.
| Decision | What to know |
|---|---|
| Connection route | Unify explicitly documents Cursor setup[1] |
| Client requirement | Cursor with team marketplace access or permission to import a user-local plugin[1][3] |
| Published server | https://mcp.unifygtm.com/mcp (authentication required)[4] |
| Identity | Calls are scoped to the authenticated Unify user and tenant[2] |
| Agent lifecycle | Start a run, poll status, answer clarification, and read the terminal result[2] |
| Usage | Unify MCP Agent work uses existing Unify Chat usage and credits[1] |
MCP exposes tool schemas to the client. For Agent work, provide a natural-language prompt and retain the returned runId for status and result calls. Direct API tools have their own required inputs. This connection is separate from a Play’s outbound Webhook action and does not make webhook responses available to later Play steps.
Technical setup reference
References and requirements for the Cursor connection.
Connection requirements and setup checklist
Before connecting
- Cursor with team marketplace access or permission to import a user-local plugin
- A Unify user with access to the intended workspace and available Chat credits for Agent runs
- One controlled research task with a clear output and explicit boundaries on record changes
Restart and enable Unify
Fully restart Cursor, then enable and sign in to Unify from Settings → Plugins. If a local installation is missing, confirm that user-local imports are allowed.[1]
Scope the first task
Request the connected identity, then provide one account question and the intended output. State whether the task is research-only or includes an explicitly requested record change.[2]
Check the Agent result
For Agent work, run_agent returns a runId before the task finishes. Poll that run. Answer every returned question if its status is CLARIFICATION_NEEDED. On READY, read_agent_results returns the completed output; on ERROR, inspect the reported failure.[2]
Troubleshooting
Start with the stage where the expected data or action stops appearing.
The client cannot find or authorize Unify
Check the official installation path for this client, workspace policy, and required account connection. Restart clients where Unify’s setup calls for it, then repeat sign-in.[1][3]
A run starts but no result appears
Keep the original runId and poll its status. PENDING is still running; CLARIFICATION_NEEDED requires answers; READY permits reading the result. Use list_agent_runs to find a previous run rather than starting duplicate work.[2]
The tool reports missing access or unavailable credits
Verify the connected user and workspace. Unify scopes tools to that user, and Agent runs require available Chat funding and are subject to rate limits. A table owned by another user is not accessible through load_datatable.[2]
Sources & review
Official documentation reviewed on September 16, 2026.
Technical claims link to primary documentation from Unify and the destination tool. Scenarios, field choices, and recovery plans are editorial implementation examples. Documentation review is separate from execution testing.
Documentation reviewed; end-to-end execution not tested. No named technical reviewer has signed off on these articles yet.
Content updated: . Report a correction to Unify with the tool name, source URL, and behavior you observed.
Keep exploring
