Side-by-Side Model Context Protocol Comparison
Infranodus MCP Server Infranodus vs Lens
In-depth architectural comparison of the Infranodus MCP Server Infranodus and Lens MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Infranodus MCP Server Infranodus
Research · Local stdio
Quality: 68/100 (Great) | Auth: API Key required
Lens
Research · Local stdio
Quality: 39/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Infranodus MCP Server Infranodus if you need specialized Research tools running via a local process. Choose Lens if your workspace requires Research integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose Infranodus MCP Server Infranodus when:
- You need dedicated capabilities in the Research domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: API Key required (Free / Open Source).
- Primary tools included: generate_knowledge_graph, create_knowledge_graph, generate_ontology_graph.
L
Choose Lens when:
- You need dedicated capabilities in the Research domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
Feature & Specification Comparison
Tools & Capabilities Breakdown
Infranodus MCP Server Infranodus Tools (40)
generate_knowledge_graph
Generate a knowledge graph with main topics, topical clusters, concepts, concepts (nodes) relations (edges) and structural gaps. Only use when explicitly asked to analyze a text or generate a knowledge graph. Do not use for short clarifying questions that you already have an answer to from the context of the conversation.
create_knowledge_graph
Create a knowledge graph in InfraNodus from text or from a URL, save it, and provide its name and a link to it for future use.
generate_ontology_graph
Use AI to generate a reasoning ontology knowledge graph (entities and the relations between them) and optionally save it as a InfraNodus graph. Three sources, provide exactly one: prompt (a topic — one AI call), text (a long document or a structural digest of a project, chunked server-side), or sourceGraphName (an existing graph — e.g. a fully ingested repo, vault, or corpus — whose statements are read back, chunked, and condensed into an ontology). Set ontologyMode: 'codebase' for software projects, or 'procedural' to write a DIGEST of how the project works (prose statements with [[wikilinks]], not relation triples) from an already-uploaded graph — save it as <repo|vault>-<project>-digest for optimize_knowledge_base. Use to get a rich overview, a reasoning map of a topic, or a condensed 'how it fits together' graph of a large corpus.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Infranodus MCP Server Infranodus Configuration
Lens Configuration