mcp-server-patterns
v0.1.0by hetaoBackend · author: Hylouis233
Reference patterns for designing, evaluating, integrating, and debugging MCP servers without changing the active MCP configuration.
Package we checked
The manifest we fetched is plugins/Hylouis233/mcp-server-patterns/plugin.json in hetaoBackend/MiniMax-Code-Plugins. The plugin root is the directory that holds that file. Its $schema is https://agent-plugins.org/schemas/1.0.0/plugin.schema.json. The manifest lists 1 skill (mcp-server-patterns) and no MCP servers.
What mcp-server-patterns does, in the publisher's words
Teams adopting MCP (Model Context Protocol) servers keep hitting the same failure classes: duplicated servers that re-wrap capability the host already has, tools with unclear read/write boundaries, missing auth documentation, and debugging sessions that cannot tell transport failure from application failure. The knowledge to prevent this exists, but it is rarely written down where the agent can use it at decision time.
This Plugin installs one reference Skill: checklists and questions for evaluating, designing, integrating, and debugging MCP servers. It is guidance only: it never changes MCP settings.
Expected result: the agent walks the evaluation questions (does it beat direct tools, read-only or mutating, auth model, what data leaves the machine, overlap with existing servers), states a recommendation, and names the failure modes to expect.
From the project README, punctuation lightly normalized · Open the README on GitHub
- Skills
- 1
- MCP servers
- 0
- Stars
- 10
- License
- Apache-2.0
- Repo created
- 2026-08-14
- Last pushed
- 2026-09-07
- Publisher type
- User
- Version
- 0.1.0
Links
Skills · 1
- mcp-server-patterns
- Reference patterns for designing, evaluating, integrating, and debugging MCP servers. Use this Skill whenever the task involves deciding whether to add an MCP server, reviewing a server design, integrating one into a workflow, or diagnosing why one fails.
Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.
Category
Agent Tooling. Assigned by this directory. Agent Plugins 1.0.0 has no category field, so no manifest declares one.
Keywords
minimax-code · plugin · mcp · reference · design-review
Related by publisher and keywords
Skills for managing Dida365 (滴答清单, China) tasks, lists, habits, focus records and countdowns through the official Dida365 MCP server, which you add yourself in your client's MCP settings.
Skills for managing TickTick (international) tasks, lists, habits, focus records and countdowns through the official TickTick MCP server, which you add yourself in your client's MCP settings.
Enforce a search-before-edit workflow: locate relevant files, symbols, call sites, and surrounding context before proposing or making code changes.
Enforce a claim-to-proof workflow: define the evidence, run the right verification, and distinguish verified results from assumptions before declaring work complete.
Nine local-first scientific research Skills for ideation, hypotheses, study design, statistics, uncertainty, writing, peer review, and scholarly evaluation.
Search, discover, summarize and audit GitHub through the gh CLI: find repos about a topic, map a field landscape, trending, repo overviews, similar projects, code search, issue/PR search and org audits, backed by 9 zero-config Python scripts with relevance ranking and quota-aware searching. Read-only by default; opt-in write management (repos/issues/PRs/workflows/secrets/releases plus auth/config and gh api mutations) requires target, impact and minimal-data disclosure plus explicit user confirmation before execution. Honours GH_HOST (defaults to github.com; routes all API traffic to e.g. *.ghe.com GitHub Enterprise Cloud or github.acme.com GitHub Enterprise Server: credentials do not cross hosts, GH_TOKEN/GITHUB_TOKEN applies to github.com+*.ghe.com only, GHES on-prem requires GH_ENTERPRISE_TOKEN, and the skill does not validate the target).
[](https://agentpluginsdirectory.com/plugins/mcp-server-patterns)✓ Verified . We fetched the manifest from GitHub and checked it against the official Agent Plugins 1.0.0 schema at agent-plugins.org.