2,500+ MCP servers ready to use
Vinkius

Jira Service Management (JSM) MCP Server for Google ADK 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools SDK

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Jira Service Management (JSM) as an MCP tool provider through the Vinkius and your ADK agents can call every tool with full schema introspection.

Vinkius supports streamable HTTP and SSE.

python
from google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
    StreamableHTTPConnectionParams,
)

# Your Vinkius token — get it at cloud.vinkius.com
mcp_tools = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    )
)

agent = Agent(
    model="gemini-2.5-pro",
    name="jira_service_management_jsm_agent",
    instruction=(
        "You help users interact with Jira Service Management (JSM) "
        "using 10 available tools."
    ),
    tools=[mcp_tools],
)
Jira Service Management (JSM)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Jira Service Management (JSM) MCP Server

Empower your AI agents with Jira Service Management's leading ITSM platform. This MCP server allows you to list service desks, retrieve customer requests, manage organizations and queues, and access knowledge base articles directly through the Jira JSM API. Ideal for automating IT support and service delivery workflows.

Google ADK natively supports Jira Service Management (JSM) as an MCP tool provider — declare the Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 10 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

The Jira Service Management (JSM) MCP Server exposes 10 tools through the Vinkius. Connect it to Google ADK in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Jira Service Management (JSM) to Google ADK via MCP

Follow these steps to integrate the Jira Service Management (JSM) MCP Server with Google ADK.

01

Install Google ADK

Run pip install google-adk

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Create the agent

Save the code above and integrate into your ADK workflow

04

Explore tools

The agent will discover 10 tools from Jira Service Management (JSM) via MCP

Why Use Google ADK with the Jira Service Management (JSM) MCP Server

Google ADK provides unique advantages when paired with Jira Service Management (JSM) through the Model Context Protocol.

01

Google ADK natively supports MCP tool servers — declare a tool provider and the framework handles discovery, validation, and execution

02

Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Jira Service Management (JSM)

03

Production-ready features like session management, evaluation, and deployment come built-in — not bolted on

04

Seamless integration with Google Cloud services means you can combine Jira Service Management (JSM) tools with BigQuery, Vertex AI, and Cloud Functions

Jira Service Management (JSM) + Google ADK Use Cases

Practical scenarios where Google ADK combined with the Jira Service Management (JSM) MCP Server delivers measurable value.

01

Enterprise data agents: ADK agents query Jira Service Management (JSM) and cross-reference results with internal databases for comprehensive analysis

02

Multi-modal workflows: combine Jira Service Management (JSM) tool responses with Gemini's vision and language capabilities in a single agent

03

Automated compliance checks: schedule ADK agents to query Jira Service Management (JSM) regularly and flag policy violations or configuration drift

04

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Jira Service Management (JSM)

Jira Service Management (JSM) MCP Tools for Google ADK (10)

These 10 tools become available when you connect Jira Service Management (JSM) to Google ADK via MCP:

01

get_info

Use for system health monitoring. Retrieves system information for the JSM instance

02

get_request

g., "SD-123") or ID. Returns full descriptions, participants, and custom field values. Use this for deep investigation of a specific customer inquiry. Retrieves details for a specific customer request

03

get_service_desk

Returns project information and branding details. Useful for understanding the configuration of a specific support portal. Retrieves details for a specific service desk

04

list_customers

Useful for identifying support recipients and their account details. Lists all customers for a specific service desk

05

list_knowledge_bases

Essential for identifying available documentation that might help resolve common customer issues. Lists all knowledge base articles for a specific service desk

06

list_organizations

Useful for understanding which business entities are being supported and grouping support data by customer. Lists all organizations in JSM

07

list_queues

g., "All Open", "Unassigned") defined for a service desk. Useful for understanding how tickets are triaged and identifying backlog counts. Lists all queues for a specific service desk

08

list_request_types

g., "IT Help", "Hardware Request") available in a portal. Useful for understanding the service catalog of a specific team. Lists all request types for a specific service desk

09

list_requests

Includes request keys, summaries, and current status. Essential for monitoring the support queue and identifying urgent issues. Lists all customer requests

10

list_service_desks

Returns project keys, names, and IDs. Use this to identify the service desk ID before querying requests or queues. Lists all service desks

Example Prompts for Jira Service Management (JSM) in Google ADK

Ready-to-use prompts you can give your Google ADK agent to start working with Jira Service Management (JSM) immediately.

01

"List all active service desks in JSM."

02

"Show me the latest customer requests."

03

"Check the queues for service desk ID '1'."

Troubleshooting Jira Service Management (JSM) MCP Server with Google ADK

Common issues when connecting Jira Service Management (JSM) to Google ADK through the Vinkius, and how to resolve them.

01

McpToolset not found

Update: pip install --upgrade google-adk

Jira Service Management (JSM) + Google ADK FAQ

Common questions about integrating Jira Service Management (JSM) MCP Server with Google ADK.

01

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.
02

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.
03

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.

Connect Jira Service Management (JSM) to Google ADK

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.