list_configs
Retrieve and filter configurations by namespace, group, type, tags, or appName using pagination and search options in Nacos MCP Server.
Instructions
This interface retrieves the list of configurations under a specified namespace.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| appName | No | The appName of configs, default null means all appName, if not null, server will search all config match appName. | |
| configTags | No | The tags of configs, default null means all tags, if not null, server will search all config match tags. Multiple tags using `,` to split, such as `tag1,tag2` | |
| dataId | No | The dataId pattern of configs, default null means all dataId. if not null, server will search all config match dataId. If `search=blur`, this parameter allow use `*` to do blur search, such as `*test` to do prefix and `test*` to do suffix | |
| groupName | No | The groupName pattern of configs, default null means all group. if not null, server will search all config match groupName. If `search=blur`, this parameter allow use `*` to do blur search, such as `*test` to do prefix and `test*` to do suffix | |
| namespaceId | No | The namespaceId of configs, default is `public` if missing | |
| pageNo | Yes | The current page number, default is 1. | |
| pageSize | Yes | The size of configs in each page, default is 100 | |
| search | No | The search way of list configs, default is `blur` means blur search groupName and dataId. Or using `accurate` means accurate match with groupName and dataId. | |
| type | No | The type of configs, default null means all type, if not null, server will search all config match type. Multiple type using `,` to split, such as `text,json` |
Input Schema (JSON Schema)
{
"properties": {
"appName": {
"description": "The appName of configs, default null means all appName, if not null, server will search all config match appName.",
"type": "string"
},
"configTags": {
"description": "The tags of configs, default null means all tags, if not null, server will search all config match tags. Multiple tags using `,` to split, such as `tag1,tag2`",
"type": "string"
},
"dataId": {
"description": "The dataId pattern of configs, default null means all dataId. if not null, server will search all config match dataId. If `search=blur`, this parameter allow use `*` to do blur search, such as `*test` to do prefix and `test*` to do suffix",
"type": "string"
},
"groupName": {
"description": "The groupName pattern of configs, default null means all group. if not null, server will search all config match groupName. If `search=blur`, this parameter allow use `*` to do blur search, such as `*test` to do prefix and `test*` to do suffix",
"type": "string"
},
"namespaceId": {
"description": "The namespaceId of configs, default is `public` if missing",
"type": "string"
},
"pageNo": {
"description": "The current page number, default is 1.",
"type": "int"
},
"pageSize": {
"description": "The size of configs in each page, default is 100",
"type": "int"
},
"search": {
"description": "The search way of list configs, default is `blur` means blur search groupName and dataId. Or using `accurate` means accurate match with groupName and dataId.",
"type": "string"
},
"type": {
"description": "The type of configs, default null means all type, if not null, server will search all config match type. Multiple type using `,` to split, such as `text,json`",
"type": "string"
}
},
"required": [
"pageNo",
"pageSize"
],
"type": "object"
}