The card has no skills or MCP server. It requires Grok Bot 0.49 and is never allowed in Cursor, so the backend can handle the connection itself.
Co-authored-by: Alex Vandak Maloney <maloney.a12@gmail.com>
Register the Microsoft Teams and SharePoint REST-MCP endpoints the same way Outlook is wired, so they can be installed from the marketplace.
Co-authored-by: Cursor <cursoragent@cursor.com>
Package Hunter's hosted Streamable HTTP MCP server
(https://mcp.hunter.io/mcp) using the official Cursor setup from
https://hunter.io/agents.md: X-API-Key with ${HUNTER_API_KEY}.
This is a fresh-from-main take on #317, which used OAuth-only config
and documented the API key as an opt-in alternative. Official Cursor
packaging is header auth, so plugin.json declares the HUNTER_API_KEY
template variable the same way other BYO-credential plugins do.
Co-authored-by: Sam Sokolin <SamSokolin@users.noreply.github.com>
Adds an Advisor plugin: the main model consults a stronger model before
major decisions, when stuck on an error, and before declaring a task done.
The advisor gets a full briefing plus the conversation transcript path,
returns a verdict with guidance, and the main model keeps doing the work.
The default advisor is the latest Grok (Grok 4.6) at its highest reasoning
effort; /advisor <model> accepts any model available to subagents.
- skill `advisor`: /advisor [model|off|status|ask ...|nudge on|off],
checkpoint protocol, briefing template, usable as a Custom Mode
- agent `advisor-subagent`: read-only, pinned to grok-4.6[effort=xhigh]
- hooks: track edits since the last consult, log consults to
.cursor/advisor/log.md, nudge a pre-completion consult once per batch
of edits; state is bound to the conversation that enabled it
- registered in marketplace.json and the root README
New plugin, separate from the existing X plugin, pointing at X's hosted
ads MCP server (https://ads-api.x.com/mcp). Auth is per protected
resource: ads-api.x.com advertises its own OAuth metadata and scopes
(ads.read, ads.write), so it cannot share the X plugin's authorization
even though it reuses the same OAuth client ID.
Co-authored-by: Cursor <cursoragent@cursor.com>
Both take a user-supplied server URL rather than a fixed endpoint, since
neither vendor publishes a shared one. Deferring them so the rest of the batch
can land on its own; the research and README copy are easy to restore when we
pick them back up.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Xero publishes no hosted MCP endpoint; its official server is the `@xeroapi/xero-mcp-server` npm package running locally over stdio with Custom Connection credentials, and Xero's FAQ records Cursor as one of the two clients it tested against.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
ActiveCampaign generates a Remote MCP URL per account rather than publishing a shared endpoint, so the plugin takes the URL as a variable the way the Salesforce plugin does.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Zoho MCP has no shared endpoint — each customer builds a server in the Zoho MCP console and gets a region-specific URL with an embedded API key, so the plugin takes the URL as a variable the way the Salesforce plugin does.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Similarweb's hosted MCP server speaks Streamable HTTP but authenticates with a user-supplied token rather than OAuth, so the plugin declares a variable and forwards it as an HTTP header.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Readwise ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Mem ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Craft ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Fathom ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Otter.ai ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Fireflies ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Guru ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Coda ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Wrike's hosted MCP server speaks Streamable HTTP but authenticates with a user-supplied token rather than OAuth, so the plugin declares a variable and forwards it as an HTTP header.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Smartsheet's hosted MCP server speaks Streamable HTTP but authenticates with a user-supplied token rather than OAuth, so the plugin declares a variable and forwards it as an HTTP header.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Calendly ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Todoist ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Mercury ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Brex ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Workable ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Upwork ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
GoDaddy's hosted MCP server serves public data with no authentication, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Ahrefs ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Semrush ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Jotform ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Typeform ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Brevo's hosted MCP server speaks Streamable HTTP but authenticates with a user-supplied token rather than OAuth, so the plugin declares a variable and forwards it as an HTTP header.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
MailerLite ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Customer.io ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Klaviyo ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Roshan Sadanani <roshansada@users.noreply.github.com>
Amplemarket ships an official remote MCP server over Streamable HTTP with per-user OAuth, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Cursor <cursoragent@cursor.com>
Outreach ships an official remote MCP server over Streamable HTTP with per-user OAuth 2.1 and dynamic client registration, so the plugin is a URL-only mcp.json with no variables block.
Co-authored-by: Cursor <cursoragent@cursor.com>
Minu Palaniappan