A side-by-side look at the Pro Reach LinkedIn Outreach and Dynatrace MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Pro Reach LinkedIn Outreach for monitoring work over a hosted endpoint; choose Dynatrace MCP for monitoring as a local process. You can also run both side by side in one mcpServers block.
DT_ENVIRONMENT, DT_MCP_TOKEN_STORAGE, DT_GRAIL_QUERY_BUDGET_GB.Rows where the two servers differ are marked.
| Spec | P Pro Reach LinkedIn Outreach | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 37/100 · Fair | 36/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Free |
| Required env vars | None listed | DT_ENVIRONMENTDT_MCP_TOKEN_STORAGEDT_GRAIL_QUERY_BUDGET_GB |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 137 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Pro Reach LinkedIn Outreach | View Dynatrace MCP |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"pro-reach-linkedin-outreach": {
"url": "https://proreach.ai/mcp"
}
}
}
{
"mcpServers": {
"dynatrace-oss-dynatrace-mcp": {
"command": "npx",
"args": [
"-y",
"@dynatrace-oss/dynatrace-mcp-server"
],
"env": {
"DT_ENVIRONMENT": "YOUR_DT_ENVIRONMENT_HERE",
"DT_MCP_TOKEN_STORAGE": "YOUR_DT_MCP_TOKEN_STORAGE_HERE",
"DT_GRAIL_QUERY_BUDGET_GB": "YOUR_DT_GRAIL_QUERY_BUDGET_GB_HERE"
}
}
}
}