What is the key difference between Lexapi Mcp and WizerAPI Contract Intelligence?

Lexapi Mcp belongs to the Legal category with local stdio execution, while WizerAPI Contract Intelligence belongs to the Legal category with local stdio execution.

How do I install Lexapi Mcp or WizerAPI Contract Intelligence in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Lexapi Mcp and WizerAPI Contract Intelligence free or paid?

Lexapi Mcp operates under a Freemium model (API Key required). WizerAPI Contract Intelligence operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Lexapi Mcp lists 10 tools with 2 views and 3 GitHub stars. WizerAPI Contract Intelligence lists 0 tools with 1 views and 0 GitHub stars.

Can I use both Lexapi Mcp and WizerAPI Contract Intelligence together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install Lexapi Mcp or WizerAPI Contract Intelligence in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Lexapi Mcp and WizerAPI Contract Intelligence free to use, or do they require API keys?

Lexapi Mcp is listed under a Freemium model with API Key required . WizerAPI Contract Intelligence operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Lexapi Mcp and WizerAPI Contract Intelligence at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both lex-api-lexapi-mcp and wizerapi-contract-intelligence as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Lexapi Mcp has a Quality Score of 60 /100 ( Good ) with 2 views, 0 installs, and 3 GitHub stars. WizerAPI Contract Intelligence holds a Quality Score of 27 /100 ( Emerging ) with 1 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Lexapi Mcp vs WizerAPI Contract Intelligence

In-depth architectural comparison of the Lexapi Mcp and WizerAPI Contract Intelligence 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

Lexapi Mcp

Legal · Local stdio

Quality: 60/100 (Good) | Auth: API Key required

WizerAPI Contract Intelligence

Legal · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Lexapi Mcp if you need specialized Legal tools running via a local process. Choose WizerAPI Contract Intelligence if your workspace requires Legal integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Lexapi Mcp when:

You need dedicated capabilities in the Legal domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: LEXAPI_API_KEY, LEXAPI_BASE_URL.
Primary tools included: lex_search, lex_get_document, lex_get_metadata.

Explore Lexapi Mcp Details

Choose WizerAPI Contract Intelligence when:

You need dedicated capabilities in the Legal domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore WizerAPI Contract Intelligence Details

Feature & Specification Comparison

Specification	Lexapi Mcp Lex-API Legal	W WizerAPI Contract Intelligence Legal
Summary
Category & Scope	Legal	Legal
Quality signal

Tools & Capabilities Breakdown

Lexapi Mcp Tools (10)

lex_search

Structured EUR-Lex search (text, dates, document type, author, language).

lex_get_document

Full parsed document by CELEX — metadata + articles, sections, tables, annexes.

lex_get_metadata

Metadata only (faster than full content).

lex_get_document_by_url

Fetch by EUR-Lex URL (pasted from a browser).

lex_recent_documents

Recent Official Journal publications (default 7 days).

lex_cited_by

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).

Lexapi Mcp Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "lex-api-lexapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@lexapi/mcp"
      ],
      "env": {
        "LEXAPI_API_KEY": "YOUR_LEXAPI_API_KEY_HERE",
        "LEXAPI_BASE_URL": "YOUR_LEXAPI_BASE_URL_HERE"
      }
    }
  }
}

WizerAPI Contract Intelligence Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "wizerapi-contract-intelligence": {
      "command": "npx",
      "args": [
        "-y",
        "wizerapi-contract-intelligence"
      ]
    }
  }
}

Frequently Asked Questions

Lexapi Mcp is categorized under Legal and uses a local stdio subprocess. In contrast, WizerAPI Contract Intelligence belongs to Legal using local stdio subprocess. Select Lexapi Mcp when you need capabilities focused on legal and WizerAPI Contract Intelligence when you require tools for legal.

More alternatives to Lexapi Mcp More alternatives to WizerAPI Contract Intelligence Legal category hub