Klussenbeheer vs MCP Atlassian
A side-by-side look at the Klussenbeheer and MCP Atlassian MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
K
KlussenbeheerSupport & Service ManagementJob management for Dutch service companies: jobs, customers, planning, quotes and invoices.48FairAuth: oauth 2.0Verdict: choose Klussenbeheer for support & service management work; choose MCP Atlassian 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?
KChoose Klussenbeheer when
- You need dedicated capabilities in the Support & Service Management domain.
- Its auth model fits you: OAuth 2.0.
- You want tools like
zoek_klanten, vandaag, klus_detail.
Choose MCP Atlassian when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
JIRA_URL, JIRA_USERNAME, JIRA_API_TOKEN, JIRA_PERSONAL_TOKEN, CONFLUENCE_URL, CONFLUENCE_USERNAME, CONFLUENCE_API_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | K Klussenbeheer | |
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 48/100 · Fair | 51/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | OAuth 2.0 | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | JIRA_URLJIRA_USERNAMEJIRA_API_TOKENJIRA_PERSONAL_TOKENCONFLUENCE_URLCONFLUENCE_USERNAMECONFLUENCE_API_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 6,010 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 9 | Not listed |
| Full listing | View Klussenbeheer | View MCP Atlassian |
Tools & capabilities
Klussenbeheer tools 9
zoek_klantenSearch customers and jobs.vandaagToday's work, the planning and a status overview.klus_detailRead, create and update a job.klus_inplannenSchedule, assign and move a job to another stage.notitie_toevoegenAdd notes, work lines and mileage.klant_toevoegenCreate or update customers and share a customer link.offerte_makenDraft, send and list quotes.openstaande_facturenOpen invoices and invoice status.berichtenMessages, customer mail, team and account info.
MCP Atlassian 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.
Klussenbeheer
No confirmed install command for Klussenbeheer yet — follow the setup steps linked from its listing page rather than a guessed package name.
MCP Atlassian
{
"mcpServers": {
"sooperset-mcp-atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian"
],
"env": {
"JIRA_URL": "YOUR_JIRA_URL_HERE",
"JIRA_USERNAME": "YOUR_JIRA_USERNAME_HERE",
"JIRA_API_TOKEN": "YOUR_JIRA_API_TOKEN_HERE",
"JIRA_PERSONAL_TOKEN": "YOUR_JIRA_PERSONAL_TOKEN_HERE",
"CONFLUENCE_URL": "YOUR_CONFLUENCE_URL_HERE",
"CONFLUENCE_USERNAME": "YOUR_CONFLUENCE_USERNAME_HERE",
"CONFLUENCE_API_TOKEN": "YOUR_CONFLUENCE_API_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Klussenbeheer is categorized under Support & Service Management and uses an install path we have not confirmed yet. MCP Atlassian belongs to Support & Service Management and uses a local stdio subprocess. Pick Klussenbeheer for support & service management work and MCP Atlassian 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. Klussenbeheer has no confirmed install command yet — follow its own setup instructions.
Klussenbeheer has no declared pricing — check the project's own site. Auth: oauth 2.0. MCP Atlassian is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 klussenbeheer and sooperset-mcp-atlassian as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Klussenbeheer has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCP Atlassian has 51/100 (Good) with 1 views, 0 installs and 6,010 GitHub stars.