What is the key difference between Fylings and Contract Compass?

Fylings belongs to the Legal category with local stdio execution, while Contract Compass belongs to the Legal category with local stdio execution.

How do I install Fylings or Contract Compass 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 Fylings and Contract Compass free or paid?

Fylings operates under a Free / Open Source model (No auth required). Contract Compass operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Fylings lists 0 tools with 0 views and 0 GitHub stars. Contract Compass lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Fylings and Contract Compass 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 Fylings or Contract Compass 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 Fylings and Contract Compass free to use, or do they require API keys?

Fylings is listed under a Free / Open Source model with No auth required . Contract Compass 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 Fylings and Contract Compass at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both fylings and contract-compass 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, Fylings has a Quality Score of 20 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Contract Compass holds a Quality Score of 40 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Fylings vs Contract Compass

In-depth architectural comparison of the Fylings and Contract Compass 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

Fylings

Legal · Local stdio

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

Contract Compass

Legal · Local stdio

Quality: 40/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Fylings if you need specialized Legal tools running via a local process. Choose Contract Compass 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 Fylings 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 Fylings Details

Choose Contract Compass 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 Contract Compass Details

Feature & Specification Comparison

Specification	F Fylings Legal	Contract Compass Legal
Summary	Search, verify & screen 1M+ African companies + their government contracts across 18 registries.	Korean public procurement law: rule-engine rulings, statutes search, live court precedents
Category & Scope	Legal	Legal
Quality signal

Tools & Capabilities Breakdown

Fylings Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Contract Compass Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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

Fylings Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "fylings": {
      "command": "npx",
      "args": [
        "-y",
        "fylings"
      ]
    }
  }
}

Contract Compass Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "contract-compass": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://contract.sallim.app/mcp"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Fylings More alternatives to Contract Compass Legal category hub Canonical compare URL