Af360 vs Weeek MCP

In-depth architectural comparison of the Af360 and Weeek 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.

Which MCP Server Should You Choose?

A

Choose Af360 when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Af360 Details

Choose Weeek MCP when:

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

Explore Weeek MCP Details

Feature & Specification Comparison

Specification	A Af360 Developer Tools	Weeek MCP Developer Tools
Summary	Watches your local projects and sites read-only and names what would be lost.	Local MCP server for Weeek (stdio transport) — read-only by default, opt-in write tools.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

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

{
  "mcpServers": {
    "af360": {
      "url": "https://afeleos.com/af360"
    }
  }
}

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

Related MCP Server Comparisons