Lens

What the lens MCP server does

The lens MCP server connects an AI assistant to Mindola's hosted platform for creating public AI pages called lenses. A lens is built from material you provide, such as writing, notes, documents, links, articles, or course content. Visitors use its shareable page to ask questions in chat or through a live voice call.

Answers are restricted to the lens's supplied knowledge and include citations to the relevant sources. When the material does not cover a question, the lens can say that it does not know rather than filling the gap with an unsupported answer. Unanswered questions can also be sent to the owner's inbox with visitor information attached.

How it works

The lens MCP server is remote and hosted by Mindola. You add its MCP URL to a compatible client; there is no local package, process, or repository build to run. An assistant can gather the profile details, show a proposed profile for confirmation, and then call the creation tool.

Creating a lens returns a public share URL along with a claim URL and management-related details. A newly created lens can be unclaimed and live immediately. Without being claimed, it expires after 30 days. During that period, more knowledge can be added through the assistant. After claiming, changes are managed through the Mindola application or authenticated developer API.

Knowledge ingestion runs in the background. The assistant can add pages or other material, then call the status tool repeatedly until the knowledge counts indicate that processing is complete.

Setup and configuration

Connect the lens MCP server at https://app.mindola.ai/mcp/lens. Claude Code uses an HTTP transport command, while Cursor uses a URL entry in its MCP configuration. Claude Desktop and claude.ai can add the same address as a custom connector. Installation is otherwise configuration-only because the service is hosted.

The documentation also provides installation guidance for VS Code, Codex CLI, Windsurf, Gemini CLI, and ChatGPT. No environment variables or local credentials are specified for the MCP connection. For REST API use, Mindola provides a separate API-key-based interface for creating and managing lenses.

Tools and capabilities

The exposed tools are:

• create_digital_twin_lens: creates a lens from the profile information confirmed in the conversation and returns URLs and creation details.
• add_lens_knowledge: adds material such as articles or pages to an existing unclaimed lens for ingestion.
• get_lens_status: reports ingestion and knowledge status so an assistant can determine when content is ready.

The hosted product also supports cited answers, out-of-scope refusals, live voice calls with interruption support, lead capture for unanswered questions, and optional Stripe Connect payments. These are properties of Mindola lenses rather than additional MCP tools listed in the provided material.

Limitations and notes

The lens MCP server does not provide source code for the hosted service; the repository contains documentation and examples, while the server runs inside Mindola. Mindola controls the retrieval, answer grounding, citation behavior, public page, and hosting, so it is not intended for developers who need full control over models, data location, retrieval ranking, or an embedded custom pipeline.

The creation flow requires explicit confirmation before anything is created, and the assistant should use only information supplied or confirmed in the conversation. Unclaimed lenses have a 30-day expiration, and claimed lenses require the app or authenticated developer API for later changes.