# Convika [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://convika.com/?utm_source=mcp_registry&utm_medium=referral&utm_campaign=mcp_directory  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/convika

## Description
Create, preview, publish, and measure landing pages from Claude, Codex, or any MCP client.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "convika": {
    "command": "npx",
    "args": ["-y","convika"]
  }
}
```

## Documentation

## What Convika does

Convika MCP server is positioned as an agent interface for landing-page workflows. It covers four listed activities: creating pages, previewing pages, publishing pages, and measuring page performance. The available description does not identify a page builder, analytics provider, hosting platform, or other external system, so those implementation details should not be assumed.

The server belongs to the 🎯 Marketing category. It may fit workflows where a developer wants an MCP client to handle landing-page operations rather than limiting the agent to text generation or planning. The listing does not describe page templates, supported content types, deployment targets, measurement metrics, or publishing controls.

## How it works

The advertised workflow starts from an MCP-compatible client. The listing names Claude and Codex and also says that Convika can be used from any MCP client. From that client, an agent can use Convika MCP server for the supported landing-page actions: create a page, preview it, publish it, and measure it.

No README or protocol-level documentation is available in the supplied material. As a result, the exact tool names, request parameters, response formats, authentication flow, and connection configuration cannot be documented here. Developers should verify those details in the project’s current documentation before implementing a client connection.

## Tools and capabilities

The stated capabilities are:

- Create landing pages.
- Preview landing pages before publishing.
- Publish landing pages.
- Measure landing-page results.

These capabilities describe the product scope, not a confirmed list of MCP tool names. The source does not specify whether the actions operate on drafts, existing pages, published URLs, or particular campaign objects. It also does not state which measurements are available or how results are returned.

## Limitations and notes

Convika MCP server should be evaluated against the landing-page features and client compatibility required by your workflow. The supplied description confirms access from Claude, Codex, and MCP clients generally, but it does not name specific desktop applications or editors. It also provides no information about authentication, environment variables, installation commands, licensing, rate limits, permissions, or supported publishing destinations.

Because the README is unavailable, this reference intentionally avoids claiming specific integrations or setup steps. Confirm the current connection method and the behavior of each landing-page operation before relying on Convika in production. The 🎯 Marketing classification reflects the listing’s category and does not by itself establish a particular analytics or advertising integration.

## Getting started with this Convika MCP server
Always refer to the official documentation for the most accurate and up-to-date information.

_Full upstream README: https://allmcps.com/mcp/convika/readme_