JSM Assets

You can run the JSM Assets MCP Server to give Claude assistants access to Jira Service Management Assets data through a robust, paginated API. This server exposes a set of tools for searching, inspecting, and traversing asset data, with reliable multi-page retrieval and clear behavior for both single-page and multi-page queries.

How to use

You use this MCP server by running it locally (stdio) or via your MCP client’s integration flow. Start the server, then configure your client to connect through the provided runtime command. Once running, you can perform asset queries such as searching assets with AQL, exploring object schemas and types, inspecting attributes, and finding child objects. The server’s robust pagination ensures you retrieve complete results even when the underlying API signals partial data.

How to install

Prerequisites: ensure you have Node.js installed (recommended version aligned with the project you’re pulling). You will also need an MCP-enabled client to connect to the server. Follow the concrete steps below to get started.

# Quick setup (traditional, from source)
git clone <repo-url> && cd jsm-assets-mcp
npm install
npm run build
cp .env.example .env  # Edit with your credentials

Configuration and runtime commands

To run the MCP server locally and connect via a client, you will use a stdio-based runtime. The example below shows how to run the server with Node and pass the required environment variables.

{
  "mcpServers": {
    "jsm_assets": {
      "command": "node",
      "args": ["/path/to/jsm-assets-mcp/dist/index.js"],
      "env": {
        "JSM_WORKSPACE_ID": "your-workspace-id",
        "JSM_AUTH_TOKEN": "Basic your-encoded-token",
        "JSM_BASE_URL": "https://api.atlassian.com/jsm/assets/workspace"
      }
    }
  }
}

Claude Code integration (CLI)

You can also add the MCP server to Claude Code so Claude can access JSM Assets data directly from the CLI.

claude mcp add jsm_assets \
  -e JSM_WORKSPACE_ID="your-workspace-id" \
  -e JSM_AUTH_TOKEN="Basic your-token" \
  -- node /path/to/jsm-assets-mcp/dist/index.js

Environment and runtime considerations

Create a dedicated environment file to store credentials securely and reference it when starting the server. The following environment variables are required for authentication and API access:

JSM_WORKSPACE_ID=your-workspace-id
JSM_AUTH_TOKEN=Basic your-encoded-token
JSM_BASE_URL=https://api.atlassian.com/jsm/assets/workspace

Available tools

search_assets_aql

Search assets using Assets Query Language (AQL) with robust automatic pagination. Supports multi-page retrieval and optional page size control.

get_object_schemas

List all object schemas available in the workspace.

get_object_types

Retrieve object types for a specific schema by schemaId.

get_object_attributes

Fetch attributes for a specific object type by objectTypeId.

search_child_objects

Find child objects of a given parent type with automatic pagination and optional filters.