fix-issue
Skill28k starsChanged 27 days agoApache-2.0View on GitHub
Carry a selected FastMCP bug from reproduction through a scoped fix, compatibility review, validation, and a monitored pull request.
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 49 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 16
Use python-tests. Reproduce the failure on unchanged code, confirm it fails for the right reason, then make the smallest causal fix.
- Distinctive: line 20
Run the repository's required dependency sync, full tests, and static checks before committing.
- Distinctive: line 30
Start review-pr monitoring after publication.
“Common” is measured: kept by at least 6 in 10 of the 49 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Fix a selected issue
Read AGENTS.md and the contribution policy in the development guide. Read the issue's full discussion, relevant history, and associated PRs in all states. Evaluate existing contributions before writing a competing fix; use review-issue when assignment is the next decision. Preserve contributor authorship when carrying existing work forward.
Establish the contract
Trace the public request to the failing operation. Confirm supported behavior is broken, not merely surprising. State the scope and compatibility boundary before implementation: which inputs must change, which adjacent behavior must remain, and any migration needed. If the intended contract is unresolved, bring that precise question to the maintainer.
Red, green, review
Use python-tests. Reproduce the failure on unchanged code, confirm it fails for the right reason, then make the smallest causal fix. Test explicit overrides and neighboring supported paths that share the changed branch. Avoid expanding the fix to unrelated standards gaps.
Self-review the full change with review-pr, including docs and dependency bounds. Separate necessary compatibility changes from accidental regressions and say whether a breaking change remains. Do not infer compatibility from passing tests.
Run the repository's required dependency sync, full tests, and static checks before committing. Honor branch and attribution conventions. If a required check fails, investigate and report evidence rather than hiding the failure.
Publish and follow through
Within existing authorization, update the existing PR or open a focused one, using draft status when appropriate. Follow repository PR-body conventions and the user's pr-body skill when available. Describe the actual user-visible change and any migration, not the development diary.
For a maintainer implementation of a community issue, apply Contributor credit before committing and publishing. Read the issue author's GitHub profile to establish their account identity; prefer the GitHub-provided noreply address, and ask if identity is unclear. Add their Co-authored-by: Name <email> trailer to the implementation commit and at the end of the PR description, alongside existing contributor attribution. Reporting the problem is enough; do not require code or root-cause analysis. Honor opt-outs and do not credit bot accounts as human issue contributors.
Maintainers are generally exempt from supplemental credit checks. For maintainer reports and routine backports, preserve existing community attribution and proceed; do not add a maintainer merely because they opened the original PR or ask for guidance on that basis. A backport does not need a fresh credit audit.
Start review-pr monitoring after publication. CI completion and review completion are distinct. Resolve real findings and report material compatibility decisions; a green check does not settle them. Do not merge or mark ready without authorization.
Trending
Steady talk.about the whole repository
Who's talking about PrefectHQ/fastmcp
- AI Engineering News“An AI Sent Police a Fake Murder Tip. Nobody Noticed for Two Months | AI Daily News, Oct 9”YouTube · Oct 9, 2026 · 4.3k views
- Github God“27K ⭐ AI NYAMBUNG KE SEMUA DATA KAMU”YouTube · Sep 10, 2026 · 1.1k views
- Prefect“Why LangChain Built Its MCP Support on FastMCP 4.0 | Sydney Runkle Interview”YouTube · Sep 28, 2026 · 941 views
- Prefect“FastMCP 4.0 Release | Meet Nate Nowack, New Lead Maintainer”YouTube · Sep 3, 2026 · 488 views
- Prefect“Your MCP Server is Bad (and you should feel bad) | Jeremiah Lowin, AI Engineer Code Summit 2025”YouTube · Feb 6, 2026 · 484 views
The biggest 5 of 76 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 76
Talked about on GitHub, YouTube, the web, Hacker News and Bluesky (76 times).
On GitHub · 50
- Mar 1, 2026refactor(mcp_server): migrate to FastMCP v3 and add OpenBB Code Mode — openbq-org/OpenBB5 reactions · 1 comment
- Jun 20, 2026ci(deps): bump the uv group across 3 directories with 9 updates — KooshaPari/AgilePlus3 reactions · 6 comments
- Jun 20, 2026ci(deps): bump the uv group across 3 directories with 9 updates — KooshaPari/AgilePlus3 reactions · 8 comments
- May 14, 2026Bump the uv group across 1 directory with 7 updates — GlacierEQ/Office-Word-MCP-Server3 reactions · 3 comments
- Oct 21, 2026build: Bump the python-dependencies group across 1 directory with 8 updates — cjangrist/omnifetch2 reactions · 2 comments
45 more on GitHub
- Oct 14, 2026build: Bump the python-dependencies group with 6 updates — cjangrist/omnifetch2 reactions · 3 comments
- Sep 23, 2026build: Bump the python-dependencies group across 1 directory with 3 updates — cjangrist/omnifetch2 reactions · 2 comments
- Sep 14, 2026deps(python)(deps-dev): bump the dev-dependencies group with 6 updates — SkyyRoseCo/DevSkyy2 reactions · 3 comments
- Sep 9, 2026build: Bump the python-dependencies group across 1 directory with 2 updates — cjangrist/omnifetch2 reactions · 2 comments
- Jul 20, 2026🔧 chore(deps): Bump the uv-production group across 1 directory with 2 updates — morzecrew/forze2 reactions · 4 comments
- Jul 17, 2026chore(deps): bump the pip group across 2 directories with 20 updates — CaffeeLake/MemOS2 reactions · 4 comments
- Jul 17, 2026chore(deps): bump the uv group across 2 directories with 20 updates — CaffeeLake/MemOS2 reactions · 4 comments
- Jul 15, 2026build: Bump the python-dependencies group across 1 directory with 5 updates — cjangrist/omnifetch2 reactions · 1 comment
- Jul 8, 2026build: Bump the python-dependencies group with 3 updates — cjangrist/omnifetch2 reactions · 2 comments
- Jul 1, 2026chore(deps): bump the uv group across 2 directories with 20 updates — CaffeeLake/MemOS2 reactions · 2 comments
- Jun 30, 2026chore(deps): bump the uv group across 1 directory with 17 updates — CaffeeLake/MemOS2 reactions · 2 comments
- Jun 24, 2026chore(deps): bump the pip group across 2 directories with 20 updates — CaffeeLake/MemOS2 reactions · 1 comment
- Jun 24, 2026chore(deps): bump the pip group across 2 directories with 6 updates — CaffeeLake/AP22 reactions
- Jun 18, 2026Bump the pip group across 1 directory with 2 updates — vzwjustin/Context-Engine2 reactions
- May 28, 2026chore(deps): bump fastmcp from 2.14.7 to 3.2.0 in /dispatch-mcp in the uv group across 1 directory — KooshaPari/AgilePlus2 reactions · 5 comments
- May 26, 2026chore(deps): bump the uv group across 1 directory with 9 updates — GlacierEQ/unity-mcp2 reactions · 2 comments
- May 26, 2026Bump the uv group across 1 directory with 12 updates — GlacierEQ/MiniMax-MCP2 reactions · 2 comments
- May 19, 2026Bump the uv group across 4 directories with 11 updates — HarleyCoops/OpenEnv2 reactions · 3 comments
- May 14, 2026chore(deps): bump the uv group across 1 directory with 10 updates — GlacierEQ/mcpm.sh2 reactions · 2 comments
- May 14, 2026Bump the uv group across 1 directory with 9 updates — GlacierEQ/mcp-server-qdrant2 reactions · 3 comments
- May 14, 2026chore(deps): bump the uv group across 1 directory with 7 updates — GlacierEQ/excel-mcp-server2 reactions · 3 comments
- Apr 21, 2026build(deps): bump the uv group across 16 directories with 3 updates — GlacierEQ/mcp-context-forge2 reactions · 1 comment
- Apr 11, 2026chore(deps): update fastmcp requirement from >=2.0 to >=3.2.3 in /python — KooshaPari/AgilePlus2 reactions · 6 comments
- Apr 1, 2026build(deps): bump the uv group across 15 directories with 1 update — GlacierEQ/mcp-context-forge2 reactions · 2 comments
- Apr 1, 2026Bump fastmcp from 2.14.3 to 3.2.0 — cicero-im/pydantic-ai2 reactions · 1 comment
- Apr 1, 2026Bump fastmcp from 2.14.1 to 3.2.0 — cicero-im/pyai-wealth-management2 reactions · 1 comment
- Apr 1, 2026build(deps): bump fastmcp from 2.13.2 to 3.2.0 — cicero-im/cuga-agent2 reactions · 2 comments
- Apr 1, 2026build(deps): bump fastmcp from 2.14.3 to 3.2.0 — cicero-im/logfire-assistant2 reactions · 1 comment
- Apr 1, 2026build(deps): bump fastmcp from 2.14.1 to 3.2.0 — cicero-im/pydantic-ai-todo2 reactions · 2 comments
- Apr 1, 2026chore(deps-dev): bump fastmcp from 2.14.4 to 3.2.0 in /python — cicero-im/mirascope2 reactions · 1 comment
- Apr 1, 2026chore(deps): bump fastmcp from 2.14.5 to 3.2.0 — cicero-im/mixseek-plus2 reactions · 1 comment
- Apr 1, 2026Bump fastmcp from 3.0.2 to 3.2.0 — cicero-im/pydantic-ai-skills2 reactions · 1 comment
- Apr 1, 2026Bump fastmcp from 2.3.4 to 3.2.0 — cicero-im/pydantic-ai-docs-server2 reactions · 1 comment
- Apr 1, 2026build(deps): bump fastmcp from 2.13.0.2 to 3.2.0 — cicero-im/pydantic-ai-temporal-example2 reactions · 2 comments
- Apr 1, 2026Bump fastmcp from 2.12.4 to 3.2.0 — cicero-im/jules-mcp-server2 reactions · 1 comment
- Apr 1, 2026Bump fastmcp from 2.12.4 to 3.2.0 — cicero-im/DeepCritical2 reactions · 1 comment
- Apr 1, 2026Bump fastmcp from 2.5.2 to 3.2.0 in /mcp3-serverhttp-test — cicero-im/mcppy2 reactions · 2 comments
- Apr 1, 2026build(deps): bump fastmcp from 3.0.2 to 3.2.0 — cicero-im/llmling-agent2 reactions · 2 comments
- Apr 1, 2026chore(deps): bump fastmcp from 3.0.0b1 to 3.2.0 in /scripts/mcp in the pip group across 1 directory — KooshaPari/Tracera2 reactions · 2 comments
- Mar 31, 2026chore(deps): bump fastmcp from 3.0.0b1 to 3.2.0 in the uv group across 1 directory — KooshaPari/Tracera2 reactions · 2 comments
- Mar 31, 2026chore(deps): bump the uv group across 2 directories with 3 updates — KooshaPari/AgilePlus2 reactions · 1 comment
- Mar 31, 2026build(deps): bump the pip group across 15 directories with 1 update — GlacierEQ/mcp-context-forge2 reactions · 1 comment
- Mar 26, 2026build(deps): bump the uv group across 15 directories with 1 update — GlacierEQ/mcp-context-forge2 reactions · 2 comments
- May 19, 2026_filter_to_supported_schema crashes with AttributeError: 'bool' object has no attribute 'items' when additionalProperties is a boolean — googleapis/python-genai1 reaction · 1 comment
- Mar 23, 2026[Feature]: OpenClaw MCP Server — Expose OpenClaw tools as Model Context Protocol tools for Claude/Cursor — openclaw/openclaw1 reaction · 1 comment
On YouTube · 21
- Oct 9, 2026An AI Sent Police a Fake Murder Tip. Nobody Noticed for Two Months | AI Daily News, Oct 9 — AI Engineering News4.3k views · 1 comment
- Sep 10, 202627K ⭐ AI NYAMBUNG KE SEMUA DATA KAMU — Github God1.1k views
- Sep 28, 2026Why LangChain Built Its MCP Support on FastMCP 4.0 | Sydney Runkle Interview — Prefect941 views · 2 comments
- Sep 3, 2026FastMCP 4.0 Release | Meet Nate Nowack, New Lead Maintainer — Prefect488 views · 2 comments
- Feb 6, 2026Your MCP Server is Bad (and you should feel bad) | Jeremiah Lowin, AI Engineer Code Summit 2025 — Prefect484 views
16 more on YouTube
- Jul 30, 2026Agent Tooling Is Eating GitHub 📈 #shorts — Coding Is Art445 views
- Sep 26, 2026FastMCP 4 Upgrade Guide: What Changed Since 2.0 — Tech Square Binary407 views
- Jul 22, 2026PrefectHQ/fastmcp — The standard way to build MCP. 🟢 Clone #Shorts — ForkCast377 views
- Mar 30, 2026Code Mode | MCP Dev Summit MCP — Prefect359 views · 5 comments
- Sep 4, 2026Is Your MCP Server Actually Good? FastMCP's Lead Maintainer Explains — Prefect313 views
- Jul 21, 2026Como crear servidores MCP para tu IA con Python paso a paso — lytohlg AI282 views
- Jul 8, 2026What the "C" in MCP Actually Means (Context, Explained) | FastMCP Pod: Summer School Ep. 2 — Prefect216 views · 4 comments
- Oct 17, 2026Acht Zeilen Code, und Claude kann mehr — Kris • AI2ROI215 views · 1 comment
- May 3, 2026One CLI, 55 AI models — Repo Radar193 views
- Sep 18, 2026This Python Library Builds MCP Servers in One Decorator — Agents on My Machine124 views
- Oct 4, 2026GPT-6 Astra Couldn't Beat a Human-Made StarCraft Bot. So It Used the Bot | AI Daily News, Oct 4 — AI Engineering News98 views
- Sep 10, 202627K ⭐ AI CONNECTS TO YOUR DATA — Github God Eng75 views
- Oct 6, 2026🚀 [Fastest Growing GitHub Repos] fastmcp: The Free Tool Taking Over GitHub! #shorts — githubrepo_cloud68 views
- Jul 25, 2026PrefectHQ/fastmcp - Gource visualisation — Gourcer66 views
- Oct 6, 2026Easier MCP Server Dev with fastmcp #Shorts — developerOS India36 views
- Sep 7, 2026How MCP Actually Works: Following One Request on the Wire — The System Prompt34 views · 1 comment
On the web · 3
- Feb 22, 2026Add v3.0.2 release notes · PrefectHQ/fastmcp@e19f239 — google.com
- Aug 13, 2025Introduce fastmcp.json · Issue #1480 — google.com
- Apr 24, 2025How to call a single resource template? #239 — google.com
On Hacker News · 1
- Apr 26, 2026Supabase Auth and FastMCP Example2 points · 1 comment
On Bluesky · 1
- Jul 20, 2026📦 PrefectHQ / fastmcp ⭐ 26,366 (+77) 🗒 Python 🚀 The fast, Pythonic way to build MCP servers and clients. — @github-trending.bsky.social1 likes and repost
Other versions52 projects use a version of this.
Word for word · 1
- jlowin/fastmcp★ 28k100% same
Edited · 0
None found.
Wrote their own version · 51
- pytorch/pytorch★ 105ksame name
- ZhuLinsen/daily_stock_analysis★ 67ksame name
- Dokploy/dokploy★ 38ksame name
- remix-run/remix★ 33ksame name
- NVIDIA-NeMo/Speech★ 19ksame name
- NVIDIA-NeMo/NeMo★ 19ksame name
- getsentry/sentry-javascript★ 8.8ksame name
- datlechin/TablePro★ 6.3ksame name
- TableProApp/TablePro★ 6.3ksame name
- docker/docs★ 4.7ksame name
41 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use document, write-tests and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nicolasestremSkilldocument
Create focused documentation for specific components or features
Also in 4 projects that use this
SentrySkillwrite-tests
Write tests following project conventions. Use when adding new tests or modifying existing ones.
Also in 4 projects that use this
ShopifySkillprepare-release
Prepare the changeset-release/main branch for release by syncing version.ts files and running pnpm install
Also in 3 projects that use this
GitHubSkillrefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Also in 5 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 6 projects that use this
Microsoft AzureSkillbuild
Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.
Also in 4 projects that use this
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/core-mcp-objects.mdcCursor rule
- docsSkill
- python-testsSkill
- releaseSkill
- review-issueSkill
- review-prSkill
- review-security-reportSkill
- triageSkill
- fastmcp-client-cliSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

