Bring Property Listings
to Cursor
Learn how to connect AgentFire to Cursor and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the AgentFire MCP Server?
Connect your AgentFire account to any AI agent and take full control of your real estate website and automated lead capture workflows through natural conversation.
What you can do
- Lead Portfolio Orchestration — List and manage all captured property inquiries programmatically, retrieving detailed lead profile metadata and contact tags
- Web Engagement Intelligence — Programmatically monitor property clicks and access engagement metadata to coordinate your sales follow-up strategy
- Property Graph Monitoring — Access real-time updates for active listings and track user interaction duration directly through your agent for instant reporting
- Metadata Management — Programmatically retrieve interest signals and search history to maintain a perfectly coordinated CRM record
- Operational Monitoring — Verify account-level API connectivity and monitor lead capture volume directly through your agent for perfectly coordinated service scaling
How it works
1. Subscribe to this server
2. Retrieve your API Key from your AgentFire dashboard (Integrations > REST API)
3. Start orchestrating your real estate growth from Claude, Cursor, or any MCP client
No more manual logging into WordPress or missing critical property inquiries. Your AI acts as your dedicated marketing coordinator and real estate architect.
Who is this for?
- Real Estate Agents — instantly retrieve lead summaries and monitor property interest using natural language commands
- Marketing Leads — verify individual lead engagement and track web conversions without leaving your workspace
- Developers — integrate high-speed AgentFire data into custom automation workflows through simple AI queries
Built-in capabilities (10)
Verify AgentFire API connectivity
Email is required. Create a new lead
Get lead details
Get listing details
Get your AgentFire profile
List all contacts
List all leads
List all property listings
Search property listings
Only provided fields are changed. Update a lead
Why Cursor?
Cursor's Agent mode turns AgentFire into an in-editor superpower. Ask Cursor to generate code using live data from AgentFire and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
AgentFire in Cursor
AgentFire and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect AgentFire to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for AgentFire in Cursor
The AgentFire MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
AgentFire for Cursor
Every tool call from Cursor to the AgentFire MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my AgentFire API Key?
Log in to your AgentFire dashboard, navigate to Integrations > REST API, and copy your unique Access Token.
Can I see individual property clicks via AI?
Yes! The list_leads tool allows your agent to retrieve interest signals and property engagement metadata for all your contacts.
How do I list my active listings?
Use the list_listings tool to retrieve your complete directory along with the unique identifiers for all managed properties.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.