Add `aliases` field to MCP server schema for improved discoverability

[mgoldsborough]

Summary

Add an optional aliases field to the MCP server schema to improve discoverability when users search for servers using common alternative names (e.g., searching "twitter" should find "X").

Problem

When users search for MCP servers, they often use colloquial or legacy names:

• "Twitter" instead of "X"
• "Sheets" instead of "Google Sheets"
• "Drive" instead of "Google Drive"

Currently, the schema supports title, name, description, category, and tags for searchability. However, none of these are specifically designed for alternate names. Using tags conflates categorization with alternate names.

Proposed Solution

Add an optional aliases field at the root level:

{
  "name": "ai.nimbletools/x-social",
  "title": "X",
  "description": "Social media platform for posts, engagement, and messaging",
  "aliases": ["twitter", "tweet", "tweets"],
  "version": "1.0.0"
}

Schema Definition

{
  "aliases": {
    "type": "array",
    "items": {
      "type": "string",
      "minLength": 1,
      "maxLength": 64
    },
    "maxItems": 10,
    "uniqueItems": true,
    "description": "Alternative names users commonly search for. Used for discoverability only, not display."
  }
}

Current State

Already implemented in Studio (internal):

• aliases field on DiscoverableConnection interface
• Hardcoded aliases for Composio toolkits (X/twitter, Google Drive/gdrive, Google Sheets/gsheets, etc.)
• Search logic includes aliases in ConnectionManagementService and connection-handlers

Gaps (this issue):

• Add aliases field to MCP registry schema
• Registry API should return aliases in server metadata
• Replace hardcoded Composio aliases with dynamic registry data

Use Cases

Server Name	Title	Aliases
ai.nimbletools/x-social	X	twitter, tweet, tweets
ai.nimbletools/google-drive	Google Drive	gdrive, drive
ai.nimbletools/google-sheets	Google Sheets	gsheets, sheets, spreadsheet

Implementation Notes

Registry clients should:

1. Include aliases in search text when filtering servers
2. NOT display aliases to users (search only)
3. Treat aliases as case-insensitive