HAL vs Scrivener MCP — MCP Server Comparison | AllMCPs
HAL vs Scrivener MCP
A side-by-side look at the HAL and Scrivener MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose HAL for developer tools work as a local process; choose Scrivener MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose HAL when
You need dedicated capabilities in the Developer Tools domain.
You prefer a local stdio subprocess transport.
Its auth model fits you: No auth required.
You have the keys it needs: HAL_SWAGGER_FILE, HAL_API_BASE_URL, HAL_SECRET_API_KEY, HAL_WHITELIST_URLS, HAL_BLACKLIST_URLS, HAL_ALLOW_MICROSOFT.
You want tools like http-get, http-post, http-put.
http-getMake an HTTP GET request to a specified URL. Supports secret substitution using {secrets.key} syntax where 'key' corresponds to HAL_SECRET_KEY environment variables.
http-postMake an HTTP POST request to a specified URL with optional body and headers. Supports secret substitution using {secrets.key} syntax in URL, headers, and body where 'key' corresponds to HAL_SECRET_KEY environment variables.
http-putMake an HTTP PUT request to a specified URL with optional body and headers. Supports secret substitution using {secrets.key} syntax in URL, headers, and body where 'key' corresponds to HAL_SECRET_KEY environment variables.
http-patchMake an HTTP PATCH request to a specified URL with optional body and headers. Supports secret substitution using {secrets.key} syntax in URL, headers, and body where 'key' corresponds to HAL_SECRET_KEY environment variables.
http-deleteMake an HTTP DELETE request to a specified URL with optional headers. Supports secret substitution using {secrets.key} syntax in URL and headers where 'key' corresponds to HAL_SECRET_KEY environment variables.
http-headMake an HTTP HEAD request to a specified URL with optional headers (returns only headers, no body). Supports secret substitution using {secrets.key} syntax in URL and headers where 'key' corresponds to HAL_SECRET_KEY environment variables.
http-optionsMake an HTTP OPTIONS request to a specified URL to check available methods and headers. Supports secret substitution using {secrets.key} syntax in URL and headers where 'key' corresponds to HAL_SECRET_KEY environment variables.
list-secretsGet a list of available secret keys that can be used with {secrets.key} syntax. Only shows the key names, never the actual secret values.
Scrivener MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
HAL is categorized under Developer Tools and uses a local stdio subprocess. Scrivener MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick HAL for developer tools work and Scrivener MCP for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
HAL is listed as free. Auth: no auth required. Scrivener MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add hal and writerslogic-scrivener-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, HAL has a quality signal of 61/100 (Good) with 2 views, 0 installs and 38 GitHub stars. Scrivener MCP has 61/100 (Good) with 18 views, 12 installs and 67 GitHub stars.