NativeKeel vs GroundTruth MCP
A side-by-side look at the NativeKeel and GroundTruth MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
N
NativeKeelDeveloper Tools · Local subprocess (stdio)React Native and Expo health check: upgrade blockers, store rules, crash risks, security findings41FairAuth: not declaredVerdict: choose NativeKeel for developer tools work as a local process; choose GroundTruth MCP 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?
NChoose NativeKeel when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
NATIVEKEEL_MCP_ROOTS.
Choose GroundTruth MCP 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:
GT_GITHUB_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | N NativeKeel | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 41/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | NATIVEKEEL_MCP_ROOTS |
Tools & capabilities
NativeKeel tools
No tool names declared yet. Check the project README from the listing page.
GroundTruth 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.
NativeKeel
{
"mcpServers": {
"nativekeel": {
"command": "npx",
"args": [
"-y",
"nativekeel"
],
"env": {
"NATIVEKEEL_MCP_ROOTS": "YOUR_NATIVEKEEL_MCP_ROOTS_HERE"
}
}
}
}
GroundTruth MCP
{
"mcpServers": {
"rm-rf-prod-groundtruth-mcp": {
"command": "npx",
"args": [
"-y",
"@groundtruth-mcp/gt-mcp@latest"
],
"env": {
"GT_GITHUB_TOKEN": "YOUR_GT_GITHUB_TOKEN_HERE"
}
}
}
}
Frequently asked questions
NativeKeel is categorized under Developer Tools and uses a local stdio subprocess. GroundTruth MCP belongs to Developer Tools and uses a local stdio subprocess. Pick NativeKeel for developer tools work and GroundTruth MCP 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.
NativeKeel has no declared pricing — check the project's own site. GroundTruth 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 nativekeel and rm-rf-prod-groundtruth-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, NativeKeel has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. GroundTruth MCP has 56/100 (Good) with 3 views, 0 installs and 6 GitHub stars.
