confluence_get_pageLABSCO SUMMARY
Read-only across Jira and Confluence, and it takes URLs exactly as people send them.
The by-URL tools are the practical difference: paste the link a colleague dropped in chat and the server resolves it, rather than making you dig the page ID or issue key out of it first. Nothing here creates or edits, so the token can be scoped read-only and the worst a mistaken call does is fetch something.
What it is
A read-only server across two Atlassian products: Jira issues and projects, Confluence pages and spaces. Every tool fetches; none of them write.
What you get
- A Jira issue by key, such as PROJ-123
- A Jira issue from a pasted URL, including board URLs that carry the issue in a query parameter
- Jira issues matching a JQL query
- The Jira projects your token can see
- A Confluence page by ID
- A Confluence page from a pasted URL, in the spaces, display and viewpage.action forms
- Confluence pages matching a search
- The Confluence spaces your token can see
Requirements
ATLASSIAN_DOMAIN and ATLASSIAN_EMAIL, plus API tokens — ATLASSIAN_CONFLUENCE_TOKEN and ATLASSIAN_JIRA_TOKEN separately, or a single combined token with access to both. Read-only scopes are enough: read:content:confluence and read:content-details:confluence on the Confluence side.
Setup effort
Build from source — get the source, then follow the project's own run instructions
USE CASES
01
Getting the context on a ticket someone just linked you
Hand the server the Jira URL as it was sent and read the issue back, board links included.
02
Answering a question from a spec that lives in Confluence
Search the pages for the topic, then pull the page that matches and read it in the conversation.
03
Pulling everything open on a project
List the projects to get the key right, then run the JQL that filters to what you want.
04
Summarising a page from the URL a colleague pasted
Resolve the wiki URL directly — the spaces, display and viewpage.action forms all work.
05
Finding where in the wiki a topic is documented
List the spaces you can see, then search pages within them for the term.
06
Checking the details on a ticket by its key
Fetch PROJ-123 straight by key when you already know which issue you mean.
8 tools
Listed in project docs. Your client may show a different list.
confluence_get_page_by_urlconfluence_search_pagesconfluence_list_spacesjira_get_issuejira_get_issue_by_urljira_search_issuesjira_list_projectsBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
- python on PATH
- ATLASSIAN_CONFLUENCE_TOKEN in your environment
- ATLASSIAN_JIRA_TOKEN in your environment
- ATLASSIAN_DOMAIN in your environment
- ATLASSIAN_EMAIL in your environment
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
Configuration file
JSON
{
"mcpServers": {
"atlassian": {
"command": "python",
"args": [
"-m",
"atlassian_mcp.server"
],
"cwd": "<YOUR_PATH_TO_ATLASSIAN_MCP>",
"env": {
"ATLASSIAN_DOMAIN": "<YOUR_COMPANY>.atlassian.net",
"ATLASSIAN_EMAIL": "<YOUR_ATLASSIAN_EMAIL>",
"ATLASSIAN_CONFLUENCE_TOKEN": "<YOUR_ATLASSIAN_CONFLUENCE_TOKEN>",
"ATLASSIAN_JIRA_TOKEN": "<YOUR_ATLASSIAN_JIRA_TOKEN>"
}
}
}
}python
TERMINAL
python -m atlassian_mcp.server
