MCP Server

MCP Server v0.0.1-beta.17

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.

MCP Server v0.0.1-beta.16

This release improves protocol compatibility, catalog refresh, documentation search and connection handling while preserving existing Convert permissions and authentication.

Protocol And Catalogs

Hosted MCP supports 2026-07-28 alongside the existing protocol adapter. Unsupported versions are not silently rewritten.
Tools, prompts, resources, schemas, permission checks and destructive-action confirmations remain consistent across supported protocols.
Compatible modern clients can subscribe to catalog-change notifications within the same authorization grant. Notifications are deduplicated and revalidate authorization; explicit refresh remains the fallback.
Client support determines whether notifications trigger automatic refresh or resubscription.

Search And Reliability

Improved hosted documentation-search efficiency while preserving semantic retrieval, support-first ranking, document-ID compatibility and direct fetch.
Safer session recovery preserves authentication boundaries and never automatically replays writes.
Cancellation propagates through API requests and documentation search. When an underlying model operation cannot be interrupted, its result is discarded instead of starting further work.

Compatibility And Limits

No customer configuration change or new OAuth consent is required. Hosted clients retain their endpoint, grants and account/project scopes. The npm package remains a local stdio server using the same API-key/HMAC setup.

Local users configured with npx -y @convertcom/mcp-server@latest receive the published version on their next launch, subject to client caching; already-running processes need a restart.

Notification settings and history remain disabled pending backend support. Explicit account-wide consent, approval requirements and two-step deletion confirmation remain unchanged.

Catalog refresh does not guarantee interruption-free transport handover. An existing legacy session may encounter a documentation-search timeout during an upgrade; subsequent sessions can recover without OAuth reauthorization.

MCP Server v0.0.1-beta.15

Explicit Account-Wide Access

Eligible users can authorize Entire account, including future projects during OAuth consent. This enables account-wide tools, including project creation, subject to backend roles, permissions, plan limits and the role approved at consent.

Selecting all existing projects remains a selected-project grant, not access to future projects. Existing grants are not automatically expanded. Reconnect only to deliberately approve broader access. Local API-key/HMAC permissions are unchanged.

Approval Governance

Approval requirements return actionable request information. Preserved request IDs let agents inspect pending requests instead of submitting duplicates.
Approval actions require explicit, target-bound confirmation. MCP never automatically approves or retries an approved action.
Account-wide approval settings require account-wide hosted consent. Write profiles remain subject to backend permissions and independent-review requirements.

Project Management And Reliability

Project creation is available only to eligible hosted grants and is checked against the exact account at execution. New projects are discoverable with an existing entire-account grant.
Project deletion requires an explicit request followed by a second confirmation naming the exact numeric resource. Read-only profiles do not expose deletion.
Grant-aware catalogs recover after transient scope-resolution failures and notify compatible clients when the catalog changes.
Refreshed knowledge search preserves existing document-ID compatibility and local/hosted semantic retrieval.
Improved validation covers newly available project lifecycle operations.

Notifications Deferred

Notification settings and history are disabled by default pending backend rollout. Disabled tools are absent from the catalog and reject stale calls. This release does not change notification settings or delivery in the Convert application.

The local package remains stdio; hosted-only runtime code is not its npm entrypoint. Existing local and hosted clients continue working without configuring notifications.

MCP Server v0.0.1-beta.14

Beta.14 expands hosted tools, read-only investigation, experimentation guidance and optional visual reports while preserving local API-key/HMAC access and existing hosted OAuth grants.

Safer Hosted Catalog

Local stdio retains 16 compact tools. Hosted MCP exposes 45 tools: 40 read/write/delete tools plus five read-only render tools, with 20 prompts and six resources.
Reads use base namespaces, writes use write and deletion uses delete. POST-backed reports are classified as reads according to their behavior.
WrongToolForAction errors provide the correct call when an action is sent to the wrong tool.
Hosted selected-project grants no longer advertise account-level actions they cannot authorize, including project creation, billing portal access, account-wide live data/history and collaborator listing. Local actions remain subject to Convert permissions; project-scoped alternatives remain available remotely.
API-key listing is omitted because API-authenticated callers cannot retrieve key records; stale calls fail explicitly instead of suggesting a successful empty result.
Canonical documentation tools are search and fetch; search_knowledge_base is not advertised.
Improved connector metadata and client compatibility do not imply approval or availability in third-party directories.

Read-Only Investigation And Opportunities

operator.investigate provides a structured evidence packet with confirmed facts, anomalies, hypotheses, missing evidence, limitations and safe next checks.
projects.debug_logs offers explicit, authorized drill-down into bounded tracking diagnostics. experiences.report_integrity compares complete recent and baseline windows for meaningful stream drops.
Default investigation output minimizes data, excluding visitor IDs, full URLs, referrers, user-agent strings and raw debug rows. Data minimization is not a claim of anonymity.
Unknown evidence remains unknown; empty debug logs alone do not prove healthy tracking. Project and experience live-data feeds retain their different goal scopes.
The High-Impact Experience Opportunities prompt grounds recommendations in configuration, experiences, goals, hypotheses, audiences, locations, results and measurement readiness. It does not promise impact or modify resources.
Browser and source checks remain client-side capabilities; MCP does not embed a browser.

