What is minimax-mcp-tools?

A guide for retrieving current documentation and using external tools. It explains when to prefer built-in tools, plugins, MCP resources, or web search, especially for version-sensitive information.

Use it when package versions, breaking changes, compatibility, framework behavior, official documentation, or external systems affect the task.

It reduces errors caused by outdated documentation or assumed tool interfaces and encourages checking authoritative sources before calling something current or recommended.

minimax-mcp-tools — Cursor rule for Cursor by madebyaris

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/madebyaris/advance-minimax-m3-cursor-rules

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/minimax-mcp-tools/github.svg)](https://agentmods.dev/rules/madebyaris/advance-minimax-m3-cursor-rules/minimax-mcp-tools)

Your own site

<a href="https://agentmods.dev/rules/madebyaris/advance-minimax-m3-cursor-rules/minimax-mcp-tools"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/minimax-mcp-tools/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/rules/madebyaris/advance-minimax-m3-cursor-rules/minimax-mcp-tools"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/minimax-mcp-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 482 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00027	$0.00482
Opus 5	$0.00014	$0.00241
Sonnet 5	$0.00005	$0.00096
Haiku 4.5	$0.00003	$0.00048

Measured 12d ago against content hash b4c91791676f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

minimax-mcp-tools scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/minimax-mcp-tools.mdc · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MCP and Web Tools

Use this rule when current documentation, external systems, or plugin-backed tools matter.

Preferred Order

When multiple paths exist, prefer:

direct native tools exposed in the prompt
direct plugin or MCP-backed tools exposed in the prompt
MCP resource functions when available
MCP Apps structured content when returned by a tool
WebSearch and WebFetch

Do not assume old wrapper APIs are present just because they appear in older docs or rules.

Web Search Discipline

Use WebSearch for:

package versions
breaking changes
compatibility questions
recent framework behavior
error messages after repeated failures

Use WebFetch for:

official docs pages
changelogs
reference pages that need close reading

Before presenting advice as current, official, recommended, or best practice, verify it against a current authoritative source such as official docs, release notes, or changelogs.

When versions matter:

use the actual current month and year
do not leave placeholders in the search query
do not rely on stale memory when a current source is available

MCP Discipline

Follow the exact schema of currently exposed tools.
If the environment exposes direct tools, use them directly.
If the environment exposes resources instead of actions, use the resource discovery and fetch path.
If a tool returns MCP Apps structured content, use the structured form rather than the prose form.
Keep assumptions about server names and tool IDs out of general rules.

Typical Chains

Version check -> install or configure -> verify
Docs lookup -> implement -> behavior check
Resource discovery -> targeted fetch -> synthesize
Visual diff -> grounded report

For version-sensitive setup guidance, prefer:

Current authoritative source -> install or configure -> executable verification

Failure Handling

If an MCP or plugin call fails:

re-check the current schema
simplify the arguments
remove stale placeholder text
fall back to another available source if the integration is optional
if the tool returned structured content, check whether the prose view missed a useful field

Read the full file on GitHub · 74 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 74 lines · 27 tokens per session scan A b4c91791676f

Subscribe to this mod's changes

minimax-mcp-tools is a cursor rule published in the GitHub repository madebyaris/advance-minimax-m3-cursor-rules (125 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 482 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code Generation agentic-ai ai-coding ai-workflow cursor cursor-ide

git-commit

Use this when the user asks for a git commit, commit message, or commit command.

kyungseo/ai-workflow-harness · 18 tokens

learnship

Activate learnship agentic engineering workflows — structured phases, persistent memory, learning partner, and impeccable UI design. Use whenever a user is working on a software project or asks about project planning, phases, workflows, or how to build something.

FavioVazquez/learnship · 48 tokens

minimax-mcp-tools