docs+fix(web): native-vs-official MCP comparison, Meta native recommendation, remove wizard shutdown button#271
Merged
Merged
Conversation
Add a bilingual (en/ja) reference explaining what mureo native tools and the official MCP providers can and cannot do for Google Ads and Meta Ads: - Google: official google-ads-mcp is read-only (3 tools, GAQL); mureo native (82 tools) covers full read/write plus the control-plane safety layer. - Meta: official meta-ads-mcp has 29 read+write tools but no guardrails and several capability gaps (audiences, creatives, CAPI send, leads, tests, rules); mureo native (88 tools) closes those gaps. - Documents the MUREO_DISABLE_<PLATFORM> coexistence gating (#102 / #265) and when to use native vs official.
…ure wizard The configure wizard labelled Meta's official hosted MCP as '(recommended)' while leaving mureo-native unmarked. Per the native-vs-official comparison (verified against Meta's official docs), the official Meta MCP lacks creative generation, audience / lookalike creation, Conversions API event sending, lead forms, split tests and automation rules — so mureo-native is the better default for Meta. Move the 'recommended' marker from the official option to the native option (en + ja), preserving the Developer App requirement note. Google stays unchanged (already asymmetric).
… a daemon) The completed step offered a 'Finish & free the terminal' button that POSTed /api/shutdown to stop the mureo configure process. Now that the configure server can run as a resident daemon (launchd/systemd service), stopping it from the wizard is no longer appropriate. Remove the button and its finish_button/finished_note i18n strings (en + ja). The 'Open dashboard' button stays. The /api/shutdown endpoint and server.shutdown() are kept for the SIGINT/SIGTERM path and non-daemon direct launches.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Three changes centered on the mureo-native vs official-MCP story:
docs — Add a Google/Meta comparison of mureo-native tools vs each platform's official MCP (
docs/native-vs-official.md+.ja.md). The Meta official MCP's capability gaps (no creative generation, audience/lookalike creation, Conversions API event sending, lead forms, split tests, automation rules) were verified against Meta's official AI Connectors announcement and Help Centre, and Google's official MCP confirmed as 3 read-only tools.fix(web) — In the configure wizard's provider-choice step, move the "recommended / 推奨" marker for Meta from the official hosted MCP to the mureo-native option (en + ja). Given the verified gaps above, mureo-native is the better default for Meta. Google is intentionally left unchanged.
fix(web) — Remove the configure wizard's "Finish & free the terminal" shutdown button (it POSTed
/api/shutdown) from the completed step, plus itsfinish_button/finished_notei18n strings. The configure server can now run as a resident daemon, so a UI shutdown button is no longer appropriate. The/api/shutdownendpoint andserver.shutdown()are kept for the SIGINT/SIGTERM path and non-daemon launches.Test plan
i18n.json— valid JSON; en/ja parity (233 keys each); no dangling references to removed keyswizard.js—node --checkpasses; completed step still renders the "Open dashboard" button/api/shutdownkept and still covered by existing tests (test_web_server.py,test_web_handlers.py)