Convika

What the Convika MCP server does

The Convika MCP server lets an AI client manage landing pages hosted by Convika. An agent can create a page from generated content, save revisions, produce a private preview, and publish only after the user requests publication. Pages may include signup forms, and Convika stores submitted entries for later retrieval or export.

The service also provides hosting and measurement features. Agents can assign a site URL, configure a custom domain, inspect domain status, and manage domain routes. Analytics tools expose visits, traffic sources, UTM campaigns, button clicks, and signups. Convika can also analyze site performance, source quality, time series, segments, calls to action, and detected trends.

How it works

The hosted endpoint is https://mcp.convika.com/mcp and uses Streamable HTTP. A compatible client connects to that URL and starts OAuth 2.1 authentication with dynamic client registration and PKCE. The client opens a browser for Convika sign-in, so the setup does not require an API key.

A typical workflow starts when the AI creates a landing page preview. Convika returns a private preview link, and the page remains unpublished until a separate publish request. Each save creates a new version, allowing the agent to roll back a site or unpublish it later. Published pages continue serving if the Convika dashboard is unavailable.

Setup and configuration

Add the hosted MCP URL to a client that supports remote MCP connections. Claude users can add it as a custom connector. Claude Code can install the Convika plugin, which also provides a publish-page skill, or add the server directly with the HTTP transport. Codex, Cursor, and other MCP clients can use a server entry containing the endpoint URL.

After connecting, authenticate through the browser. The repository documents no required environment variables and identifies the server as a hosted, closed-source service. A Convika account is required; signup is available without a payment card. The free plan includes limits on pages, pageviews, form entries, custom domains, and analytics retention, while the Pro plan increases or removes several of those limits.

Tools and capabilities

The Convika MCP server exposes tools in several groups:

• Create and manage sites and pages, including create_landing_page_preview, create_landing_page, create_site, update_site, save_page_content, and get_page_structure.
• Preview, publish, roll back, unpublish, and claim pages.
• Create forms, retrieve or export submissions, and configure goals.
• Query analytics summaries and details, portfolio results, time series, segments, source quality, CTA performance, and trends.
• Configure site URLs and custom domains, check verification, and manage domain routes.
• Check connectivity with ping or retrieve a referral link.

Limitations and notes

The repository contains documentation and a server manifest, not the Convika service implementation. The MCP endpoint is hosted by Convika, so local deployment of the server is not described. Publishing is a distinct action from preview creation, but users should still review generated content before asking the agent to publish it.

Plan limits affect practical use. The free tier allows 10 pages, 10,000 monthly pageviews, 50 monthly form entries, one custom domain, 90 days of visitor statistics, and a Convika badge. Pro provides 50 pages, unlimited form entries and custom domains, no badge, and a 14-day trial.