|
2 | 2 |
|
3 | 3 | This guide, for client application developers, covers a new API for client |
4 | 4 | configuration. Client applications can use this API to get info about configured |
5 | | -MCP servers from configuration files in a variety of formats and with some |
6 | | -useful, built-in features. |
| 5 | +MCP servers from configuration files |
| 6 | + |
| 7 | +## Why should my application use this API? |
| 8 | + |
| 9 | +- Eliminate the need to write and maintain code to parse configuration files |
| 10 | +- Your application can easily benefit from bug fixes and new features related to configuration |
| 11 | +- Allows your application to support features that other applications may have |
| 12 | + and which your application does not. E.g., |
| 13 | + |
| 14 | + - Allow specifying the entire command in the `command` field (not having to |
| 15 | + specify an `args` list), which makes it easier for users to manage |
| 16 | + - Allow comments in JSON configuration files |
| 17 | + - Input variables (as supported by VS Code), plus validation of required inputs |
| 18 | + and interpolation of input values |
| 19 | + - YAML configuration files, which are more readable and easier to write than JSON |
| 20 | + |
| 21 | +- If every application that uses MCP supported this API, it would lead to |
| 22 | + greater consistency in how MCP servers are configured and used, which is a |
| 23 | + tremendous win for users and a benefit to the MCP ecosystem. |
7 | 24 |
|
8 | 25 | ## Loading Configuration Files |
9 | 26 |
|
|
0 commit comments