Experience And Statistics Guidance

Uses experience terminology consistently. Deploy experiences are rollout containers, not visitor/conversion-tracked tests; empty tracking data alone does not mean a deploy is broken.
Keeps Bayesian, fixed-sample Frequentist and sequential evidence distinct. done is interpreted within the configured engine, and reaching a sample target is not necessarily significance.
Sample ratio mismatch blocks result verdicts, including inferential intervals and Bayesian/sequential completion claims. Explicitly labeled sample-planning progress may remain visible.
Multi-Armed Bandit allocation is not evidence of significance or a winner. MAB is limited to standard A/B, fullstack A/B and MVT experiences; Frequentist MAB requires Sequential.
Preserves automatic-MDE locks, clarifies fixed_mde as relative-percent planning input and rejects unsafe unknown or legacy-scale updates. Planning thresholds are not expected or observed lift.
More precise statistics validation, allowed-value guidance and guarded MDE updates prevent ambiguous or silently normalized writes. Inactive-engine results are not invented from counts.
Goal definitions are resolved against authoritative catalogs, with incomplete coverage reported explicitly.
Portfolio and audit workflows follow pagination and disclose bounded coverage rather than treating an initial page as a complete total.
Unknown wrapper fields and misplaced history pagination fail before dispatch with corrective guidance.

Optional Visual Reports

Hosted clients supporting MCP Apps can render project portfolios, experience details, draft reviews, experience results and investigation reports.

Rendering is optional and read-only. Agents first retrieve and analyze ordinary tool data; every renderer also provides a sanitized text digest. Clients without MCP Apps receive the same substantive evidence. Existing versioned visual resources retain compatibility.

Safer Writes And Security

Improved validation of nullable and composed API schemas, account scope and JSON inputs, including embedded JavaScript, CSS and selectors.
Verified operator writes independently read back persisted changes. Disclosed trimming of code-edge whitespace is distinguished from substantive changes, preventing duplicate retries after successful writes.
Variation-code updates preserve omitted code, page binding and sibling content, use optimistic concurrency, and fail closed on ambiguous, incomplete or stale readback.
Authentication headers cannot be overridden. Bounded retries apply to safe/idempotent rate-limit and service-unavailable responses; unsafe writes are not automatically retried by default.
Upstream redirects are rejected without forwarding credentials or replaying OAuth codes.
Hosted OAuth supports Dynamic Client Registration and HTTPS Client ID Metadata Documents with PKCE. Refresh-token lifetime is bounded by the upstream session.
Strengthened credential protection, origin restrictions and redaction keep secrets and sensitive upstream diagnostics out of model-visible output.
Hosted stream results are not persisted for replay. Interrupted streams restart instead of resuming via Last-Event-ID.
Deletion still requires an exact user request and a second confirmation naming the numeric resource. Generated API operations cannot bypass namespace guardrails.

Knowledge And Feedback

Refreshed support, developer and public website knowledge with 9,523 chunks, hybrid search and one result per canonical article.
Earlier document IDs resolve to exact compatible content or an explicit stale-document response, never a fuzzy substitute.
The local package includes its semantic index and retains keyword fallback when optional dependencies are omitted.
operator.prepare_feedback creates a sanitized preview without storing it. operator.submit_feedback requires explicit approval of the prepared content; local feedback never forwards Convert credentials.

Compatibility And Security Notice

Hosted clients retain the same endpoint, OAuth client, grants and selected account/project scope. The beta.14 transport-session security update requires active MCP sessions to initialize again but preserves OAuth authorization. Host caching may require an explicit tool/app refresh or a new conversation; catalog-change notifications are advisory, not guaranteed delivery.

The local package retains stdio transport and excludes hosted-only runtime components.

At beta.14 release, the optional text-embedding runtime inherited upstream sharp image-decoding and adm-zip archive advisories. Neither affected path accepted MCP request data; the archive dependency was used by the model runtime's vendor-binary installer. Installations omitting optional semantic dependencies did not include those findings. These are historical beta.14 dependency notes, not a statement about later package versions.

MCP Server v0.0.1-beta.13

This release improves consistency between local and hosted Convert MCP while preserving the local npm startup fix introduced in beta.12.

Highlights

