Currently ghst mcp http exposes all 90 tools as a flat list. When adding the server to a client like Claude Desktop, all tools appear ungrouped, which makes it hard to navigate and understand the available surface at a glance.
It would be useful to group tools by functional category, for example:
- Posts —
ghost_post_list, ghost_post_get, ghost_post_create, ghost_post_update, ghost_post_delete, ghost_post_publish, ghost_post_schedule
- Pages —
ghost_page_*
- Members —
ghost_member_*
- Stats —
ghost_stats_*
- Social web —
ghost_socialweb_*
- Settings / Site —
ghost_setting_*, ghost_site_info
- Tags / Newsletters / Tiers — etc.
This would also make the --tools filtering more ergonomic if categories could be used as a shorthand (e.g. --tools posts,stats instead of listing individual tool names).
The MCP spec supports tool annotations which could carry category metadata for clients that know how to render it.
Currently
ghst mcp httpexposes all 90 tools as a flat list. When adding the server to a client like Claude Desktop, all tools appear ungrouped, which makes it hard to navigate and understand the available surface at a glance.It would be useful to group tools by functional category, for example:
ghost_post_list,ghost_post_get,ghost_post_create,ghost_post_update,ghost_post_delete,ghost_post_publish,ghost_post_scheduleghost_page_*ghost_member_*ghost_stats_*ghost_socialweb_*ghost_setting_*,ghost_site_infoThis would also make the
--toolsfiltering more ergonomic if categories could be used as a shorthand (e.g.--tools posts,statsinstead of listing individual tool names).The MCP spec supports tool annotations which could carry category metadata for clients that know how to render it.