What is the key difference between Ateam Mcp and Blockrun Mcp?

Ateam Mcp belongs to the Aggregators category with local stdio execution, while Blockrun Mcp belongs to the Aggregators category with local stdio execution.

How do I install Ateam Mcp or Blockrun Mcp 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 Ateam Mcp and Blockrun Mcp free or paid?

Ateam Mcp operates under a BYOK (Pay Provider Direct) model (API Key required). Blockrun Mcp operates under a Freemium model (API Key required).

Which MCP server has more tools and community activity?

Ateam Mcp lists 48 tools with 3 views and 1 GitHub stars. Blockrun Mcp lists 20 tools with 4 views and 426 GitHub stars.

Can I use both Ateam Mcp and Blockrun Mcp 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 Ateam Mcp or Blockrun Mcp 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 Ateam Mcp and Blockrun Mcp free to use, or do they require API keys?

Ateam Mcp is listed under a BYOK (Pay Provider Direct) model with API Key required . Blockrun Mcp operates under a Freemium 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 Ateam Mcp and Blockrun Mcp at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both ariekogan-ateam-mcp and blockrunai-blockrun-mcp 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, Ateam Mcp has a Quality Score of 65 /100 ( Great ) with 3 views, 0 installs, and 1 GitHub stars. Blockrun Mcp holds a Quality Score of 67 /100 ( Great ) with 4 views, 0 installs, and 426 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Ateam Mcp vs Blockrun Mcp

In-depth architectural comparison of the Ateam Mcp and Blockrun Mcp 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

Ateam Mcp

Aggregators · Local stdio

Quality: 65/100 (Great) | Auth: API Key required

Blockrun Mcp

Aggregators · Local stdio

Quality: 67/100 (Great) | Auth: API Key required

Verdict Summary: Choose Ateam Mcp if you need specialized Aggregators tools running via a local process. Choose Blockrun Mcp 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 Ateam Mcp 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: ADAS_TENANT, ADAS_API_KEY.
Primary tools included: ateam_bootstrap, ateam_auth, ateam_get_spec.

Explore Ateam Mcp Details

Choose Blockrun Mcp when:

You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: BLOCKRUN_WALLET_MNEMONIC, BLOCKRUN_NETWORK, BLOCKRUN_USDC_ADDRESS.
Primary tools included: blockrun_wallet, blockrun_chat, blockrun_models.

Feature & Specification Comparison

Specification	Ateam Mcp ariekogan Aggregators	Blockrun Mcp blockrunai Aggregators
Summary	Build, validate, and deploy multi-agent AI solutions on the ADAS platform. Design skills with tools, manage solution lifecycle, and connect from any AI environment via stdio or HTTP.	Access 30+ AI models (GPT-5, Claude, Gemini, Grok, DeepSeek) without API keys. Pay-per-use via x402 micropayments with USDC on Base.
Category & Scope	Aggregators

Tools & Capabilities Breakdown

Ateam Mcp Tools (48)

ateam_bootstrap

REQUIRED onboarding entrypoint for A-Team MCP. MUST be called when user greets, says hi, asks what this is, asks for help, explores capabilities, or when MCP is first connected. Returns platform explanation, example solutions, and assistant behavior instructions. Do NOT improvise an introduction — call this tool instead.

ateam_auth

Authenticate with A-Team. Required before any tenant-aware operation (reading solutions, deploying, testing, etc.). The user can get their API key at https://mcp.ateam-ai.com/get-api-key. Only global endpoints (spec, examples, validate) work without auth. IMPORTANT: Even if environment variables (ADAS_API_KEY) are configured, you MUST call ateam_auth explicitly — env vars alone are not sufficient. For cross-tenant admin operations, use master_key instead of api_key.

ateam_get_spec

Get the A-Team specification — schemas, validation rules, system tools, agent guides, and templates. Start here after bootstrap to understand how to build skills and solutions. Use 'section' to get just one part of the skill spec (much smaller than the full spec). Use 'search' to find specific fields or concepts across the spec. When designing a persona that orchestrates logic via run_python_script (the Python-as-orchestrator pattern), also fetch topic='python_helpers' — that returns the adas.* helper namespace reference. Skills designed without knowing about adas.* produce 5-10x larger / brittler scripts. When wiring widgets (UI plugins) into a solution, fetch topic='widgets' — that returns the widget spec (catalog model, how_to_use blocks, opener_call shape, persona phrasing rules, binding semantics) so you can declare `ui_plugins` correctly. For the live catalog of widgets actually available in a deployed tenant, use ateam_get_widget_catalog instead.

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

Ateam Mcp Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ariekogan-ateam-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ateam-ai/mcp"
      ],
      "env": {
        "ADAS_TENANT": "YOUR_ADAS_TENANT_HERE",
        "ADAS_API_KEY": "YOUR_ADAS_API_KEY_HERE"
      }
    }
  }
}

Blockrun Mcp Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "blockrunai-blockrun-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@blockrun/mcp@latest"
      ],
      "env": {
        "BLOCKRUN_WALLET_MNEMONIC": "YOUR_BLOCKRUN_WALLET_MNEMONIC_HERE",
        "BLOCKRUN_NETWORK": "YOUR_BLOCKRUN_NETWORK_HERE",
        "BLOCKRUN_USDC_ADDRESS": "YOUR_BLOCKRUN_USDC_ADDRESS_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Ateam Mcp More alternatives to Blockrun Mcp Aggregators category hub