Skip to content

The tool list_applications search parameter does not work with Argo CD REST API (v3.2.1) #107

Description

@bodaWang

I noticed a mismatch between the search parameter exposed by the list_applications tool and the actual capabilities of the Argo CD REST API.

The MCP tool:
list_applications

supports a parameter:
search: string

which implies that it can be used to filter applications.

However, when using Argo CD version:
• Version: v3.2.1+8c4ab63
• Build Date: 2025-11-30T11:48:14Z

the REST API:
GET /api/v1/applications
does not support a generic search parameter.

As a result, when an MCP client calls:
{ "name": "list_applications", "arguments": { "search": "keyword" } }

The response is not filtered at all, and returns the full list of applications. According to the Argo CD REST API, the supported query parameters are:
• name (string): the application’s name
• refresh (string): forces reconciliation
• projects (array): restrict by project
• resourceVersion (string): for watch calls
• selector (string): label selector
• repo (string): filter by repo URL
• appNamespace (string): filter by namespace
• project (array): legacy project filter

There is no search parameter supported by the API. This causes confusion because:
• The MCP tool interface suggests filtering capability via search
• But the underlying API does not support it
• The MCP server currently appears to pass search directly to the API without applying any fallback filtering

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions