In-depth architectural comparison of the Ghost Publisher and UI5 MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Ghost Publisher
Developer Tools · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
UI5 MCP Server
Developer Tools · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose Ghost Publisher if you need specialized Developer Tools tools running via a local process. Choose UI5 MCP Server if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Ghost Publisher when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Verify Ghost and report the permission profile, backward-compatible read-only flag, and optional feature availability. A configured deployment reveals only its host.
list_posts
List/search posts and obtain exact IDs plus `updated_at`.
get_post
Read one post by ID or slug with content plus complete SEO and social metadata.
list_tags
List tags with post counts.
list_authors
Search bounded public author identity fields without exposing staff email, roles, permissions, or settings.
list_pages
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Ghost Publisher is categorized under Developer Tools and uses a local stdio subprocess. In contrast, UI5 MCP Server belongs to Developer Tools using local stdio subprocess. Select Ghost Publisher when you need capabilities focused on developer tools and UI5 MCP Server when you require tools for developer tools.
List/search Pages with bounded status, date, order, and pagination fields.
get_page
Read one Page by exact ID or slug with content and metadata.
audit_content
Mechanically inspect up to 25 exact posts/Pages and return backward-compatible inventory plus deterministic content, structure, accessibility, card, link, citation, metadata, and media findings; never crawls or scores quality.
check_site_health
Read-only checks of server-derived Ghost and delivery homepages, sitemaps, up to five exact published posts/Pages, rendered titles/canonicals/share prerequisites, and Ghost-returned feature images.
plan_schedule
Convert an ordered draft list from an IANA local time to exact UTC timestamps and return a site/revision-bound HMAC plan without writing.
create_drafts
Create up to 10 posts from Markdown or bounded native headings, paragraphs, lists, quotes, code blocks, uploaded-image cards, bookmarks, callouts, and buttons; prose supports inline bold, italic, code, and HTTP(S) links. Always draft-only.
create_page_drafts
Create up to 10 Pages from the same bounded Markdown or native-block input; always draft-only.
+12 more tools listed on main page
UI5 MCP Server Tools (10)
create_integration_card
Scaffolds a new UI Integration Card.
create_ui5_app
Scaffolds a new UI5 application based on a set of templates.
get_api_reference
Fetches and formats UI5 API documentation.
get_guidelines
Provides access to UI5 development best practices.
get_integration_cards_guidelines
Provides access to UI Integration Cards development best practices.
get_project_info
Extracts metadata and configuration from a UI5 project.
get_typescript_conversion_guidelines
Provides guidelines for converting UI5 applications and controls from JavaScript to TypeScript.
get_version_info
Retrieves version information for the UI5 framework.
run_manifest_validation
Validates the manifest against the UI5 Manifest schema.
run_ui5_linter
Integrates with [`@ui5/linter`](https://github.com/UI5/linter) to analyze and report issues in the UI5 code.