Freshdesk vs Weav
A side-by-side look at the Freshdesk and Weav MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Freshdesk for support & service management work as a local process; choose Weav for support & service management over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Freshdesk when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
FRESHDESK_DOMAIN, FRESHDESK_API_KEY.
Choose Weav when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
status, priority, type.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 40/100 · Fair | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | FRESHDESK_DOMAINFRESHDESK_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Freshdesk | View Weav |
Tools & capabilities
Freshdesk tools
No tool names declared yet. Check the project README from the listing page.
Weav tools 3
status`open` or `closed`priority`low`, `normal`, `high`, or `urgent`type`text`, `qa`, or `url`
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.
Freshdesk
{
"mcpServers": {
"freshdesk-3": {
"command": "npx",
"args": [
"-y",
"github:WYRE-AI/freshdesk-mcp"
],
"env": {
"FRESHDESK_DOMAIN": "YOUR_FRESHDESK_DOMAIN_HERE",
"FRESHDESK_API_KEY": "YOUR_FRESHDESK_API_KEY_HERE"
}
}
}
}
Weav
{
"mcpServers": {
"weav": {
"url": "https://mcp.weav.com/mcp"
}
}
}
Frequently asked questions
Freshdesk is categorized under Support & Service Management and uses a local stdio subprocess. Weav belongs to Support & Service Management and uses a remote HTTP/SSE transport. Pick Freshdesk for support & service management work and Weav for support & service management.
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.
Freshdesk has no declared pricing — check the project's own site. Weav has no declared pricing — check the project's own site. 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 freshdesk-3 and weav as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Freshdesk has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Weav has 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.