feat(mcp): add Neon catalog entry

[mezotv]

Description

Add Neon to the MCP catalog with its hosted MCP endpoint, docs link, and catalog icon.

[greptile-apps]

Greptile Summary

Adds a Neon Postgres entry to the MCP catalog, covering the hosted remote endpoint (https://mcp.neon.tech/mcp), its documentation URL, and the matching SVG icon. The icon is picked up automatically via the existing filename-based glob convention in mcpIcons.tsx.

• The catalog entry mirrors the pattern of other OAuth-authenticated hosted endpoints (Supabase, Vercel, Linear), with credentialKeys: [] since mcp.neon.tech handles auth via an OAuth browser flow and requires no pre-configured client credentials.
• The SVG's fill="currentColor" and sizing are injected at render time by prepareInlineSvgMarkup, so the bare path element in the file is correct.

Confidence Score: 5/5

Straightforward catalog addition with no logic changes — safe to merge.

Both changed files are additive only: a new catalog entry that follows the same shape as every other OAuth-based hosted MCP server in the file, and an SVG that is picked up automatically by the existing glob loader. The MCP URL, docs link, and icon are all verified correct.

No files require special attention.

Important Files Changed

Filename	Overview
src/shared/mcp/catalog.ts	Adds a neon catalog entry with the correct hosted MCP URL, docs link, and empty credentialKeys (OAuth-based remote endpoint requires no pre-configured credentials, consistent with Supabase, Vercel, Linear, etc.)
src/assets/images/mcp/neon.svg	New SVG icon for Neon using the Neon logo path; fill="currentColor" and sizing are applied at render time by prepareInlineSvgMarkup, consistent with all other catalog icons

Sequence Diagram

sequenceDiagram
    participant User
    participant App as emdash App
    participant CatalogEntry as catalog.ts (neon entry)
    participant OAuthFlow as OAuth Browser Flow
    participant NeonMCP as mcp.neon.tech/mcp

    User->>App: Select Neon from MCP catalog
    App->>CatalogEntry: Load config (type: http, url: mcp.neon.tech/mcp)
    App->>OAuthFlow: Trigger OAuth authentication (no API key needed)
    OAuthFlow-->>App: Return access token
    App->>NeonMCP: HTTP requests with OAuth token
    NeonMCP-->>App: Postgres DB management responses

Loading

_{Reviews (1): Last reviewed commit: "fix(mcp): add Neon auth header" | Re-trigger Greptile}

[arnestrickmann]

Nice!

[arnestrickmann]

Great addition, @mezotv!
Thank you:)