Atlassian MCP Server vs Vedaksha
A side-by-side look at the Atlassian MCP Server and Vedaksha MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Atlassian MCP Server for version control work over a hosted endpoint; choose Vedaksha for spirituality & esoterica as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Atlassian MCP Server when
- You need dedicated capabilities in the Version Control domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: other.
Choose Vedaksha when
- You need dedicated capabilities in the Spirituality & Esoterica domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
VEDAKSHA_MCP_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Spirituality & Esoterica |
| Quality signal | 80/100 · Excellent | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | VEDAKSHA_MCP_TOKEN |
| Verified owner | Verified | Community listing |
| GitHub stars | 1,120 | 4 |
| Directory activity | 9 views 0 installs 1 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Atlassian MCP Server | View Vedaksha |
Tools & capabilities
Atlassian MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Vedaksha 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.
Atlassian MCP Server
{
"mcpServers": {
"atlassian-mcp-server": {
"url": "https://mcp.atlassian.com/v2/mcp"
}
}
}
Vedaksha
{
"mcpServers": {
"vedaksha": {
"command": "uvx",
"args": [
"vedaksha"
],
"env": {
"VEDAKSHA_MCP_TOKEN": "YOUR_VEDAKSHA_MCP_TOKEN_HERE"
}
}
}
}