You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -237,8 +237,7 @@ A full `manifest.json` with most of the optional fields looks like this:
237
237
-**privacy_policies**: Array of URLs to privacy policies for external services that handle user data. Required when the extension connects to external services (first- or third-party) that process user data. Each URL should link to the respective service's privacy policy document
238
238
-**compatibility**: Compatibility requirements (client app version, platforms, and runtime versions)
239
239
-**user_config**: User-configurable options for the extension (see User Configuration section)
240
-
-**static_responses**: A set of static response to protocol messages (for example, `initialize`, `tools/list`, etc.). This allows clients to avoid running a server when a static response is present (e.g. to get the set of tools with their input schemas). For more information, consult the [MCP specification](https://modelcontextprotocol.io/specification).
241
-
-**client_extensions**: Platform-specific client integration metadata (e.g., Windows `package_family_name`, macOS bundle identifiers) enabling tighter OS/app store integration
240
+
-**_meta**: Platform-specific client integration metadata (e.g., Windows `package_family_name`, macOS bundle identifiers) enabling tighter OS/app store integration. The keys in the `_meta` object are reverse-DNS namespaced, and the values are a dictionary of platform-specific metadata.
242
241
243
242
## Compatibility
244
243
@@ -598,8 +597,6 @@ These fields describe the tools and prompts your MCP server provides. For server
598
597
599
598
Note: Resources are not included in the manifest because MCP resources are inherently dynamic - they represent URIs to data that the server discovers at runtime based on configuration, filesystem state, database connections, etc.
600
599
601
-
You can provide richer static tools by adding an `tools/list` entry inside the `static_responses` object.
602
-
603
600
### Static Declaration
604
601
605
602
For servers with a fixed set of capabilities, list them in arrays.
@@ -659,62 +656,3 @@ The `_generated` fields:
659
656
660
657
This helps implementing apps understand that querying the server at runtime will reveal more capabilities than what's declared in the manifest.
661
658
662
-
## Static responses
663
-
664
-
Servers can provide clients with static responses to protocol messages. Static responses let clients short-circuit server startup for discovery or platform integration metadata.
665
-
This is useful to obtain rich tool schema information, server instructions, protocol version that the server supports, etc.
666
-
The `static_responses` object is a dictionary where the key is the name of an MCP JSON-RPC method. For more information, consult the [MCP specification](https://modelcontextprotocol.io/specification).
667
-
668
-
If both the `tools/list` static response and the `tools` array are present, clients should use the tools described in `tools/list`.
669
-
670
-
Example:
671
-
672
-
```json
673
-
{
674
-
"static_responses": {
675
-
"initialize": {
676
-
"capabilities": {},
677
-
"instructions": "When the user wants to search files, use the search_files tool but only after asking them whether the files are local.",
678
-
"protocolVersion": "2025-06-18",
679
-
"serverInfo": {
680
-
"name": "MyMCPExtension",
681
-
"title": "My MCP Extension - Pro Edition",
682
-
"version": "1.0.0"
683
-
}
684
-
},
685
-
"tools/list": {
686
-
"tools": [
687
-
{
688
-
"name": "search_files",
689
-
"title": "File search",
690
-
"description": "Search for files in a directory",
691
-
"inputSchema": {
692
-
"type": "object",
693
-
"properties": {
694
-
"fileSpec": {
695
-
"type": "string",
696
-
"description": "The file name to search for. Wildcards are supported"
697
-
}
698
-
},
699
-
"required": ["fileSpec"]
700
-
},
701
-
"outputSchema": {
702
-
"type": "object",
703
-
"properties": {
704
-
"searchResults": {
705
-
"type": "array",
706
-
"description": "The list of file paths that were found",
0 commit comments