A side-by-side look at the MCP Typescribe and Reactuse MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Typescribe for developer tools work as a local process; choose Reactuse for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Typescribe when
You need dedicated capabilities in the Developer Tools domain.
No tool names declared yet. Check the project README from the listing page.
Reactuse 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.
MCP Typescribe is categorized under Developer Tools and uses a local stdio subprocess. Reactuse belongs to Developer Tools and uses a local stdio subprocess. Pick MCP Typescribe for developer tools work and Reactuse for developer tools.
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.
MCP Typescribe is listed as free. Auth: no auth required. Reactuse 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 yworks-mcp-typescribe and childrentime-reactuse as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Typescribe has a quality signal of 44/100 (Fair) with 2 views, 0 installs and 46 GitHub stars. Reactuse has 63/100 (Good) with 4 views, 0 installs and 1,065 GitHub stars.