fastmcp 2.13.1__tar.gz → 2.13.3__tar.gz

{fastmcp-2.13.1 → fastmcp-2.13.3}/.github/workflows/auto-close-duplicates.yml

@@ -16,7 +16,7 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
 
       - name: Generate Marvin App token
         id: marvin-token

{fastmcp-2.13.1 → fastmcp-2.13.3}/.github/workflows/auto-close-needs-mre.yml

@@ -16,7 +16,7 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
 
       - name: Generate Marvin App token
         id: marvin-token

{fastmcp-2.13.1 → fastmcp-2.13.3}/.github/workflows/martian-issue-triage.yml

@@ -24,7 +24,7 @@ jobs:
 
     steps:
       - name: Checkout base repository
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
         with:
           repository: ${{ github.repository }}
           ref: ${{ github.event.repository.default_branch }}

{fastmcp-2.13.1 → fastmcp-2.13.3}/.github/workflows/martian-test-failure.yml

@@ -2,7 +2,7 @@ name: Marvin Test Failure Analysis
 
 on:
   workflow_run:
-    workflows: ["Run Tests"]
+    workflows: ["Tests", "Run static analysis"]
     types:
       - completed
 
@@ -23,7 +23,7 @@ jobs:
       actions: read # Required for Claude to read CI results
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v6
         with:
           fetch-depth: 1
 
@@ -35,7 +35,7 @@ jobs:
           private-key: ${{ secrets.MARVIN_APP_PRIVATE_KEY }}
 
       - name: Set up Python 3.10
-        uses: actions/setup-python@v5
+        uses: actions/setup-python@v6
         with:
           python-version: "3.10"
 

{fastmcp-2.13.1 → fastmcp-2.13.3}/.github/workflows/marvin-dedupe-issues.yml

@@ -21,7 +21,7 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
 
       - name: Generate Marvin App token
         id: marvin-token

{fastmcp-2.13.1 → fastmcp-2.13.3}/.github/workflows/marvin-label-triage.yml

@@ -28,7 +28,7 @@ jobs:
 
     steps:
       - name: Checkout base repository
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
         with:
           repository: ${{ github.repository }}
           ref: ${{ github.event.repository.default_branch }}

{fastmcp-2.13.1 → fastmcp-2.13.3}/.github/workflows/marvin.yml

@@ -31,7 +31,7 @@ jobs:
       (github.event_name == 'issues' && github.event.action == 'labeled' && github.event.label.name == 'marvin')
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v6
 
       # Install UV package manager
       - name: Install UV

{fastmcp-2.13.1 → fastmcp-2.13.3}/.github/workflows/publish.yml

@@ -12,7 +12,7 @@ jobs:
       id-token: write # For PyPI's trusted publishing
     steps:
       - name: Checkout
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
         with:
           fetch-depth: 0
 

{fastmcp-2.13.1 → fastmcp-2.13.3}/.github/workflows/run-static.yml

@@ -30,7 +30,7 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v6
       - name: Install uv
         uses: astral-sh/setup-uv@v7
         with:

{fastmcp-2.13.1 → fastmcp-2.13.3}/.github/workflows/run-tests.yml

@@ -34,7 +34,7 @@ jobs:
     timeout-minutes: 10
 
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v6
 
       - name: Install uv
         uses: astral-sh/setup-uv@v7
@@ -60,7 +60,7 @@ jobs:
     timeout-minutes: 10
 
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v6
 
       - name: Install uv
         uses: astral-sh/setup-uv@v7
@@ -85,7 +85,7 @@ jobs:
     timeout-minutes: 10
 
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v6
 
       - name: Install uv
         uses: astral-sh/setup-uv@v7

{fastmcp-2.13.1 → fastmcp-2.13.3}/.github/workflows/update-config-schema.yml

@@ -21,7 +21,7 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v6
 
       - name: Generate Marvin App token
         id: marvin-token

{fastmcp-2.13.1 → fastmcp-2.13.3}/.github/workflows/update-sdk-docs.yml

@@ -21,7 +21,7 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v6
 
       - name: Generate Marvin App token
         id: marvin-token

