Skip to content

Add Xquik MCP Cursor rule#317

Open
kriptoburak wants to merge 2 commits into
PatrickJS:mainfrom
kriptoburak:codex/add-xquik-mcp-rule
Open

Add Xquik MCP Cursor rule#317
kriptoburak wants to merge 2 commits into
PatrickJS:mainfrom
kriptoburak:codex/add-xquik-mcp-rule

Conversation

@kriptoburak

@kriptoburak kriptoburak commented Jun 20, 2026

Copy link
Copy Markdown

Summary

Adds a Cursor Project Rule for using the Xquik MCP server for public X/Twitter research. It documents the remote MCP config, says to call explore before xquik, and keeps write/account endpoints opt-in.

Contribution Type

  • New Cursor rule file or rules folder
  • Update/fix to an existing rule
  • New rules/*.mdc rule
  • Documentation or README cleanup

Value To Cursor Users

This gives Cursor users a reusable rule for current public X/Twitter research tasks without guessing social data. It points agents to the live MCP tool list and keeps collection narrow.

Added Or Changed Files

  • rules/xquik-mcp-x-research.mdc: New Cursor rule with setup and agent guardrails.
  • README.md: Adds the rule in Database and API.

Quality Checklist

  • The contribution includes original rule content, or clearly credits the source.
  • New rule files use a descriptive kebab-case filename, such as react-typescript.mdc.
  • New rules/*.mdc files include frontmatter with a non-empty description, relevant globs, and alwaysApply: false unless the rule is universal.
  • README links use canonical GitHub URLs for repo files and point to the correct category.
  • The text is neutral and useful, not sales copy.
  • This is not a standalone external tool, product, directory, marketplace, or service listing.
  • No secrets, credentials, affiliate links, tracking links, or unrelated product claims are included.
  • I checked for duplicate or near-duplicate existing entries.

Notes For Maintainers

Duplicate checks: target README/code search, PR search, and issue search returned no existing Xquik entry.

Validation run:

  • npm test
  • npm run check:awesome-list
  • npm run check:readme-hygiene
  • npm run check:rule-hygiene
  • npm run check:repo-security
  • git diff --check

Summary by CodeRabbit

  • Documentation
    • Added a new Cursor rule guide for using an Xquik MCP server to perform public X/Twitter research, including authentication, endpoint discovery steps, and constraints to keep requests read-only and results time-sensitive.
    • Updated the README under Database and API with a link and brief description for the new “Xquik MCP X Research” research capability documentation.

@coderabbitai

coderabbitai Bot commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f1145bb0-0d60-4505-b91e-e2a023581d41

📥 Commits

Reviewing files that changed from the base of the PR and between 8f7bfb9 and e81561d.

📒 Files selected for processing (1)
  • rules/xquik-mcp-x-research.mdc
✅ Files skipped from review due to trivial changes (1)
  • rules/xquik-mcp-x-research.mdc

📝 Walkthrough

Walkthrough

A new Cursor rule file rules/xquik-mcp-x-research.mdc is created, configuring the Xquik remote MCP server for public X/Twitter research with agent behavior constraints, tool selection guidance, and response formatting rules. A corresponding entry is added to README.md under the Database and API section.

Changes

Xquik MCP X Research Rule and Registration

Layer / File(s) Summary
Xquik MCP rule: metadata, setup, agent behavior, and response format
rules/xquik-mcp-x-research.mdc
Creates the full rule document: sets alwaysApply: false with a **/* glob, scopes applicable task types to public X/Twitter posts/profiles/trends, instructs enabling the streamable HTTP MCP server with Authorization: Bearer ${XQUIK_API_KEY}, mandates explore-first endpoint discovery, enforces read-only defaults, narrow query scoping, key non-leakage, exact error reporting, and defines post-call response formatting (lead with results, cite returned content, avoid extrapolating beyond returned fields).
README registration
README.md
Inserts a bullet for Xquik MCP X Research under the Database and API subsection, linking to the new rule file.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

Suggested reviewers

  • PatrickJS

Poem

