REA vs Testcollab MCP Server
A side-by-side look at the REA and Testcollab MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose REA for developer tools work as a local process; choose Testcollab MCP Server 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 REA 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.
Choose Testcollab MCP Server when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TC_API_TOKEN, TC_API_URL, TC_DEFAULT_PROJECT. - You want tools like
project_id, suite, filter.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 55/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Free |
| Required env vars | None listed | TC_API_TOKENTC_API_URLTC_DEFAULT_PROJECT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 330,567 | 4 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 6 |
| Full listing | View REA | View Testcollab MCP Server |
Tools & capabilities
REA tools
No tool names declared yet. Check the project README from the listing page.
Testcollab MCP Server tools 6
project_idProject ID (*required if `TC_DEFAULT_PROJECT` not set)suiteNofilterFilter conditionssortSort specificationlimitMax results (1-100, default: 50)offsetSkip N results (default: 0)
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.
REA
{
"mcpServers": {
"rea": {
"command": "npx",
"args": [
"-y",
"rea-agents"
]
}
}
}
Testcollab MCP Server
{
"mcpServers": {
"tcsoftinc-testcollab-mcp-server": {
"command": "npx",
"args": [
"-y",
"@testcollab/mcp-server"
],
"env": {
"TC_API_TOKEN": "YOUR_TC_API_TOKEN_HERE",
"TC_API_URL": "YOUR_TC_API_URL_HERE",
"TC_DEFAULT_PROJECT": "YOUR_TC_DEFAULT_PROJECT_HERE"
}
}
}
}
Frequently asked questions
REA is categorized under Developer Tools and uses a local stdio subprocess. Testcollab MCP Server belongs to Developer Tools and uses a local stdio subprocess. Pick REA for developer tools work and Testcollab MCP Server 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.
REA is listed as free. Auth: no auth required. Testcollab MCP Server is listed as free. Auth: api key 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 rea and tcsoftinc-testcollab-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, REA has a quality signal of 55/100 (Good) with 2 views, 0 installs and 330,567 GitHub stars. Testcollab MCP Server has 59/100 (Good) with 2 views, 0 installs and 4 GitHub stars.