{fastmcp-2.13.1 → fastmcp-2.13.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: fastmcp
-Version: 2.13.1
+Version: 2.13.3
 Summary: The fast, Pythonic way to build MCP servers and clients.
 Project-URL: Homepage, https://gofastmcp.com
 Project-URL: Repository, https://github.com/jlowin/fastmcp
@@ -23,10 +23,10 @@ Requires-Dist: cyclopts>=4.0.0
 Requires-Dist: exceptiongroup>=1.2.2
 Requires-Dist: httpx>=0.28.1
 Requires-Dist: jsonschema-path>=0.3.4
-Requires-Dist: mcp!=1.21.1,<2.0.0,>=1.19.0
+Requires-Dist: mcp!=1.21.1,<1.23,>=1.19.0
 Requires-Dist: openapi-pydantic>=0.5.1
 Requires-Dist: platformdirs>=4.0.0
-Requires-Dist: py-key-value-aio[disk,keyring,memory]<0.3.0,>=0.2.8
+Requires-Dist: py-key-value-aio[disk,memory]<0.4.0,>=0.2.8
 Requires-Dist: pydantic[email]>=2.11.7
 Requires-Dist: pyperclip>=1.9.0
 Requires-Dist: python-dotenv>=1.1.0
@@ -355,6 +355,7 @@ FastMCP provides comprehensive authentication support that sets it apart from ba
 - **Auth0**
 - **WorkOS**
 - **Descope**
+- **Discord**
 - **JWT/Custom**
 - **API Keys**
 

{fastmcp-2.13.1 → fastmcp-2.13.3}/README.md

@@ -316,6 +316,7 @@ FastMCP provides comprehensive authentication support that sets it apart from ba
 - **Auth0**
 - **WorkOS**
 - **Descope**
+- **Discord**
 - **JWT/Custom**
 - **API Keys**
 

{fastmcp-2.13.1 → fastmcp-2.13.3}/docs/deployment/http.mdx

@@ -510,6 +510,7 @@ When deploying to production, you'll want to optimize your server for performanc
 # Run with basic configuration
 uvicorn app:app --host 0.0.0.0 --port 8000
 
+# Ensure stateless HTTP mode is enabled (stateless_http=True)
 # Run with multiple workers for production
 uvicorn app:app --host 0.0.0.0 --port 8000 --workers 4
 ```
@@ -601,4 +602,4 @@ This guide has shown you how to create an HTTP-accessible MCP server, but you'll
 - **Edge platforms** (Cloudflare Workers)
 - **Kubernetes clusters** (self-managed or managed)
 
-The key requirements are Python 3.10+ support and the ability to expose an HTTP port. Most providers will require you to package your server (requirements.txt, Dockerfile, etc.) according to their deployment format. For managed, zero-configuration deployment, see [FastMCP Cloud](/deployment/fastmcp-cloud).
+The key requirements are Python 3.10+ support and the ability to expose an HTTP port. Most providers will require you to package your server (requirements.txt, Dockerfile, etc.) according to their deployment format. For managed, zero-configuration deployment, see [FastMCP Cloud](/deployment/fastmcp-cloud).

{fastmcp-2.13.1 → fastmcp-2.13.3}/docs/docs.json

@@ -197,6 +197,7 @@
                   "integrations/aws-cognito",
                   "integrations/azure",
                   "integrations/descope",
+                  "integrations/discord",
                   "integrations/github",
                   "integrations/scalekit",
                   "integrations/google",
@@ -363,6 +364,7 @@
                           "python-sdk/fastmcp-server-auth-providers-in_memory",
                           "python-sdk/fastmcp-server-auth-providers-introspection",
                           "python-sdk/fastmcp-server-auth-providers-jwt",
+                          "python-sdk/fastmcp-server-auth-providers-oci",
                           "python-sdk/fastmcp-server-auth-providers-scalekit",
                           "python-sdk/fastmcp-server-auth-providers-supabase",
                           "python-sdk/fastmcp-server-auth-providers-workos"

{fastmcp-2.13.1 → fastmcp-2.13.3}/docs/integrations/azure.mdx

@@ -164,6 +164,34 @@ Using your specific tenant ID is recommended for better security and control.
 **Important**: The `required_scopes` parameter is **REQUIRED** and must include at least one scope. Azure's OAuth API requires the `scope` parameter in all authorization requests - you cannot authenticate without specifying at least one scope. Use the unprefixed scope names from your Azure App registration (e.g., `["read", "write"]`). These scopes must be created under **Expose an API** in your App registration.
 </Note>
 
+### Scope Handling
+
+FastMCP automatically prefixes `required_scopes` with your `identifier_uri` (e.g., `api://your-client-id`) since these are your custom API scopes. Scopes in `additional_authorize_scopes` are sent as-is since they target external resources like Microsoft Graph.
+
+**`required_scopes`** — Your custom API scopes, defined in Azure "Expose an API":
+
+| You write | Sent to Azure | Validated on tokens |
+|-----------|---------------|---------------------|
+| `mcp-read` | `api://xxx/mcp-read` | ✓ |
+| `my.scope` | `api://xxx/my.scope` | ✓ |
+| `openid` | `openid` | ✗ (OIDC scope) |
+| `api://xxx/read` | `api://xxx/read` | ✓ |
+
+**`additional_authorize_scopes`** — External scopes (e.g., Microsoft Graph) for server-side use:
+
+| You write | Sent to Azure | Validated on tokens |
+|-----------|---------------|---------------------|
+| `User.Read` | `User.Read` | ✗ |
+| `Mail.Send` | `Mail.Send` | ✗ |
+
+<Info>
+**Why aren't `additional_authorize_scopes` validated?** Azure issues separate tokens per resource. The access token FastMCP receives is for *your API*—Graph scopes aren't in its `scp` claim. To call Graph APIs, your server uses the upstream Azure token in an on-behalf-of (OBO) flow.
+</Info>
+
+<Note>
+OIDC scopes (`openid`, `profile`, `email`, `offline_access`) are never prefixed and excluded from validation because Azure doesn't include them in access token `scp` claims.
+</Note>
+
 ## Testing
 
 ### Running the Server
@@ -304,6 +332,8 @@ Redirect path configured in your Azure App registration
 <ParamField path="FASTMCP_SERVER_AUTH_AZURE_REQUIRED_SCOPES" required>
 Comma-, space-, or JSON-separated list of required scopes for your API (at least one scope required). These are validated on tokens and used as defaults if the client does not request specific scopes. Use unprefixed scope names from your Azure App registration (e.g., `read,write`).
 
+You can include standard OIDC scopes (`openid`, `profile`, `email`, `offline_access`) in `required_scopes`. FastMCP automatically handles them correctly: they're sent to Azure unprefixed and excluded from token validation (since Azure doesn't include OIDC scopes in access token `scp` claims).
+
 <Note>
 Azure's OAuth API requires the `scope` parameter - you must provide at least one scope.
 </Note>

