Update repository references for transfer to prefecthq

.github/workflows/martian-triage-issue.yml

@@ -10,7 +10,8 @@ on:
 jobs:
   triage:
     if: |
-      contains(fromJSON('["jlowin", "strawgate"]'), github.event.issue.user.login)
+      github.event.issue.user.login == 'strawgate' ||
+      (github.event.issue.user.login == 'jlowin' && contains(toJSON(github.event.issue.labels.*.name), 'bug'))
     concurrency:
       group: triage-issue-${{ github.event.issue.number }}
       cancel-in-progress: true
@@ -166,8 +167,8 @@ jobs:
 
             | Repository | Issue or PR | Relevance |
             | --- | --- | --- |
-            | jlowin/fastmcp | [Add matrix operations support](https://github.com/jlowin/fastmcp/pull/680) | This pull request directly addresses the feature request for adding matrix operations to the calculator. |
-            | jlowin/fastmcp | [Add matrix operations support](https://github.com/jlowin/fastmcp/issues/681) | This issue directly addresses the feature request for adding matrix operations to the calculator. |
+            | prefecthq/fastmcp | [Add matrix operations support](https://github.com/prefecthq/fastmcp/pull/680) | This pull request directly addresses the feature request for adding matrix operations to the calculator. |
+            | prefecthq/fastmcp | [Add matrix operations support](https://github.com/prefecthq/fastmcp/issues/681) | This issue directly addresses the feature request for adding matrix operations to the calculator. |
             </details>
 
             <details>

README.md

@@ -17,10 +17,10 @@
 [![Docs](https://img.shields.io/badge/docs-gofastmcp.com-blue)](https://gofastmcp.com)
 [![Discord](https://img.shields.io/badge/community-discord-5865F2?logo=discord&logoColor=white)](https://discord.gg/uu8dJCgttd)
 [![PyPI - Version](https://img.shields.io/pypi/v/fastmcp.svg)](https://pypi.org/project/fastmcp)
-[![Tests](https://github.com/jlowin/fastmcp/actions/workflows/run-tests.yml/badge.svg)](https://github.com/jlowin/fastmcp/actions/workflows/run-tests.yml)
-[![License](https://img.shields.io/github/license/jlowin/fastmcp.svg)](https://github.com/jlowin/fastmcp/blob/main/LICENSE)
+[![Tests](https://github.com/prefecthq/fastmcp/actions/workflows/run-tests.yml/badge.svg)](https://github.com/prefecthq/fastmcp/actions/workflows/run-tests.yml)
+[![License](https://img.shields.io/github/license/prefecthq/fastmcp.svg)](https://github.com/prefecthq/fastmcp/blob/main/LICENSE)
 
-<a href="https://trendshift.io/repositories/13266" target="_blank"><img src="https://trendshift.io/api/badge/repositories/13266" alt="jlowin%2Ffastmcp | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a>
+<a href="https://trendshift.io/repositories/13266" target="_blank"><img src="https://trendshift.io/api/badge/repositories/13266" alt="prefecthq%2Ffastmcp | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a>
 </div>
 
 ---

SECURITY.md

@@ -11,6 +11,6 @@ FastMCP v2.x receives security updates. Earlier versions are no longer supported
 
 ## Reporting a Vulnerability
 
-Please report security vulnerabilities privately using [GitHub's security advisory feature](https://github.com/jlowin/fastmcp/security/advisories/new).
+Please report security vulnerabilities privately using [GitHub's security advisory feature](https://github.com/prefecthq/fastmcp/security/advisories/new).
 
 Do not open public issues for security concerns.

docs/clients/sampling.mdx

@@ -168,5 +168,5 @@ client = Client(
 Tool execution happens on the server side. The client's role is to pass tools to the LLM and return the LLM's response (which may include tool use requests). The server then executes the tools and may send follow-up sampling requests with tool results.
 
 <Tip>
-To implement a custom sampling handler, see the [handler source code](https://github.com/jlowin/fastmcp/tree/main/src/fastmcp/client/sampling/handlers) as a reference.
+To implement a custom sampling handler, see the [handler source code](https://github.com/prefecthq/fastmcp/tree/main/src/fastmcp/client/sampling/handlers) as a reference.
 </Tip>

docs/community/showcase.mdx

@@ -47,7 +47,7 @@ Discover exemplary MCP servers and implementations created by our community. The
 
 ### Community Examples
 
-Have you built something interesting with FastMCP? We'd love to feature high-quality examples here! Start a [discussion on GitHub](https://github.com/jlowin/fastmcp/discussions) to share your project.
+Have you built something interesting with FastMCP? We'd love to feature high-quality examples here! Start a [discussion on GitHub](https://github.com/prefecthq/fastmcp/discussions) to share your project.
 
 ## Contributing
 
@@ -56,7 +56,7 @@ To get your project featured:
 1. Ensure your project demonstrates best practices
 2. Include comprehensive documentation
 3. Add clear usage examples
-4. Open a discussion in our [GitHub Discussions](https://github.com/jlowin/fastmcp/discussions)
+4. Open a discussion in our [GitHub Discussions](https://github.com/prefecthq/fastmcp/discussions)
 
 We review submissions regularly and feature projects that provide value to the FastMCP community.
 

docs/development/contributing.mdx

@@ -54,7 +54,7 @@ To contribute to FastMCP, you'll need to set up a development environment with a
 
 ```bash
 # Clone the repository
-git clone https://github.com/jlowin/fastmcp.git
+git clone https://github.com/prefecthq/fastmcp.git
 cd fastmcp
 
 # Install all dependencies including dev tools

docs/development/tests.mdx

@@ -49,7 +49,7 @@ async def test_github_api_integration():
 
     # Test against real GitHub API
     client = GitHubClient(token)
-    repos = await client.list_repos("jlowin")
+    repos = await client.list_repos("prefecthq")
     assert "fastmcp" in [repo.name for repo in repos]
 
 @pytest.mark.client_process

docs/development/upgrade-guide.mdx

@@ -12,6 +12,16 @@ This guide covers breaking changes and migration steps when upgrading FastMCP.
 
 For most servers, upgrading to v3 requires a single change: swap `from mcp.server.fastmcp import FastMCP` for `from fastmcp import FastMCP`. Everything below covers the less common cases.
 
+<Info>
+**New repository home.** As part of the v3 release, FastMCP's GitHub repository now lives at [`prefecthq/fastmcp`](https://github.com/prefecthq/fastmcp) under [Prefect](https://prefect.io)'s stewardship. GitHub automatically redirects existing clones and bookmarks, so nothing breaks — but you can update your local remote whenever convenient:
+
+```bash
+git remote set-url origin https://github.com/prefecthq/fastmcp.git
+```
+
+If you reference the repository URL in dependency specifications (e.g., `git+https://github.com/jlowin/fastmcp.git`), update those to the new location.
+</Info>
+
 <Prompt description="Copy this prompt into any LLM along with your server code to get automated migration guidance.">
 You are migrating a FastMCP v2 server to FastMCP v3.0. Analyze the provided code and identify every change needed. The full upgrade guide is at https://gofastmcp.com/development/upgrade-guide — fetch it for complete context.
 
@@ -95,7 +105,7 @@ The full list of removed kwargs and their replacements:
 
 **OAuth storage backend changed (diskcache CVE)**
 
-The default OAuth client storage has moved from `DiskStore` to `FileTreeStore` to address a pickle deserialization vulnerability in diskcache ([CVE-2025-69872](https://github.com/jlowin/fastmcp/issues/3166)).
+The default OAuth client storage has moved from `DiskStore` to `FileTreeStore` to address a pickle deserialization vulnerability in diskcache ([CVE-2025-69872](https://github.com/prefecthq/fastmcp/issues/3166)).
 
 If you were using the default storage (i.e., not passing an explicit `client_storage`), clients will need to re-register on their first connection after upgrading. This happens automatically — no user action required, and it's the same flow that already occurs whenever a server restarts with in-memory storage.