Share Jira MCP tools.
Sprint and issue lookups for remote teammates — writes need your approval.
Run on your machine
Start the server on your host machine. Tools not listed in --allow are completely hidden from the agent.
npx -y @mcpwire/cli share \
--name jira \
--allow "jira_get" \
--redact-secrets \
-- npx -y @aashari/mcp-server-atlassian-jira@3.3.0
Exposes 1 default tools with pattern-based secret redaction.
Optionally set an expiry with --ttl 30m, prompt for approvals with --confirm, or limit calls with --max-calls 20.
Connect your teammate’s agent
MCPWire prints a unique wire://... ticket in your terminal. Send it privately to your teammate to paste into their MCP client:
Claude Desktop · Cursor · Windsurf config
{
"mcpServers": {
"jira": {
"command": "npx",
"args": [
"-y",
"@mcpwire/cli",
"join",
"wire://<TICKET_FROM_HOST>"
]
}
}
}
Replace <TICKET_FROM_HOST> with the active session ticket. The agent can only discover and call the tools exposed above.
Scoped tool permissions
MCPWire acts as a Layer 7 JSON-RPC firewall. Requests for blocked tools are dropped on the wire before ever touching your machine.
| Tool | Default Policy | Notes |
|---|---|---|
jira_get | Allowed | Reads any Jira REST endpoint the token can access, including issues, comments, and user data. Scope the API token to the projects you intend to share. |
jira_post | Blocked (High risk) | Creates issues, comments, and other resources. |
jira_put | Blocked (High risk) | Replaces issues, comments, and other resources. |
jira_patch | Blocked (High risk) | Partially updates issues and fields. |
jira_delete | Blocked (High risk) | Removes issues, comments, and attachments. |
Test and verify
Try these recommended prompts to confirm the agent receives expected outputs and that restricted actions fail safely.
Try Jira
Create an Atlassian API token, then set ATLASSIAN_SITE_NAME, ATLASSIAN_USER_EMAIL, and ATLASSIAN_API_TOKEN in the host environment. Use a token whose account only sees the projects you intend to share. This is a community server — Atlassian’s official MCP server is remote-only and not supported by this catalog.
Ask the agent to look up an issue with jira_get on a path like /rest/api/3/issue/PROJ-123, or to search with /rest/api/3/search/jql. Search results include issue fields your token can access. The write tools (jira_post, jira_put, jira_patch, jira_delete) stay outside the default allowlist because they act on your Jira data with your identity.
The generated command above contains the catalog’s explicit default allowlist. Check the guest’s tool list before making calls and use the server’s argument schema for required fields. See the CLI guide for guest configuration and session controls for approvals, redaction, and expiry.
--record session.wirelog to your host command. Drop the resulting file into the Session Replay Viewer to inspect timestamps, latency, blocked attempts, and secret scrubbing.