{fastmcp-2.13.1 → fastmcp-2.13.3}/docs/integrations/descope.mdx

@@ -6,7 +6,7 @@ icon: shield-check
 tag: NEW
 ---
 
-import { VersionBadge } from "/snippets/version-badge.mdx"
+import { VersionBadge } from "/snippets/version-badge.mdx";
 
 <VersionBadge version="2.12.4" />
 
@@ -17,28 +17,29 @@ This guide shows you how to secure your FastMCP server using [**Descope**](https
 ### Prerequisites
 
 Before you begin, you will need:
+
 1. To [sign up](https://www.descope.com/sign-up) for a Free Forever Descope account
-2. Your **Project ID** from the [Descope Console](https://app.descope.com/settings/project)
-3. Your FastMCP server's URL (can be localhost for development, e.g., `http://localhost:3000`)
+2. Your FastMCP server's URL (can be localhost for development, e.g., `http://localhost:3000`)
 
 ### Step 1: Configure Descope
 
 <Steps>
-<Step title="Enable Dynamic Client Registration">
-    1. Go to the [Inbound Apps page](https://app.descope.com/apps/inbound) of the Descope Console
-    2. Click **DCR Settings**
-    3. Enable **Dynamic Client Registration (DCR)**
-    4. Define allowed scopes
+<Step title="Create an MCP Server">
+    1. Go to the [MCP Servers page](https://app.descope.com/mcp-servers) of the Descope Console, and create a new MCP Server.
+    2. Give the MCP server a name and description.
+    3. Ensure that **Dynamic Client Registration (DCR)** is enabled. Then click **Create**.
+    4. Once you've created the MCP Server, note your Well-Known URL.
+    
     
     <Warning>
     DCR is required for FastMCP clients to automatically register with your authentication server.
     </Warning>
 </Step>
 
-<Step title="Note Your Project ID">
-    Save your Project ID from [Project Settings](https://app.descope.com/settings/project):
+<Step title="Note Your Well-Known URL">
+    Save your Well-Known URL from [MCP Server Settings](https://app.descope.com/mcp-servers):
     ```
-    Project ID: P2abc...123
+    Well-Known URL: https://.../v1/apps/agentic/P.../M.../.well-known/openid-configuration
     ```
 </Step>
 </Steps>
@@ -48,15 +49,10 @@ Before you begin, you will need:
 Create a `.env` file with your Descope configuration:
 
 ```bash
-DESCOPE_PROJECT_ID=P2abc...123      # Your Descope Project ID
-DESCOPE_BASE_URL=https://api.descope.com   # Descope API URL
+DESCOPE_CONFIG_URL=https://.../v1/apps/agentic/P.../M.../.well-known/openid-configuration     # Your Descope Well-Known URL
 SERVER_URL=http://localhost:3000     # Your server's base URL
 ```
 
-<Note>
-You can find your project's Descope Base URL in the [Multi-Region Support Guide](https://docs.descope.com/management/project-settings/multi-regional).
-</Note>
-
 ### Step 3: FastMCP Configuration
 
 Create your FastMCP server file and use the DescopeProvider to handle all the OAuth integration automatically:
@@ -68,9 +64,8 @@ from fastmcp.server.auth.providers.descope import DescopeProvider
 # The DescopeProvider automatically discovers Descope endpoints
 # and configures JWT token validation
 auth_provider = DescopeProvider(
-    project_id=DESCOPE_PROJECT_ID,        # Your Descope Project ID
+    config_url=https://.../.well-known/openid-configuration,        # Your MCP Server .well-known URL
     base_url=SERVER_URL,                  # Your server's public URL
-    descope_base_url=DESCOPE_BASE_URL,    # Descope API base URL
 )
 
 # Create FastMCP server with auth
@@ -80,7 +75,7 @@ mcp = FastMCP(name="My Descope Protected Server", auth=auth_provider)
 
 ## Testing
 
-To test your server, you can use the `fastmcp` CLI to run it locally. Assuming you've saved the above code to `server.py` (after replacing the `project_id`, `base_url`, and `descope_base_url` with your actual values!), you can run the following command:
+To test your server, you can use the `fastmcp` CLI to run it locally. Assuming you've saved the above code to `server.py` (after replacing the environment variables with your actual values!), you can run the following command:
 
 ```bash
 fastmcp run server.py --transport http --port 8000
@@ -102,7 +97,6 @@ if __name__ == "__main__":
 
 ## Environment Variables
 
-
 For production deployments, use environment variables instead of hardcoding credentials.
 
 ### Provider Selection
@@ -110,9 +104,10 @@ For production deployments, use environment variables instead of hardcoding cred
 Setting this environment variable allows the Descope provider to be used automatically without explicitly instantiating it in code.
 
 <Card>
-<ParamField path="FASTMCP_SERVER_AUTH" default="Not set">
-Set to `fastmcp.server.auth.providers.descope.DescopeProvider` to use Descope authentication.
-</ParamField>
+  <ParamField path="FASTMCP_SERVER_AUTH" default="Not set">
+    Set to `fastmcp.server.auth.providers.descope.DescopeProvider` to use
+    Descope authentication.
+  </ParamField>
 </Card>
 
 ### Descope-Specific Configuration
@@ -120,28 +115,25 @@ Set to `fastmcp.server.auth.providers.descope.DescopeProvider` to use Descope au
 These environment variables provide default values for the Descope provider, whether it's instantiated manually or configured via `FASTMCP_SERVER_AUTH`.
 
 <Card>
-<ParamField path="FASTMCP_SERVER_AUTH_DESCOPEPROVIDER_PROJECT_ID" required>
-Your Descope Project ID from the [Descope Console](https://app.descope.com/settings/project)
+<ParamField path="FASTMCP_SERVER_AUTH_DESCOPEPROVIDER_CONFIG_URL" required>
+Your Well-Known URL from the [Descope Console](https://app.descope.com/mcp-servers)
 </ParamField>
 
 <ParamField path="FASTMCP_SERVER_AUTH_DESCOPEPROVIDER_BASE_URL" required>
-Public URL of your FastMCP server (e.g., `https://your-server.com` or `http://localhost:8000` for development)
-</ParamField>
-
-<ParamField path="FASTMCP_SERVER_AUTH_DESCOPEPROVIDER_DESCOPE_BASE_URL" default="https://api.descope.com">
-Descope API base URL for your [region/environment](https://docs.descope.com/management/project-settings/multi-regional)
+  Public URL of your FastMCP server (e.g., `https://your-server.com` or
+  `http://localhost:8000` for development)
 </ParamField>
 </Card>
 
 Example `.env` file:
+
 ```bash
 # Use the Descope provider
 FASTMCP_SERVER_AUTH=fastmcp.server.auth.providers.descope.DescopeProvider
 
 # Descope configuration
-FASTMCP_SERVER_AUTH_DESCOPEPROVIDER_PROJECT_ID=P2abc...123
+FASTMCP_SERVER_AUTH_DESCOPEPROVIDER_CONFIG_URL=https://.../v1/apps/agentic/P.../M.../.well-known/openid-configuration
 FASTMCP_SERVER_AUTH_DESCOPEPROVIDER_BASE_URL=https://your-server.com
-FASTMCP_SERVER_AUTH_DESCOPEPROVIDER_DESCOPE_BASE_URL=https://api.descope.com
 ```
 
 With environment variables set, your server code simplifies to:
@@ -151,4 +143,4 @@ from fastmcp import FastMCP
 
 # Authentication is automatically configured from environment
 mcp = FastMCP(name="My Descope Protected Server")
-```
+```