[TASK] List dotCMS MCP server in Cursor Directory and Smithery

Task Title

dotCMS MCP listing in MCP directories

Description

We should publish the dotCMS MCP server in common registries/directories for agent/tool discovery—specifically Cursor Directory and Smithery—to improve visibility, consistency, and developer onboarding.

Scope:

• Confirm MCP server metadata (name, description, categories, tags, auth, endpoints, version).
• Prepare listing content and assets (short/long descriptions, logo/icon, docs link, repo link).
• Submit and verify listings in:
  • Cursor Directory: https://cursor.directory/
  • Smithery: https://smithery.ai/
• Add a “Discoverability” section to MCP README with links to published listings.
• Document the listing process so we can update it with each release.

Notes:

• Keep descriptions factual and modest; ask for corrections if any details are off.
• Prefer automation or scripts if these directories support API submission.

Acceptance Criteria

• Cursor Directory listing for dotCMS MCP server is publicly visible and includes:
  • Accurate name, description, tags/categories
  • Link to dotCMS/core repository MCP docs
  • Logo/icon rendering correctly
  • Version and last-updated date present (if supported)
• Smithery listing for dotCMS MCP server is publicly visible and includes the same metadata and links.
• MCP README updated with a “Discoverability” section linking to both listings.
• A brief “Listing Playbook” doc (in docs or repo) describing steps to create/update listings.
• QA: Another team member confirms links, metadata accuracy, and search discoverability (searching “dotCMS MCP” returns both listings).

Priority

Medium

Additional Context

Directories like Cursor and Smithery are becoming de facto places developers search for MCP-compatible tools. Listing our MCP server reduces friction for adoption, aligns with community practices, and gives us a place to standardize metadata. If the submission requires email or org verification, loop in the repo owners to complete it.