Clevra vs Jira Alerts (JSM Operations)
A side-by-side look at the Clevra and Jira Alerts (JSM Operations) MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
ClevraSupport & Service Management · Remote HTTP/SSEField service management for trades: clients, jobs, estimates, invoices, schedule and reports.37FairAuth: not declaredVerdict: choose Clevra for support & service management work over a hosted endpoint; choose Jira Alerts (JSM Operations) for support & service management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
CChoose Clevra when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a remote HTTP/SSE transport.
Choose Jira Alerts (JSM Operations) when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
JSM_CLOUD_ID, JSM_EMAIL, JSM_API_TOKEN, JSM_OAUTH_TOKEN, JSM_TOOLSETS, JSM_READ_ONLY, TRANSPORT, PORT.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Clevra | |
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 37/100 · Fair | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | JSM_CLOUD_IDJSM_EMAILJSM_API_TOKENJSM_OAUTH_TOKENJSM_TOOLSETSJSM_READ_ONLYTRANSPORTPORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 4 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Clevra | View Jira Alerts (JSM Operations) |
Tools & capabilities
Clevra tools
No tool names declared yet. Check the project README from the listing page.
Jira Alerts (JSM Operations) 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.
Clevra
{
"mcpServers": {
"clevra": {
"url": "https://clevra.ai/mcp"
}
}
}
Jira Alerts (JSM Operations)
{
"mcpServers": {
"jira-alerts-jsm-operations": {
"command": "npx",
"args": [
"-y",
"jira-alerts-mcp"
],
"env": {
"JSM_CLOUD_ID": "YOUR_JSM_CLOUD_ID_HERE",
"JSM_EMAIL": "YOUR_JSM_EMAIL_HERE",
"JSM_API_TOKEN": "YOUR_JSM_API_TOKEN_HERE",
"JSM_OAUTH_TOKEN": "YOUR_JSM_OAUTH_TOKEN_HERE",
"JSM_TOOLSETS": "YOUR_JSM_TOOLSETS_HERE",
"JSM_READ_ONLY": "YOUR_JSM_READ_ONLY_HERE",
"TRANSPORT": "YOUR_TRANSPORT_HERE",
"PORT": "YOUR_PORT_HERE"
}
}
}
}
Frequently asked questions
Clevra is categorized under Support & Service Management and uses a remote HTTP/SSE transport. Jira Alerts (JSM Operations) belongs to Support & Service Management and uses a local stdio subprocess. Pick Clevra for support & service management work and Jira Alerts (JSM Operations) 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.
Clevra has no declared pricing — check the project's own site. Jira Alerts (JSM Operations) 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 clevra and jira-alerts-jsm-operations as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Clevra has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Jira Alerts (JSM Operations) has 45/100 (Fair) with 1 views, 0 installs and 4 GitHub stars.