Jira Assets (BYOK)

Jira Assets (BYOK) — connector documentation

• MCP endpoint: https://byok-jira-assets.connectorbay.com/mcp
• REST API: POST https://byok-jira-assets.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-jira-assets.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Jira Assets Atlassian account email, sent in the X-Upstream-Key header and the Atlassian API token in X-Upstream-Key-2 of every request (never stored, logged or cached)
• Health: https://byok-jira-assets.connectorbay.com/health · Tool schemas: https://byok-jira-assets.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-jira-assets · agent@connectorbay.com

What Jira Assets (BYOK) is for

Jira Assets (BYOK) lets an AI assistant read your own Jira Assets data through the Jira Assets API with a key you supply (Atlassian account email). Read-only: 12 tools (list_object_schemas, get_object_schema, list_object_types, list_object_type_attributes, search_objects, count_objects, get_object, get_object_history, list_object_connected_tickets, list_status_types, list_reference_types, get_assets_usage). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.atlassian.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Jira Assets. Jira Assets and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which Assets schemas do we have in Jira?"
• "Show Assets schema 1"
• "Which asset types are in Assets schema 1?"
• "Which attributes does Assets object type 5 have?"
• "Which laptops are in our Jira Assets?"
• "How many active laptops are in Jira Assets?"

What it does

• list_object_schemas: List Assets object schemas (asset catalogues) with key, name, status, object and object type counts. Paging uses startAt and maxResults.
• get_object_schema: Get one Assets object schema: key, name, description, status and counts.
• list_object_types: List the object types of a schema (Laptop, Licence, Office ...) with id, name, description, object count and parent type.
• list_object_type_attributes: List the attributes (fields) defined on an object type: name, kind of value, whether it is the label, and description.
• search_objects: Find Assets objects with an AQL query such as 'objectType = Laptop AND Status = Active'; returns key, label, type and times (attribute values are left out unless asked).
• count_objects: Count the Assets objects matching an AQL query without returning them.
• get_object: Get one Assets object: key, label, type, creation and update time.
• get_object_history: List the change history of an Assets object: which attribute changed, old and new value, when and by whom.
• list_object_connected_tickets: List the Jira issues linked to an Assets object with key, title, status, type, priority and reporter.
• list_status_types: List the Assets status types (Active, Retired ...) with category; optionally for one schema.
• list_reference_types: List the Assets reference types (kinds of links between objects such as Installed, Owned) with color; optionally for one schema.
• get_assets_usage: Get the total number of Assets objects on the site and the count per schema.

BYOK key

You bring your own Jira Assets Atlassian account email (https://id.atlassian.com/manage-profile/security/api-tokens). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.atlassian.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://developer.atlassian.com/cloud/assets/rest/intro/ (the API this connector calls, with a BYOK key)

Live from the Jira Assets API (api.atlassian.com) with a BYOK key; documentation: https://developer.atlassian.com/cloud/assets/rest/intro/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Jira Assets. Jira Assets and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Jira Assets account.

Built for: Worldwide. Languages: English.

Jira Assets (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Jira Assets (BYOK) is. Jira Assets (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Jira Assets data: Read Jira Service Management Assets: object schemas, object types and attributes, objects found with AQL, history and linked tickets with your Atlassian email and API token. You bring your own Jira Assets Atlassian account email; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Jira Assets call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.atlassian.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Jira Assets rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Jira Assets receives. The request we make on your behalf, including the key and the arguments, under Jira Assets's own terms and privacy policy. Jira Assets acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Jira Assets gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Jira Assets data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Jira Assets (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Jira Assets at any time to end all access.

Children. Jira Assets (BYOK) is a general-audience service operated by the adult using the assistant, under Jira Assets's own age rules.

Changes. We will post changes here with a new effective date.

Jira Assets (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Jira Assets (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Jira Assets (BYOK) provides: Read Jira Service Management Assets: object schemas, object types and attributes, objects found with AQL, history and linked tickets with your Atlassian email and API token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Jira Assets credentials and only access data you are allowed to access. Jira Assets's terms apply to your use of Jira Assets; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Jira Assets. Jira Assets and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Jira Assets returns, lightly trimmed; it may be incomplete, delayed or changed by Jira Assets. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Jira Assets account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Jira Assets's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Jira Assets may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Jira Assets key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Jira Assets takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-jira-assets

Jira Assets (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-jira-assets.connectorbay.com/mcp
• REST API: https://byok-jira-assets.connectorbay.com/openapi.json
• Live status: https://byok-jira-assets.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Jira Assets (BYOK) never asks for them.