Skip to content

Dual-publish Open Plugins 1.0.0 and list for Grok Bot - #20

Open
jesseoue wants to merge 2 commits into
mainfrom
feat/open-plugins-directory-scan
Open

jesseoue wants to merge 2 commits into
mainfrom
feat/open-plugins-directory-scan

Conversation

@jesseoue

Copy link
Copy Markdown
Contributor

Summary

  • Dual-publish Agent Plugins 1.0.0 (plugin.json + $schema on mcp.json) beside .cursor-plugin/ so cursor.directory Auto GitHub scan can detect skills/MCP without breaking Cursor Plugin CI.
  • mcp.json and .mcp.json are byte-identical OAuth HTTP: streamable-http to https://mcp.leadmagic.io/mcp, no keys, no extra servers.
  • Grok Bot Plugins is the same Cursor Marketplace listing: minClientVersions.grokbot 0.49.0, same first-run OAuth, no second login page.

Type Of Change

  • Documentation
  • Skills or rules
  • MCP config or metadata
  • Validation or GitHub automation

Validation

  • Ran npm test && npm run validate
  • Checked that copy matches the current hosted MCP surface
  • Verified no secrets or hardcoded API keys were added (no .env with real keys; see SECURITY.md)

Alignment Checklist

  • mcp.json still points to https://mcp.leadmagic.io/mcp
  • Default mcp.json stays OAuth-only (no headers; no API keys)
  • New or edited agents/*.md and commands/*.md include YAML frontmatter (name, description)
  • Repo copy does not imply MCP support for tools outside the current MCP surface
  • README and submission copy stay consistent

Test plan

Notes For Reviewers

Directory Auto scan reads GitHub main. Merge this PR before expecting a successful catalog detect of the new root manifest.

Add a root plugin.json plus identical OAuth mcp.json files so cursor.directory Auto GitHub scan can detect Agent Plugins 1.0.0 without breaking Cursor Plugin CI. Document the same marketplace listing and first-run OAuth for Grok Bot.
Drop supporting skills, duplicate .mcp.json, and unused docs. Keep four OAuth fronts, Open Plugins dual-publish, and one Hosted sign-in page for Cursor and Grok Bot.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant