Find local businesses, research companies, and discover decision-maker contacts from Cursor. Openmart distinguishes physical business locations from brands, so you can ask for independent stores or multi-location companies and get the appropriate results.
This plugin connects to Openmart's hosted MCP server and includes five skills: onboarding, business discovery, company research, contact enrichment, and contact exclusions. It requires an Openmart account and an active team.
For local installation before Marketplace approval:
- Clone or download this repository.
- Copy the plugin directory to
~/.cursor/plugins/local/openmart. The.cursor-plugin/plugin.json,mcp.json, andskills/directory must be inside that directory. Do not use a symlink to a directory elsewhere. - Reload Cursor and open Customize. Confirm that the Openmart plugin and its MCP server are present. Your organization may need to permit local plugin imports.
- Connect the Openmart MCP server and complete sign-in in your browser. Select your Openmart team and review the requested permissions.
- Ask: “Check my Openmart connection and credit balance. Do not run a paid search.”
No Openmart API key or client secret is required. The OAuth client ID in mcp.json is a public identifier, not a credential. The desktop sign-in callback uses http://localhost:8787/callback; the web callback uses https://www.cursor.com/agents/mcp/oauth/callback. Keep Cursor open while authenticating.
- “Find three independent coffee shops in Austin, Texas, with websites. Show their locations and save the results.”
- “For only the first shop in those results, find one owner work email if available. Do not enrich phone numbers.”
- “Check the progress of that contact lookup, then export the completed results as CSV.”
Searches and contact enrichment may consume your selected team's existing Openmart credits. A row limit controls the scope of work; it is not a guaranteed spending cap. Check the balance first. Contact work may run asynchronously: retain the operation reference and check its status instead of resubmitting the request. Reading existing operation status and exporting saved results do not start a new paid search.
The server also returns an interactive MCP App for supported clients. Text and structured results remain available when a client does not render the card. File download behavior depends on the Cursor surface. Refer to selected businesses by name or row when using chat instead of card controls.
The plugin sends the filters, company identifiers, selected results, or explicit exclusion changes needed for your request to https://api.openmart.ai/mcp. Openmart returns business data, contact results, and operation status for the authorized team. Contact enrichment and exclusion management require the relevant optional permissions. The plugin does not require access to your source repository or upload your workspace files as part of its configuration.
To revoke access, open Openmart Settings → Connected apps. Revocation also removes saved plugin results associated with that connection. Reconnect through Cursor if authorization expires. Never paste passwords, API keys, or access tokens into chat.
The five skills and icon are copied without changes from Openmart's released OpenAI plugin 0.2.5. This repository adds a Cursor manifest, a separate public OAuth client, and Cursor installation instructions. OpenAI and Claude releases continue to use their own packages and OAuth clients; the hosted MCP implementation is shared.
Before publishing a release, validate the package and test a fresh Cursor installation: sign-in, account status, a small business search, one selected contact lookup, asynchronous polling, export, and revocation. Verify the actual card on its first load, without using Retry. Use an isolated review team and explicitly bound any paid work. Do not include review credentials or tokens in this repository.