Touch Browser vs Research Toolkit
A side-by-side look at the Touch Browser and Research Toolkit MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
R
Research ToolkitResearchResearch methods, workflow tools, and independent review for AI agents, packaged as a Skill, plugin, and local MCP server.49FairAuth: no auth requiredVerdict: choose Touch Browser for research work as a local process; choose Research Toolkit for research. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Touch Browser when
- You need dedicated capabilities in the Research domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
RChoose Research Toolkit when
- You need dedicated capabilities in the Research domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | R Research Toolkit | |
|---|---|---|
| Category | Research | Research |
| Quality signal | 51/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 10 | 263 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Touch Browser | View Research Toolkit |
Tools & capabilities
Touch Browser tools
No tool names declared yet. Check the project README from the listing page.
Research Toolkit 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.
Touch Browser
{
"mcpServers": {
"nangman-infra-touch-browser": {
"command": "npx",
"args": [
"-y",
"@nangman-infra/touch-browser-mcp"
]
}
}
}
Research Toolkit
No confirmed install command for Research Toolkit yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Touch Browser is categorized under Research and uses a local stdio subprocess. Research Toolkit belongs to Research and uses an install path we have not confirmed yet. Pick Touch Browser for research work and Research Toolkit for research.
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. Research Toolkit has no confirmed install command yet — follow its own setup instructions.
Touch Browser is listed as free. Auth: no auth required. Research Toolkit 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 nangman-infra-touch-browser and research-toolkit as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Touch Browser has a quality signal of 51/100 (Good) with 3 views, 0 installs and 10 GitHub stars. Research Toolkit has 49/100 (Fair) with 0 views, 0 installs and 263 GitHub stars.