Improved
MCP Server v0.0.1-beta.17
about 1 month ago by ReadMe API
This release improves goal safety, split-URL creation, reporting guidance and privacy-safe diagnostics across local and hosted Convert MCP.
Safer Experience Workflows
- Visits-page goals reject ignored settings.url fields and explain the correct triggering_rule shape, including partial updates.
- Split-URL creation defaults to a no-redirect Original and a redirect treatment with 50/50 allocation. Custom setups require an explicit baseline and allocation.
- Readback checks arm identity, traffic and the requested changes, rejecting unexpected code or redirects. Incomplete verification preserves the creation receipt instead of recommending a duplicate experience.
- Lifecycle permission errors distinguish creating an active experience from starting or pausing an existing one. User confirmation never substitutes for backend permissions.
Clearer Reporting
- Engine-specific done guidance distinguishes Bayesian chance-to-win and risk, sequential Frequentist significance, and other Frequentist MDE/power sample targets. Reaching a sample target does not necessarily mean a significant result.
- Default-like report values are not treated as proof that computation occurred.
- Improved project-default inheritance, daily-report goal selection and deprecated minimum-conversion guidance.
Diagnostics And Compatibility
- Clearer authentication, authorization and failure categories without recording credentials, customer data or raw upstream diagnostics.
- Existing OAuth endpoints, grants, session bindings, tool names and protocol settings are unchanged. Existing authenticated clients do not need to reconnect.
- Local users running npx -y @convertcom/mcp-server@latest receive the new version on a fresh launch; already-running processes need a restart.
Stricter goal and custom split-input checks intentionally reject ambiguous or silently ignored payloads. Actions retain the same backend permissions and confirmation guardrails. Missing backend computation-availability metadata remains a limitation; notifications and directory submissions are not included in this release.