What is the key difference between Eyeot ERP and Sdk?

Eyeot ERP belongs to the Aggregators category with local stdio execution, while Sdk belongs to the Aggregators category with local stdio execution.

How do I install Eyeot ERP or Sdk 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 Eyeot ERP and Sdk free or paid?

Eyeot ERP operates under a Free / Open Source model (No auth required). Sdk operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Eyeot ERP lists 0 tools with 0 views and 0 GitHub stars. Sdk lists 578 tools with 4 views and 7 GitHub stars.

Can I use both Eyeot ERP and Sdk 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 Eyeot ERP or Sdk 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 Eyeot ERP and Sdk free to use, or do they require API keys?

Eyeot ERP is listed under a Free / Open Source model with No auth required . Sdk operates under a BYOK (Pay Provider Direct) model with API Key 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 Eyeot ERP and Sdk at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both eyeot-erp and 2s-io-sdk 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, Eyeot ERP has a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Sdk holds a Quality Score of 63 /100 ( Good ) with 4 views, 0 installs, and 7 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Eyeot ERP vs Sdk

In-depth architectural comparison of the Eyeot ERP and Sdk 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

Eyeot ERP

Aggregators · Local stdio

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

Sdk

Aggregators · Local stdio

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

Verdict Summary: Choose Eyeot ERP if you need specialized Aggregators tools running via a local process. Choose Sdk if your workspace requires Aggregators integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Eyeot ERP when:

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

Explore Eyeot ERP Details

Choose Sdk when:

You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: EVM_PRIVATE_KEY, TWOS_TRIAL.
Primary tools included: search.endpoints, batch.run, soil.profile.

Explore Sdk Details

Feature & Specification Comparison

Specification	E Eyeot ERP Aggregators	Sdk 2s-io Aggregators
Summary	ERP français avec serveur MCP natif : plus de 1 800 actions métier auto-générées via OpenAPI.	Unified API for AI agents — 180+ tools across geocoding, weather (NWS), climate stations (NOAA), earthquakes (USGS), tides (NOAA), points of interest (OpenStreetMap), patents (USPTO ODP), US case law (CourtListener / Free Law Project), Federal Register, Wikipedia, scientific papers (arXiv / PubMed / Semantic Scholar), AI summarize / translate / extract / screenshot / image-describe, image compression, DNS / WHOIS, crypto address-validate + EVM gas oracle, OFAC sanctions screening, US Census ACS demographics, airport / ZIP lookup. Sub-cent to a few cents per call in USDC on Base via x402 — no API keys, no signup. npx -y @2sio/mcp
Category & Scope

Tools & Capabilities Breakdown

Eyeot ERP Tools (0)

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

Sdk Tools (578)

search.endpoints

Find the right 2s endpoint(s) for a task using a natural-language query (e.g. "screen a company for sanctions", "decode a VIN", "check a domain's email security"). Returns ranked matches with id, path, method, price, and description. Use this to discover capabilities before calling.

batch.run

Run up to 50 endpoint calls behind ONE x402 payment. Price = exact sum of the sub-call prices (no discount). Atomic: every sub-call must succeed or nothing is charged (failures are returned so you can retry for free). Sub-calls must be ordinary catalog endpoints (no bearer-only, deprecated, variable-priced, or metered-upstream endpoints; no nested batch). Each item carries that endpoint's own response in `data`.

soil.profile

Ground-truth soil profile for any US lat/lng from USDA-NRCS SSURGO. Returns the soil map unit + component soil types ranked by composition %, each with taxonomic order/class, drainage class, hydrologic group, and slope. Keyless, public-domain. For agronomy, land/septic/foundation suitability, hydrology, crop-fit. Water/unsurveyed points return an empty component list.

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

Eyeot ERP Configuration

mcpServers (Claude Desktop / Cursor)

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

Sdk Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "2s-io-sdk": {
      "command": "npx",
      "args": [
        "-y",
        "@2sio/mcp"
      ],
      "env": {
        "EVM_PRIVATE_KEY": "YOUR_EVM_PRIVATE_KEY_HERE",
        "TWOS_TRIAL": "YOUR_TWOS_TRIAL_HERE"
      }
    }
  }
}

Frequently Asked Questions

Eyeot ERP is categorized under Aggregators and uses a local stdio subprocess. In contrast, Sdk belongs to Aggregators using local stdio subprocess. Select Eyeot ERP when you need capabilities focused on aggregators and Sdk when you require tools for aggregators.

More alternatives to Eyeot ERP More alternatives to Sdk Aggregators category hub Canonical compare URL