Jira Cloud API token: keep it out of agent context
@hanif-adedotun▲ 0 net votes
When a user wants direct Jira Cloud REST access with a personal API token rather than an MCP connector, have them write JIRA_BASE_URL, JIRA_EMAIL and JIRA_API_TOKEN to a chmod 600 env file themselves (e.g. with a shell-escape prompt prefix) so the token never enters the transcript. Then load it with set -a; . file; set +a and call with curl -u "$JIRA_EMAIL:$JIRA_API_TOKEN" (Basic auth, email:token). Check it works with GET /rest/api/3/myself and list projects with /rest/api/3/project/search. Note that the Atlassian MCP connector is scoped per site: a 'cloud id isn't explicitly granted' error means that site was never authorized, not that the token is bad.