The posh part of the city, what else could i add?
The online regions name is deepwired
u/deep_singh_baweja — 11 days ago
[Open Source] mcp-jira-scoped: A zero-trust Jira MCP server with server-side scope and project boundaries
​
When integrating AI agents (Claude Desktop, Cursor, Copilot) with enterprise Jira workspaces, access control presents a critical security challenge. Most community MCP servers still rely on legacy, unscoped API tokens that grant broad organizational access, relying entirely on the model to self-regulate its queries.
* **GitHub Repository:** [https://github.com/deepwired/mcp-jira\](https://github.com/deepwired/mcp-jira)
* **npm Registry:** [mcp-jira-scoped on npm](https://www.npmjs.com/package/mcp-jira-scoped)
To address this, we released mcp-jira (published on npm as mcp-jira-scoped), an open-source MCP server architected specifically around Atlassian's modern scoped API tokens and strict least-privilege principles.
Key Architectural Guardrails
Server-Side Scope Validation: Scopes are verified locally before any HTTP request reaches Atlassian's gateway (api.atlassian.com). Calls outside the granted scopes are rejected immediately without trusting the LLM to self-restrain.
JQL Containment: A project allowlist (JIRA_PROJECTS) wraps every JQL query server-side, preventing the model from escaping its sandboxed boundary through injected or hallucinated OR logic.
Destructive Action Protections: All deletions (issues, comments, worklogs, attachments) enforce an explicit confirm: true parameter, while administrative operations (such as workflow or project modifications) are omitted from the server entirely.
Modular Toolsets: The 44 available tools are partitioned into opt-in modules (Core, Agile, Versions, Filters) to prevent context bloat and tool-selection degradation in the LLM.
Credential Redaction: Tokens, base64 strings, and Basic authentication headers are stripped from error traces before they can leak into model context.
Implementation
You can evaluate the server without persistent installation:
npx -y mcp-jira-scoped
```[span_9](start_span)[span_9](end_span)
* **GitHub Repository:** [https://github.com/deepwired/mcp-jira\](https://github.com/deepwired/mcp-jira)
* **npm Registry:** [mcp-jira-scoped on npm](https://www.npmjs.com/package/mcp-jira-scoped)
We welcome technical feedback, bug reports, and pull requests from DevSecOps and platform engineering teams.
u/deep_singh_baweja — 15 days ago
TheoTown - Hands down the best Mobile city builder game
Let me know what you guys think, but truly this game is wonderful, you guys should check it out
u/deep_singh_baweja — 23 days ago
▲ 23 r/TheoTown
My massive setup, military, navy, beaches, skylines, monuments
I really love this game, keeps me sane.
u/deep_singh_baweja — 24 days ago
[Release] mcp-jira v2.0.0: The Jira MCP server built for modern scoped API tokens (with server-side scope enforcement)
Hey everyone, version 2.0.0 of the Jira MCP server is out, designed specifically to fix the blast-radius and security issues of letting an AI agent loose in your Atlassian workspace.
Most existing Jira MCP servers use classic, unscoped API tokens with basic auth against yoursite.atlassian.net. This server is built from the ground up for Atlassian's modern api.atlassian.com gateway, using scoped API tokens.
Here is why that matters for your agentic workflows:
Security & Blast-Radius Controls
Zero-Trust AI:
The AI is never trusted to restrain itself. The server enforces your granted scopes server-side before any API call is made.
Hard Project Boundaries: You can pass a JIRA_PROJECTS allowlist (e.g., JIRA_PROJECTS=PROJ,OPS). Requests naming outside projects are blocked immediately, and JQL searches are wrapped server-side so the AI cannot escape the list.
Fail-Safe Defaults:
If no JIRA_SCOPES are provided, the server defaults to read-only tools.
Explicit Confirmations:
All destructive operations (deleting issues, comments, attachments, worklogs, and links) require a confirm: true parameter.
Credential Masking:
The raw token, its base64 form, and Basic headers are stripped from every error message before it reaches the model.
No Admin Ops:
The server completely omits tools for project creation, deletion, workflow changes, or webhook management.
What's new in v2.0.0 (Breaking Changes)
The default content format returned to the model is now Markdown.
The jira_search tool now paginates on nextPageToken instead of startAt.
An unrecognized JIRA_SCOPES value now intentionally crashes the server at startup rather than silently dropping the scope, so you know exactly what permissions are active.
Tool Management
There are 44 tools available, which is past the point where model tool-selection degrades. To solve this, tools are grouped into modular sets.
Common tools (Core, Users, Attachments, Links, Worklogs, Metadata) load by default, while specialized sets like Agile (boards and sprints), Versions, Filters, and Labels are opt-in.
Getting Started
Note on package naming: While the GitHub repo is named mcp-jira, the npm package is currently mcp-jira-scoped.
You can run it immediately with:
npx -y mcp-jira-scoped
Check out the full setup guide, scope mapping, and repo here:
u/deep_singh_baweja — 25 days ago