What is the key difference between Keywordise and ScratchRun?

Keywordise belongs to the Developer Tools category with cloud HTTP/SSE execution, while ScratchRun belongs to the Developer Tools category with local stdio execution.

How do I install Keywordise or ScratchRun 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 Keywordise and ScratchRun free or paid?

Keywordise operates under a Free / Open Source model (No auth required). ScratchRun operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Keywordise lists 0 tools with 0 views and 0 GitHub stars. ScratchRun lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Keywordise and ScratchRun 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

Keywordise vs ScratchRun

In-depth architectural comparison of the Keywordise and ScratchRun 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

Keywordise

Developer Tools · Remote HTTP/SSE

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

ScratchRun

Developer Tools · Local stdio

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

Verdict Summary: Choose Keywordise if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose ScratchRun 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 Keywordise 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 Keywordise Details

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

Feature & Specification Comparison

Specification	K Keywordise Developer Tools	ScratchRun Developer Tools
Summary	Auto-apply to jobs: matches your CV, tailors a fresh CV per posting, and applies for you.	Ephemeral MicroVM-isolated code execution for AI agents. Fresh VM per call, hard-purged after.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Keywordise Tools (0)

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

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

Keywordise Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "keywordise": {
      "url": "https://keywordise.com/"
    }
  }
}

ScratchRun Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Keywordise is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, ScratchRun belongs to Developer Tools using local stdio subprocess. Select Keywordise when you need capabilities focused on developer tools and ScratchRun when you require tools for developer tools.

More alternatives to Keywordise More alternatives to ScratchRun Developer Tools category hub