Server Details
Your agent tests pages, copy, and flows on simulated users while you build.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- victorgulchenko/mimiq-mcp
- GitHub Stars
- 0
- Server Listing
- Mimiq MCP
See and control every tool call
Available Tools
6 toolsmimiq.ask_audienceInspect
Run a survey question on a synthetic audience to gauge preferences, priorities, or opinions. Provide a question and 2-10 answer options. Each simulated persona votes independently with reasoning. Use for product decisions ("which feature should we build next?"), naming ("which product name resonates?"), positioning ("which value prop is strongest?"), or any audience preference question. Returns: each respondent's vote and reasoning.
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | Number of respondents (default 10, max 50). | |
| context | No | Additional context about the survey purpose. | Product validation survey |
| options | Yes | Answer options (2-10 choices). | |
| audience | Yes | Who to survey. E.g. "SaaS founders with 10-50 employees" or "mobile gamers aged 18-25". | |
| question | Yes | The survey question to ask. | |
| concurrency | No | Parallel survey workers (default 6). |
mimiq.test_componentInspect
Evaluate a UI component (button, card, form, modal, navigation, pricing table) by providing its HTML and/or text description. Use when you want feedback on whether a specific UI element is clear, trustworthy, and actionable. Simulated users evaluate clarity, trust signals, and whether they would interact with the component.
| Name | Required | Description | Default |
|---|---|---|---|
| goal | No | What the component should achieve, e.g. "get users to click the upgrade button". | |
| count | No | Number of simulated users (default 10, max 50). | |
| audience | No | Target audience for the component. | |
| component_html | No | The HTML of the component to evaluate. | |
| component_text | No | Text description of the component (alternative or supplement to HTML). | |
| timeout_seconds | No |
mimiq.test_copyInspect
Test copy on simulated users, or A/B test two variants head-to-head. Use when choosing between headlines, taglines, value propositions, email subject lines, CTA text, product descriptions, or any written content. For single variant: returns raw persona reactions and monologues. For two variants: returns both sets of raw results side by side for you to compare.
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | Simulated users per variant (default 10, max 50). | |
| audience | No | Target audience. E.g. "developers evaluating CI/CD tools" or "e-commerce shoppers". | |
| variant_a | Yes | The copy to test (or first variant for A/B comparison). | |
| variant_b | No | Optional second variant for A/B comparison. If provided, returns a winner. | |
| timeout_seconds | No |
mimiq.test_flowInspect
Deep interactive simulation of a multi-step user flow (signup, onboarding, checkout, multi-page funnel). Each simulated persona navigates the page interactively — clicking links, filling forms, reading content, making decisions at each step. Use this for complex flows where you need to find exactly WHERE users get stuck or abandon. Slower than test_page (uses real browser sessions) but reveals step-by-step journey issues. Returns: raw per-persona journey data with step-by-step actions and drop-off points.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Starting URL of the flow to test. For localhost, first create a cloudflared tunnel and pass the tunnel URL here. | |
| goal | No | What success looks like, e.g. "complete the signup and reach the dashboard". | |
| count | No | Number of simulated users (default 5, max 10). Each runs a full interactive browser session. | |
| audience | No | Target audience description. E.g. "small business owners looking for accounting software". | |
| bridge_id | No | Deprecated. Use cloudflared tunnel directly instead. | |
| max_steps | No | Maximum navigation steps per persona (default 15). | |
| timeout_seconds | No |
mimiq.test_pageInspect
Test a web page on simulated users to find UX issues, confusing copy, and conversion blockers. Use this BEFORE shipping any landing page, pricing page, signup flow, or marketing page. Simulated users scroll through the entire page like real visitors — seeing hero, features, pricing, CTAs, and footer — then react honestly about what confused them, where they dropped off, and why they left. Returns: raw per-persona results with actions, monologues, objections, and suggestions.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL to test. Must be publicly accessible. For localhost, first create a cloudflared tunnel and pass the tunnel URL here. | |
| goal | No | What the page is trying to achieve, e.g. "get visitors to sign up for the waitlist". | |
| count | No | Number of simulated users (default 10, max 50). More = higher confidence but slower. | |
| audience | No | Who should test this page. Natural language, e.g. "startup founders in SF" or "parents shopping for kids toys". If omitted, auto-detects from page content. | |
| bridge_id | No | Deprecated. Use cloudflared tunnel directly instead. | |
| timeout_seconds | No |
mimiq.test_textInspect
Test any text content on simulated users — positioning statements, feature descriptions, error messages, onboarding copy, instructions, announcements. Use when you want honest reactions to written content. Returns raw persona reactions, objections, and what they say would help.
| Name | Required | Description | Default |
|---|---|---|---|
| goal | No | What the text should achieve, e.g. "convince users to upgrade to the paid plan". | |
| text | Yes | The text content to test. | |
| count | No | Number of simulated users (default 10, max 50). | |
| audience | No | Target audience for the content. | |
| timeout_seconds | No |
Verify Ownership
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.
Sign in to verify ownershipControl your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.