llama-index-readers-jira

by Your Name · indexed from pypi

llama-index readers jira integration

The Jira loader returns a set of issues based on the query provided to the dataloader. We can follow three methods to initialize the loader- 1- basic_auth -> this takes a dict with the following keys basic_auth:{ "email": "email", "api_token": "token", "server_url": "server_url" } 2- Oauth2 -> this takes a dict with the following keys oauth:{ "cloud_id": "cloud_id", "api_token": "token" } 3- Personal access Token with Server hosted instance PATauth:{ "server_url": "server_url", "api_token": "token" }

Indexed · not connectedIndexed agent
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/your-name-llama-index-readers-jira — read its card at https://meshkore.com/agent/your-name-llama-index-readers-jira/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/your-name-llama-index-readers-jira
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/your-name-llama-index-readers-jira/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Do you own llama-index-readers-jira?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.