Local and hosted clients share namespace schemas, prompts, operator workflows, result envelopes, guardrails and OpenAI-compatible search/fetch tools.
Local startup remains compatible with npx -y @convertcom/mcp-server@latest, the installed convert-mcp binary and Windows package shims.
The public npm package remains local stdio; hosted-only runtime files are excluded.
Improved hosted connector guidance, OAuth metadata and client-facing branding.
Reliable schema validation across local and hosted tools.
Deletion requires an exact user request and a second confirmation naming the resource before dispatch.
Improved OAuth refresh compatibility with Claude clients.

Existing local API-key/HMAC authentication and hosted OAuth permissions are preserved.

MCP Server v0.0.1-beta.12

Beta.12 replaces withdrawn beta.11 and fixes local npm/npx server startup.

Fixes

Corrected startup through npx -y @convertcom/mcp-server@latest and installed package binaries, including Windows command shims.
Refreshed the packaged Convert knowledge base and semantic index with 5,797 chunks.
Corrected vector-index packaging so required empty segments are preserved and documentation search can open the installed index.

Beta.11 was withdrawn after a package-binary startup failure. npm versions are immutable, so the corrected package uses beta.12 rather than replacing beta.11. The npm package remains a local stdio server.

MCP Server v0.0.1-beta.10

Beta.10 expands workflow guidance, documentation search and API validation.

Discovery And Workflows

OpenAI-compatible search and fetch replace the advertised search_knowledge_base tool.
Refreshed hybrid knowledge search with 5,776 chunks across 500 support articles.
Added 19 prompts for experimentation workflows, implementation debugging and experience building.
Added a compact operator namespace with reporting/audit actions and verified write workflows, plus project-default inference for goals, audiences, locations, URL patterns and traffic splits.
Expanded API coverage includes account billing portal and experience heatmap background/overlay operations, subject to backend permissions.

Validation And Safer Writes

Corrected schemas for experience changes, audiences, locations, goals and typed feature defaults, including boolean false and numeric values.
Rejects inline site_area values that the API would accept but fail to persist.
Link-click goal href settings must be strings; use triggering_rule for page scoping or separate link goals where appropriate.
Fixed multipart screenshot uploads and verifies persistence when an upload reports an error after saving.
Protected authentication/signing headers from overrides and added bounded backoff for 429/503 responses without automatic unsafe-write retries by default.
Improved package reliability and packaged semantic-index availability.

MCP Server v0.0.1-beta.9

Highlights

Improved namespace argument handling for Claude Code and other MCP clients that flatten or stringify path/body fields.
Pinned axios to 1.13.5 for consistent dependency behavior.

MCP Server v0.0.1-beta.8

Improved robustness and compatibility across MCP clients.
Better validation and actionable errors that help agents correct invalid calls.
Stronger safety guardrails and improved schemas across namespaces.

MCP Server v0.0.1-beta.7

Agent Usability And Discovery

Write tools show valid enums, required fields, examples and guidance for common configuration pitfalls.
Errors include contextual recovery guidance.
Improved discovery helps clients use the 13 namespace API tools for authorized Convert account access, alongside documentation search.
Tools expose standard MCP read-only, destructive, idempotent and external-access annotations.

Knowledge And Reliability

Built-in hybrid keyword and semantic search answers Convert platform questions using embedded documentation.
Fixed an abnormal shutdown when partially initialized semantic search falls back to keyword-only mode.
Updated API coverage and dependencies.

MCP Server v0.0.1-beta.6

Updated npm package metadata to remove unavailable repository and homepage links. Runtime features are unchanged from beta.5.

Client Configuration

Configure your MCP client to run npx with arguments -y and @convertcom/mcp-server@latest. Set CONVERT_API_KEY and CONVERT_API_SECRET to your own Convert credentials. TOOLS_FOR_CLIENT=reporting selects the reporting profile.

Do not share credentials or include them in prompts or release notes.

MCP Server v0.0.1-beta.5

Simplified npm documentation to focus on MCP client integration and usage. Runtime features are unchanged from beta.4.

Client Configuration

Do not share credentials or include them in prompts or release notes.

MCP Server v0.0.1-beta.4

Redesigned package documentation with clearer client integration, API coverage, examples and troubleshooting.
Improved security guidance and access-level explanations.
Built-in knowledge base includes more than 5,279 indexed chunks from Convert support documentation.

Installation

Run npx -y @convertcom/mcp-server@latest from your MCP client's local-server configuration.

This replaces beta.3's package documentation; release-maintainer workflows are not required for client setup.

MCP Server v0.0.1-beta.3

Improved package documentation, example prompts and client guidance.
Built-in knowledge base includes more than 5,279 indexed chunks from Convert support documentation.
Clearer security best practices.

Installation

Run npx -y @convertcom/mcp-server@latest from your MCP client's local-server configuration.

MCP Server v0.0.1-beta.2

Improved package documentation, example prompts and client guidance.
Built-in knowledge base includes more than 5,279 indexed chunks from Convert support documentation.
Clearer security best practices.

Installation

Run npx -y @convertcom/mcp-server@latest from your MCP client's local-server configuration.