🐇 A new rule hops into the repo today,
For searching X with MCP along the way.
Bearer tokens kept secret, explore run first,
Read-only by default — quench that research thirst!
The README now points to where the magic stays. ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Add Xquik MCP Cursor rule' clearly and specifically summarizes the main change—adding a new Cursor rule for the Xquik MCP server.
Description check ✅ Passed The PR description is comprehensive and addresses all required template sections: a clear summary, correct contribution type selections, practical value explanation, detailed file list, and a completed quality checklist with notes on validation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@rules/xquik-mcp-x-research.mdc`:
- Line 3: The glob pattern `globs: **/*` on line 3 is invalid YAML because the
`**` sequence is interpreted as an alias indicator, and the pattern is too broad
as it matches every file in every directory. Fix this by either properly quoting
the pattern as `'**/*'` if a universal pattern is truly needed, or better yet,
narrow it to specific file extensions relevant to the X/Twitter research rule
following the repository's documented format (e.g., patterns like **/*.ts,
**/*.tsx for TypeScript files). Refer to the repository's README for the correct
documented format for glob patterns in this rule file.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4ab986fc-f791-4b8b-8a39-0bff64e6a33c

📥 Commits

Reviewing files that changed from the base of the PR and between b044f95 and 8f7bfb9.

📒 Files selected for processing (2)
  • README.md
  • rules/xquik-mcp-x-research.mdc

Comment thread rules/xquik-mcp-x-research.mdc Outdated
@@ -0,0 +1,54 @@
---
description: "Use the Xquik MCP server for public X/Twitter research in Cursor."
globs: **/*

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

cat -n rules/xquik-mcp-x-research.mdc | head -20

Repository: PatrickJS/awesome-cursorrules

Length of output: 764


🏁 Script executed:

# Check YAML parsing with Python
python3 - <<'PY'
import yaml

# Test if unquoted **/* is valid YAML
test_cases = [
    "globs: **/*",
    "globs: '**/*'",
    "globs: \"**/*\""
]

for test in test_cases:
    yaml_str = f"---\n{test}\n---"
    try:
        result = yaml.safe_load(yaml_str)
        print(f"✓ Valid: {test} → {result}")
    except Exception as e:
        print(f"✗ Invalid: {test} → {e}")
PY

Repository: PatrickJS/awesome-cursorrules

Length of output: 761


🏁 Script executed:

# Check if there are other .mdc files to understand the glob pattern convention
find . -name "*.mdc" -type f | head -10

Repository: PatrickJS/awesome-cursorrules

Length of output: 553


🏁 Script executed:

# Check how other rules format their globs field
rg -A 3 "^globs:" rules/*.mdc | head -40

Repository: PatrickJS/awesome-cursorrules

Length of output: 2531


🏁 Script executed:

# Look for any documentation or schema about rule format
fd -e md -e txt -e json | xargs rg -l "globs|cursor.*rule" 2>/dev/null | head -10

Repository: PatrickJS/awesome-cursorrules

Length of output: 112


🏁 Script executed:

# Check if there's a README or docs explaining the format
ls -la | grep -i readme
cat README.md | grep -A 20 -B 5 "globs\|frontmatter" 2>/dev/null | head -40

Repository: PatrickJS/awesome-cursorrules

Length of output: 1761


Quote and narrow the glob pattern to match the documented format.

globs: **/* is invalid YAML (the ** is interpreted as an alias indicator) and too broad—it matches every file in every directory. According to the repository's README, the correct format specifies file extensions or patterns, like globs: **/*.ts, **/*.tsx. For an X/Twitter research rule, consider a scoped pattern (e.g., globs: **/* with proper quoting as '**/*' if truly universal, but narrower patterns are preferred) to ensure the rule only activates where intended.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@rules/xquik-mcp-x-research.mdc` at line 3, The glob pattern `globs: **/*` on
line 3 is invalid YAML because the `**` sequence is interpreted as an alias
indicator, and the pattern is too broad as it matches every file in every
directory. Fix this by either properly quoting the pattern as `'**/*'` if a
universal pattern is truly needed, or better yet, narrow it to specific file
extensions relevant to the X/Twitter research rule following the repository's
documented format (e.g., patterns like **/*.ts, **/*.tsx for TypeScript files).
Refer to the repository's README for the correct documented format for glob
patterns in this rule file.

@kriptoburak

Copy link
Copy Markdown
Author

Addressed the CodeRabbit glob note in e81561d by quoting the project-rule glob.

Validation rerun:

  • npm test
  • npm run check:awesome-list
  • npm run check:readme-hygiene
  • npm run check:rule-hygiene
  • npm run check:repo-security
  • git diff --check

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