What is the key difference between Contract Compass and Fylings?

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

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

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

Which MCP server has more tools and community activity?

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

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

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

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

Side-by-Side Model Context Protocol Comparison

Contract Compass vs Fylings

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

Contract Compass

Legal · Local stdio

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

Fylings

Legal · Local stdio

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

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

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

Feature & Specification Comparison

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

Tools & Capabilities Breakdown

Contract Compass Tools (0)

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

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

Contract Compass Configuration

mcpServers (Claude Desktop / Cursor)

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

Fylings Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Contract Compass More alternatives to Fylings Legal category hub