What is the key difference between 404.directory and Apiosk?

404.directory belongs to the Developer Tools category with local stdio execution, while Apiosk belongs to the Developer Tools category with local stdio execution.

How do I install 404.directory or Apiosk 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 404.directory and Apiosk free or paid?

404.directory operates under a Free / Open Source model (No auth required). Apiosk operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

404.directory lists 0 tools with 0 views and 1 GitHub stars. Apiosk lists 0 tools with 0 views and 0 GitHub stars.

Can I use both 404.directory and Apiosk 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.

Side-by-Side Model Context Protocol Comparison

404.directory vs Apiosk

In-depth architectural comparison of the 404.directory and Apiosk 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

404.directory

Developer Tools · Local stdio

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

Apiosk

Developer Tools · Local stdio

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

Verdict Summary: Choose 404.directory if you need specialized Developer Tools tools running via a local process. Choose Apiosk if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose 404.directory 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 404.directory Details

Choose Apiosk 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 Apiosk Details

Feature & Specification Comparison

Specification	404.directory Developer Tools	Apiosk Developer Tools
Summary	Discover, verify, and execute curated read-only MCP tools through one trusted Agent gateway.	Discover, pay for, execute, and publish Apiosk APIs through MCP.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

404.directory Tools (0)

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

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

404.directory Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "404-directory-2": {
      "command": "npx",
      "args": [
        "-y",
        "skills"
      ]
    }
  }
}

Apiosk Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "apiosk": {
      "command": "npx",
      "args": [
        "-y",
        "@apiosk/mcp"
      ]
    }
  }
}

Frequently Asked Questions

404.directory is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Apiosk belongs to Developer Tools using local stdio subprocess. Select 404.directory when you need capabilities focused on developer tools and Apiosk when you require tools for developer tools.

More alternatives to 404.directory More alternatives to Apiosk Developer Tools category hub