[cursor]

Unreviewed third-party submission. This PR came in through the plugin submission form and nobody has reviewed it yet. Do not merge before review.

Submission

• Publisher handle: attention
• Company: Attention
• Contact: Anis Bennaceur [email protected]
• plugin_url: https://github.com/attentiontech/attention
• Website (as submitted): attentio.com. This looks like a typo; the plugin source uses https://www.attention.com.
• Description (as submitted): Attention helps sales teams reach their full revenue potential.
• Listing targets: Grok Bot, Cursor

Testing instructions (from submitter)

1. Go to app.attention.tech
2. Log in with the test account the submitter provided.

The submission included a login email and password in plain text. I left both out of this PR because the repo is public. Get them from the original submission.

What this adds

• third_party/attention/, copied from the publisher's repo (https://github.com/attentiontech/attention):
  • mcp.json: the publisher's remote MCP server, https://api.attention.tech/mcp (HTTP, OAuth 2.0 with PKCE)
  • skills/conversations/SKILL.md
  • LICENSE (MIT)
  • .cursor-plugin/plugin.json with category integrations, "skills": "./skills/", and "mcpServers": "./mcp.json"
  • README.md with install steps and the MCP JSON block
• One entry appended to .cursor-plugin/marketplace.json and one row in the root README table. .claude-plugin/marketplace.json is unchanged.

Logo: missing, needs follow-up

No logo is committed, and plugin.json has no logo field yet.

• The submitted logo_url (https://drive.google.com/file/d/1ipEo11AfUMQl6LGEA58wGaKYsJNRLUUB/view?usp=sharing) could not be downloaded. Google Drive is not reachable from the build environment, and the link opens a viewer page, not an image file.
• Fallbacks also failed: attention.com, docs.attention.com, attention.tech, app.attention.tech, and the favicon services were all unreachable. The attentiontech repos contain no logo file. The GitHub org avatar is GitHub's auto-generated placeholder, not the company logo, so I didn't use it.
• Best URL found: the submitted Drive link above. A maintainer should download it, commit it as third_party/attention/assets/logo.png, and add "logo": "assets/logo.png" to plugin.json.

Validation

node scripts/validate-plugins.mjs passes.

  

---

Note

Low Risk
Additive marketplace manifest and docs only; no changes to core repo logic, though merge still depends on third-party MCP/OAuth review.

Overview
Adds the Attention third-party integration to the Cursor plugin marketplace so agents can reach Attention’s hosted MCP server for sales conversation intelligence.

The new third_party/attention/ package wires mcp.json to https://api.attention.tech/mcp (HTTP, OAuth 2.0 + PKCE with mcp:read / mcp:write), ships a conversations agent skill for search/transcripts/coaching workflows, and includes manifest, README, and MIT license. .cursor-plugin/marketplace.json and the root README plugin table gain an attention entry (author Attention, not Cursor). No logo is included in this diff.

Maintainers should treat this as an unreviewed publisher submission: verify the external MCP endpoint and publisher before merge; logo follow-up is noted in the PR description.

^{Reviewed by Cursor Bugbot for commit 3e59f6c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Grok Bot cannot connect Attention
  • Attention’s HTTP MCP entry omitted placement, so Grok Bot left the row undecided; mcp.json now sets placement to server so the hosted connect path can show a sign-in card.

Or push these changes by commenting:

@cursor push 3ae9f6cb50

Preview (3ae9f6cb50)

diff --git a/third_party/attention/mcp.json b/third_party/attention/mcp.json
--- a/third_party/attention/mcp.json
+++ b/third_party/attention/mcp.json
@@ -2,7 +2,8 @@
   "mcpServers": {
     "attention": {
       "type": "http",
-      "url": "https://api.attention.tech/mcp"
+      "url": "https://api.attention.tech/mcp",
+      "placement": "server"
     }
   }
 }

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 3e59f6c. Configure here.}

[cursor]

Grok Bot cannot connect Attention

Medium Severity · Logic Bug

The listing targets Grok Bot, but the Attention MCP server omits placement. On Grok Bot, HTTP MCP rows without placement set to server stay undecided and never show a connect or sign-in card, so Grok users cannot authenticate or use the plugin.

 

^{Reviewed by Cursor Bugbot for commit 3e59f6c. Configure here.}