Merge branch 'main' into feat/task-continuity

Author: LucaButBoring

.github/workflows/sep-lifecycle-manual.yml

@@ -72,7 +72,7 @@ jobs:
           LOG_LEVEL: info
 
       - name: Upload logs
-        uses: actions/upload-artifact@v6
+        uses: actions/upload-artifact@v7
         if: always()
         with:
           name: automation-logs-manual-${{ github.run_id }}

.github/workflows/sep-lifecycle.yml

@@ -103,7 +103,7 @@ jobs:
           LOG_LEVEL: info
 
       - name: Upload logs
-        uses: actions/upload-artifact@v6
+        uses: actions/upload-artifact@v7
         if: always()
         with:
           name: automation-logs-${{ github.run_id }}

docs/clients.mdx

@@ -1180,6 +1180,25 @@ Junie is JetBrains' AI coding agent for JetBrains IDEs and Android Studio.
 
 </McpClient>
 
+<McpClient
+  name="Joey"
+  homepage="https://benkaiser.github.io/joey-mcp-client/"
+  sourceCode="https://github.com/benkaiser/joey-mcp-client"
+  supports="Prompts, Tools, Sampling, Elicitation, Apps"
+>
+
+Joey is a mobile-first MCP client for **iOS and Android** (also available on macOS, Windows, and Linux) that connects to AI models via OpenRouter and remote MCP servers over Streamable HTTP.
+
+**Key features:**
+
+- **Mobile MCP support** — use MCP servers directly from your phone or tablet on iOS and Android.
+- Connects to remote MCP servers over **Streamable HTTP** with OAuth support.
+- Supports multiple MCP servers per conversation with tool calling.
+- MCP sampling and elicitation support for interactive server-initiated workflows.
+- Image and audio attachments with SSE streaming responses.
+
+</McpClient>
+
 <McpClient
   name="Kilo Code"
   homepage="https://github.com/Kilo-Org/kilocode"

docs/community/sep-guidelines.mdx

@@ -31,7 +31,7 @@ The SEP process is reserved for changes that are substantial enough to require b
 - Adding examples to existing features
 - Minor schema fixes that don't change behavior
 
-Not sure? Ask in [Discord](https://discord.gg/6CSzBmMkjX) before starting significant work.
+Not sure? Ask in [Discord](/community/communication#discord) before starting significant work.
 
 ## SEP Types
 
@@ -69,6 +69,15 @@ flowchart TD
 
 ### Step-by-Step Process
 
+<Note>
+  To improve your chances of a SEP being accepted:
+
+- **Discuss your idea with the relevant [working or interest group](/community/working-interest-groups) in [Discord](/community/communication#discord) first.** This is the single best way to refine your proposal and build early support.
+- **If no relevant group exists, start a conversation in [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions) or the `#general` channel in [Discord](/community/communication#discord).** If there is enough interest, it may be worth [creating a new IG or WG](/community/working-interest-groups#creating-an-interest-group) — the effort involved in finding sponsors and facilitators is a good signal of whether the idea has sufficient traction, and is still preferable to a cold submission.
+- **Check alignment with [Core Maintainer](/community/governance#roles) priorities and [design principles](/community/design-principles).** Priorities are generally reflected in the [project roadmap](/development/roadmap). Proposals outside current priorities or that conflict with design principles are more likely to face delays or additional friction in the review process.
+
+</Note>
+
 1. **Draft your SEP** as a markdown file named `0000-your-feature-title.md`, using `0000` as a placeholder. Follow the [SEP format](#sep-format) below.
 
 2. **Create a pull request** adding your SEP file to the `seps/` directory in the [specification repository](https://github.com/modelcontextprotocol/modelcontextprotocol).

docs/docs/sdk.mdx

@@ -16,8 +16,8 @@ Build MCP servers and clients using our official SDKs. SDKs are classified into
 | <Icon icon="golang" size={24} /> &nbsp; Go            | [modelcontextprotocol/go-sdk](https://github.com/modelcontextprotocol/go-sdk)                 | [Tier 1](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/2279) |
 | <Icon icon="square-k" size={24} /> &nbsp; Kotlin      | [modelcontextprotocol/kotlin-sdk](https://github.com/modelcontextprotocol/kotlin-sdk)         |                                                                                TBD |
 | <Icon icon="swift" size={24} /> &nbsp; Swift          | [modelcontextprotocol/swift-sdk](https://github.com/modelcontextprotocol/swift-sdk)           | [Tier 3](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/2309) |
-| <Icon icon="rust" size={24} /> &nbsp; Rust            | [modelcontextprotocol/rust-sdk](https://github.com/modelcontextprotocol/rust-sdk)             |                                                                                TBD |
-| <Icon icon="gem" size={24} /> &nbsp; Ruby             | [modelcontextprotocol/ruby-sdk](https://github.com/modelcontextprotocol/ruby-sdk)             |                                                                                TBD |
+| <Icon icon="rust" size={24} /> &nbsp; Rust            | [modelcontextprotocol/rust-sdk](https://github.com/modelcontextprotocol/rust-sdk)             | [Tier 2](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/2346) |
+| <Icon icon="gem" size={24} /> &nbsp; Ruby             | [modelcontextprotocol/ruby-sdk](https://github.com/modelcontextprotocol/ruby-sdk)             | [Tier 3](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/2340) |
 | <Icon icon="php" size={24} /> &nbsp; PHP              | [modelcontextprotocol/php-sdk](https://github.com/modelcontextprotocol/php-sdk)               | [Tier 3](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/2305) |
 
 _\*Official tier assignments will be published February 23, 2026. See [SDK Tiering System](/community/sdk-tiers) for details._