[UI Bug] MCP Registry search does not filter server descriptions

Abierto
  • ¿Algo no está bien?
#1,807 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
search

Línea de trabajo

Start by locating the MCP Registry UI search entry point and tracing which server fields it searches; the issue does not name files or tests. Review the search discussion in Issue #13 for relevant context, then add description matching alongside name matching with partial keyword support. Done when a query found only in a server description returns that server.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug

Description

The search functionality in the MCP Registry UI does not appear to search or filter MCP servers based on their descriptions.

Currently, users have difficulty discovering relevant MCP servers unless they already know the server name or an exact keyword associated with it.

Searching by functionality or use case should also return MCP servers whose descriptions contain the relevant terms.

Steps to Reproduce

  1. Open the MCP Registry UI.
  2. Enter a keyword or phrase related to an MCP server's functionality.
  3. Check whether servers with matching terms in their descriptions appear.
  4. Observe that relevant servers may not be returned when the search term exists only in the description.

Expected Behaviour

  • Search should include MCP server names and descriptions.
  • Matching keywords in descriptions should return relevant MCP servers.
  • Search should support partial keyword matching.
  • Users should be able to discover servers based on functionality and use cases, not just server names.

Actual Behaviour

The search does not appear to consider the description field, making it difficult to discover relevant MCP servers based on their capabilities.

Suggested Improvement

Extend the existing search functionality to include the description field alongside server names.

Consider supporting keyword-based matching across metadata fields to improve search relevance and discoverability as the registry grows.

Related Discussion

This issue is related to the earlier discussion in Issue #13, which also touches on registry search behaviour.

It would be useful to revisit this discussion when implementing the improvement.

Impact

Improving description-based search will:

  • Make MCP discovery easier for developers and users.
  • Improve visibility of MCP servers based on their actual capabilities.
  • Reduce dependency on knowing exact server names.
  • Improve the overall usability and discoverability of the MCP ecosystem.

Priority: Medium – Search usability and discoverability.

Lenguaje dominante
Go
Estrellas
7.4k
Forks
1k
Merge medio
17 h 57 min
PR fusionados (30 d)
68

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de modelcontextprotocol/registry

Todos los issues de modelcontextprotocol/registry

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.