
MCP Atlassian (Jira and Confluence)
Jira issues and Confluence pages, Cloud or self-hosted.
- Started in our test
- ★ 6.1K GitHub stars
- 215.9K downloads a week
- Last commit 19 Sept 2026
What is MCP Atlassian (Jira and Confluence)?
MCP Atlassian (mcp-atlassian) is an open source MCP server that lets AI assistants search, create and update Jira issues and Confluence pages, on Atlassian Cloud or Server and Data Center.
- Tools
- 98
- Runs on
- Your computer
- Licence
- MIT
- GitHub stars
- 6.1K
Good for
- Turning a conversation into well-formed Jira tickets
- Summarising a sprint or an epic
- Finding the Confluence page that answers a question
You'll need
- uv (for uvx)
- An Atlassian API token (Cloud) or personal access token (Server/Data Center)
Started in our testWe ran this exact config on 26 Oct 2026: it started and answered with 98 tools. The npm package called "mcp-atlassian" comes from a different repository (Vijay-Duke/mcp-atlassian). This project is a Python package of the same name, so it runs with uvx.
MCP Shelf take
We started MCP Atlassian (Jira and Confluence) on our own test machine on 26 Oct 2026 and it answered with 98 tools. 58 of the 98 only read; the other 40 can change things. Every tool comes with a useful description, all of them say whether they change things, and the tool list costs about 7,800 tokens of context before you ask a thing. Other directories point at a package with the same name that belongs to someone else; the config on this page installs the real one. It is the most-starred of the 16 servers in its category on our shelf (6.1K stars, with 215.9K downloads a week).
What can MCP Atlassian (Jira and Confluence) read and change?
It can read
- Every Jira project and Confluence space your account can open, including attachments and history
It can change
- Creates, edits, moves and deletes issues, pages, comments, sprints and attachments
- Can change page restrictions
Safer setup: Set READ_ONLY_MODE=true until you trust it, and narrow it with ENABLED_TOOLS and the project and space filters.
MCP Atlassian (Jira and Confluence) in more detail
mcp-atlassian is the most used community server for Atlassian tools. It searches and updates Jira issues with JQL, manages sprints and transitions, and reads and writes Confluence pages, for both Cloud and Server/Data Center.
You can set it to read-only, and you can limit which Confluence spaces and Jira projects it sees.
- Made by
- sooperset and community contributors (not Atlassian)
- Latest version
- 0.23.1 (19 Aug 2026)
- PyPI package
- mcp-atlassian
- Downloads
- 215.9K a week
- Last commit
- 19 Sept 2026
- Setup checked
- 27 Oct 2026
- Page updated
- 27 Oct 2026
What's in the pod
What tools does MCP Atlassian (Jira and Confluence) have?
We found 98 tools when we started it on 26 Oct 2026. 58 only read. The rest can change things, so keep your app's "ask before each tool call" setting on for them.
Show all 98 tools
Changes things40 tools · Can create, edit, send or delete.
| Tool | What it is for |
|---|---|
confluence_add_comment | Comments on a page. |
confluence_add_inline_comment | Pins a comment to a piece of text. |
confluence_add_label | Adds a label. |
confluence_copy_page | Copies a page to a new place. |
confluence_create_page | Creates a page, from Markdown or storage format. |
confluence_create_page_from_template | Creates a page from a template (Cloud). |
confluence_delete_attachment | Deletes an attachment for good. |
confluence_delete_page | Deletes a page. |
confluence_move_page | Moves a page to a new parent or space. |
confluence_reply_to_comment | Replies in a comment thread. |
confluence_set_page_restrictions | Changes who can view or edit a page. |
confluence_update_page | Replaces a page's content. |
confluence_update_page_section | Rewrites one section of a page and leaves the rest alone. |
confluence_upload_attachment | Attaches a file to a page. |
confluence_upload_attachments | Attaches several files at once. |
jira_add_comment | Comments on an issue. |
jira_add_issues_to_sprint | Pulls issues into a sprint. |
jira_add_watcher | Adds someone as a watcher. |
jira_add_worklog | Logs time against an issue. |
jira_assign_issue | Assigns an issue to someone. |
jira_batch_create_issues | Opens many issues in one call, with a dry-run option. |
jira_batch_create_versions | Creates several fix versions at once. |
jira_create_customer_request | Raises a Jira Service Management request. |
jira_create_issue | Opens a new issue, sub-task or epic child. |
jira_create_issue_link | Links two issues, for example "blocks". |
jira_create_remote_issue_link | Adds a web or Confluence link to an issue. |
jira_create_sprint | Creates a sprint on a board. |
jira_create_version | Creates a fix version. |
jira_delete_issue | Deletes an issue. |
jira_edit_comment | Edits an existing comment. |
jira_link_to_epic | Puts an issue under an epic. |
jira_move_issue | Moves an issue to another project (Cloud only). |
jira_move_issues_to_backlog | Sends issues back to the backlog. |
jira_remove_issue_link | Removes a link between issues. |
jira_remove_watcher | Removes a watcher. |
jira_transition_issue | Moves an issue to a new status. |
jira_update_issue | Edits an issue's fields. |
jira_update_proforma_form_answers | Fills in answers on an issue's form. |
jira_update_sprint | Renames, starts, closes or re-dates a sprint. |
jira_update_version | Edits or releases a fix version. |
Only reads58 tools · Looks things up and changes nothing.
| Tool | What it is for |
|---|---|
confluence_check_content_permissions | Checks whether a person or group may do something with a page. |
confluence_download_attachment | Fetches one attachment. |
confluence_download_content_attachments | Fetches every attachment on a page. |
confluence_get_attachments | Lists a page's attachments. |
confluence_get_comments | Reads a page's comments. |
confluence_get_inline_comments | Reads comments pinned to text on a page. |
confluence_get_labels | Reads a page's labels. |
confluence_get_page | Reads a page by id, or by title and space. |
confluence_get_page_children | Lists the pages under a page. |
confluence_get_page_diff | Shows what changed between two versions. |
confluence_get_page_history | Reads an older version of a page. |
confluence_get_page_images | Fetches a page's images so the assistant can look at them. |
confluence_get_page_restrictions | Shows who can view or edit a page. |
confluence_get_page_template | Reads one template's body (Cloud). |
confluence_get_page_views | Reads view counts for a page (Cloud only). |
confluence_get_space_page_tree | Lists a whole space's page tree. |
confluence_get_space_permissions | Lists who has which rights in a space. |
confluence_list_page_templates | Lists page templates (Cloud). |
confluence_search | Finds pages by words or a CQL query. |
confluence_search_user | Finds Confluence users. |
jira_batch_get_changelogs | Reads the change history of many issues (Cloud only). |
jira_download_attachments | Fetches an issue's attachments. |
jira_get_agile_boards | Finds Scrum and Kanban boards. |
jira_get_all_projects | Lists every project you can see. |
jira_get_board_issues | Lists the issues on a board, with an optional JQL filter. |
jira_get_create_fields | Lists the fields needed to create a given issue type. |
jira_get_cross_project_dependencies | Finds links from a project's issues into other projects. |
jira_get_field_options | Lists the allowed values of a custom field. |
jira_get_issue | Reads one issue with its fields, epic and links. |
jira_get_issue_dates | Reads an issue's key dates and status history. |
jira_get_issue_development_info | Shows branches, commits and pull requests linked to an issue. |
jira_get_issue_images | Fetches an issue's image attachments so the assistant can look at them. |
jira_get_issue_proforma_forms | Lists the forms attached to an issue. |
jira_get_issue_sla | Works out cycle time and other SLA figures for an issue. |
jira_get_issue_watchers | Lists who watches an issue. |
jira_get_issues_development_info | The same for many issues at once. |
jira_get_link_types | Lists link types such as blocks or duplicates. |
jira_get_proforma_form_details | Reads one form's questions and answers. |
jira_get_project_components | Lists a project's components. |
jira_get_project_epic_hierarchy | Groups a project's epics under their parents across projects. |
jira_get_project_fields | Lists the fields used across a project's issue types. |
jira_get_project_issue_types | Lists the issue types a project allows. |
jira_get_project_issues | Lists the issues in a project. |
jira_get_project_versions | Lists a project's fix versions. |
jira_get_queue_issues | Lists the requests in a queue (Server and Data Center). |
jira_get_request_type_fields | Lists the fields a request type asks for. |
jira_get_request_types | Lists the request types of a service desk. |
jira_get_service_desk_for_project | Finds the service desk behind a project (Server and Data Center). |
jira_get_service_desk_queues | Lists a service desk's queues (Server and Data Center). |
jira_get_sprint_issues | Lists the issues in a sprint. |
jira_get_sprints_from_board | Lists a board's sprints by state. |
jira_get_transitions | Shows which statuses an issue can move to next. |
jira_get_user_profile | Looks up one Jira user. |
jira_get_worklog | Reads time logged on an issue. |
jira_search | Finds issues with a JQL query. |
jira_search_assignable_users | Finds people who can be assigned in a project or issue. |
jira_search_fields | Finds field names and ids by keyword, handy for custom fields. |
jira_search_projects | Finds projects by name or key. |
Grouped and described by us. The README on GitHub lists the inputs each tool takes.
How clearly it describes its tools to your assistant
- Tools with a description
- 98 of 98
- Say if they change things
- 98 of 98
- Context it takes, at least
- ~7,800 tokens
Every tool says whether it only reads or can change things, so a client can ask before the risky ones. The tool list is large: switch off the tools you do not use if your client allows it.
From the tool list it sent us. The token figure counts names, descriptions and input names; the full schemas your client loads add more.
How do I install MCP Atlassian (Jira and Confluence)?
Install steps from the MCP Atlassian (Jira and Confluence) README
The project's own instructions, copied from its README on GitHub on 27 Oct 2026 under its MIT licence. They are the source of truth; the ready-made configs further down are built from them. The rest of the README is in the README tab.
Quick Start
1. Get Your API Token
Go to https://id.atlassian.com/manage-profile/security/api-tokens and create a token.
For Server/Data Center, use a Personal Access Token instead. See Authentication.
2. Configure Your IDE
Add to your Claude Desktop or Cursor MCP configuration:
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": ["mcp-atlassian"],
"env": {
"JIRA_URL": "https://your-company.atlassian.net",
"JIRA_USERNAME": "your.email@company.com",
"JIRA_API_TOKEN": "your_api_token",
"CONFLUENCE_URL": "https://your-company.atlassian.net/wiki",
"CONFLUENCE_USERNAME": "your.email@company.com",
"CONFLUENCE_API_TOKEN": "your_api_token"
}
}
}
}
Server/Data Center users: Use
JIRA_PERSONAL_TOKENinstead ofJIRA_USERNAME+JIRA_API_TOKEN. See Authentication for details.
Autohand Code
Use the same uvx server with your Atlassian credentials:
autohand mcp add mcp-atlassian env \
JIRA_URL=https://your-company.atlassian.net \
JIRA_USERNAME=your.email@company.com \
JIRA_API_TOKEN=your_api_token \
CONFLUENCE_URL=https://your-company.atlassian.net/wiki \
CONFLUENCE_USERNAME=your.email@company.com \
CONFLUENCE_API_TOKEN=your_api_token \
uvx mcp-atlassian
Add --scope project after add to keep the configuration in the current
project. See Autohand Code for current
installation and CLI details.
3. Start Using
Ask your AI assistant to:
- "Find issues assigned to me in PROJ project"
- "Search Confluence for onboarding docs"
- "Create a bug ticket for the login issue"
- "Update the status of PROJ-123 to Done"
What you need first
- uv (for uvx)
- An Atlassian API token (Cloud) or personal access token (Server/Data Center)
Add MCP Atlassian (Jira and Confluence) to your app
Pick your app for a ready-to-paste snippet and where it goes, built from the steps above.
Where it goes: Your terminal, in the project folder
claude mcp add atlassian -e JIRA_URL=https://your-company.atlassian.net -e JIRA_USERNAME=you@company.com -e JIRA_API_TOKEN=your-token -e CONFLUENCE_URL=https://your-company.atlassian.net/wiki -e CONFLUENCE_USERNAME=you@company.com -e CONFLUENCE_API_TOKEN=your-token -- uvx mcp-atlassianFor Server or Data Center, swap JIRA_USERNAME and JIRA_API_TOKEN for JIRA_PERSONAL_TOKEN (and the same for Confluence). Leave out the Confluence variables to load only the Jira tools.
Where it goes: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
"mcpServers": {
"atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian"
],
"env": {
"JIRA_URL": "https://your-company.atlassian.net",
"JIRA_USERNAME": "you@company.com",
"JIRA_API_TOKEN": "your-token",
"CONFLUENCE_URL": "https://your-company.atlassian.net/wiki",
"CONFLUENCE_USERNAME": "you@company.com",
"CONFLUENCE_API_TOKEN": "your-token"
}
}
}
}Where it goes: claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian"
],
"env": {
"JIRA_URL": "https://your-company.atlassian.net",
"JIRA_USERNAME": "you@company.com",
"JIRA_API_TOKEN": "your-token",
"CONFLUENCE_URL": "https://your-company.atlassian.net/wiki",
"CONFLUENCE_USERNAME": "you@company.com",
"CONFLUENCE_API_TOKEN": "your-token"
}
}
}
}Where it goes: .vscode/mcp.json in your project
{
"servers": {
"atlassian": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-atlassian"
],
"env": {
"JIRA_URL": "https://your-company.atlassian.net",
"JIRA_USERNAME": "you@company.com",
"JIRA_API_TOKEN": "your-token",
"CONFLUENCE_URL": "https://your-company.atlassian.net/wiki",
"CONFLUENCE_USERNAME": "you@company.com",
"CONFLUENCE_API_TOKEN": "your-token"
}
}
}
}Where it goes: ~/.codex/config.toml, shared by the Codex CLI, IDE extension and ChatGPT desktop app
[mcp_servers.atlassian]
command = "uvx"
args = ["mcp-atlassian"]
[mcp_servers.atlassian.env]
JIRA_URL = "https://your-company.atlassian.net"
JIRA_USERNAME = "you@company.com"
JIRA_API_TOKEN = "your-token"
CONFLUENCE_URL = "https://your-company.atlassian.net/wiki"
CONFLUENCE_USERNAME = "you@company.com"
CONFLUENCE_API_TOKEN = "your-token"Or run: codex mcp add atlassian --env JIRA_URL=https://your-company.atlassian.net --env JIRA_USERNAME=you@company.com --env JIRA_API_TOKEN=your-token --env CONFLUENCE_URL=https://your-company.atlassian.net/wiki --env CONFLUENCE_USERNAME=you@company.com --env CONFLUENCE_API_TOKEN=your-token -- uvx mcp-atlassian
Where it goes: ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian"
],
"env": {
"JIRA_URL": "https://your-company.atlassian.net",
"JIRA_USERNAME": "you@company.com",
"JIRA_API_TOKEN": "your-token",
"CONFLUENCE_URL": "https://your-company.atlassian.net/wiki",
"CONFLUENCE_USERNAME": "you@company.com",
"CONFLUENCE_API_TOKEN": "your-token"
}
}
}
}Where it goes: Not supported
Not supported as a local server. The project can run over streamable HTTP for remote use, but ChatGPT cannot send the Atlassian token, so Atlassian's own hosted Rovo server is the better route for ChatGPT on Cloud.
Add "READ_ONLY_MODE": "true" to env while you try it out.
Checked against the project's own install docs on 27 Oct 2026: sooperset/mcp-atlassian README, mcp-atlassian.soomiles.com/docs/authentication.
Did this work for you?
Projects change their install steps often. If MCP Atlassian (Jira and Confluence) did not install, or something here no longer matches the project, tell us and we will check it against the README and fix the page.
New to this? See the setup guides for Claude Code, Cursor, Claude Desktop, VS Code, Codex and ChatGPT. If it will not start, test it in MCP Inspector and look up the error in Fixing MCP server errors.
MCP Atlassian (Jira and Confluence) not working? Common fixes
- 401 Unauthorized on Atlassian Cloud
- Use your account email as the username and an API token, not your password. Check the URL has no trailing path for Jira and ends in /wiki for Confluence.
- 401 on Jira Server or Data Center
- Use JIRA_PERSONAL_TOKEN (and CONFLUENCE_PERSONAL_TOKEN) instead of username and API token.
- SSL certificate errors on a self-hosted instance
- Set JIRA_SSL_VERIFY=false and CONFLUENCE_SSL_VERIFY=false only if you trust the network, or add your company's certificate authority to the machine.
- The assistant ignores the right tool among almost 100
- Set ENABLED_TOOLS to the dozen you actually use.
How do I configure MCP Atlassian (Jira and Confluence)?
Names are exactly as the project spells them. Required ones are marked.
| Setting | What it does |
|---|---|
JIRA_URLEnvironment variable · required | Your Jira address. Leave out the Jira variables to use Confluence only.https://your-company.atlassian.net |
JIRA_USERNAME + JIRA_API_TOKENEnvironment variable · required | For Atlassian Cloud: your account email and an API token from id.atlassian.com.you@company.com / ATATT3x... |
JIRA_PERSONAL_TOKENEnvironment variable | For Jira Server or Data Center: a personal access token instead of email plus API token.NjM0... |
CONFLUENCE_URLEnvironment variable | Your Confluence address, with /wiki on Cloud. Leave out to use Jira only.https://your-company.atlassian.net/wiki |
CONFLUENCE_USERNAME + CONFLUENCE_API_TOKENEnvironment variable | Confluence credentials, the same kind as Jira's. On Server and Data Center use CONFLUENCE_PERSONAL_TOKEN.you@company.com / ATATT3x... |
READ_ONLY_MODEEnvironment variable | Turns off every tool that creates, edits or deletes.true |
ENABLED_TOOLSEnvironment variable | Offers only the tools you list, which also keeps the prompt small.jira_search,jira_get_issue,confluence_search |
JIRA_PROJECTS_FILTER / CONFLUENCE_SPACES_FILTEREnvironment variable | Limits searches to the projects or spaces you list.PROJ,DEV |
MCP Atlassian (Jira and Confluence) FAQ
How do I add MCP Atlassian to Claude Code?
Run claude mcp add mcp-atlassian with -e flags for JIRA_URL, JIRA_USERNAME and JIRA_API_TOKEN (and the Confluence equivalents if you want them), then -- uvx mcp-atlassian. You need uv installed first.
How do I connect Jira to Cursor with MCP Atlassian?
Add an mcpServers entry to ~/.cursor/mcp.json that runs uvx mcp-atlassian, with JIRA_URL, your email and an API token in env. Create the token at id.atlassian.com under Security, API tokens.
Is MCP Atlassian made by Atlassian?
No. It is an open source project by sooperset and contributors, MIT licensed. Atlassian runs its own hosted Rovo MCP server for Cloud; mcp-atlassian is the choice for Server and Data Center or when you want to run it yourself.
Does MCP Atlassian work with Jira Server and Data Center?
Yes. Use a personal access token in JIRA_PERSONAL_TOKEN instead of a username and API token. A few tools are Cloud only, and the service desk queue tools are Server and Data Center only.
Is MCP Atlassian safe to use on our Jira?
It acts with your token's permissions, so it can change what you can change. Set READ_ONLY_MODE=true to block every write, and use ENABLED_TOOLS plus the project and space filters to narrow what it sees.
Is MCP Atlassian free?
Yes. The server is MIT licensed and runs on your machine. It uses the Jira and Confluence APIs that come with your existing Atlassian licence.
Why does MCP Atlassian return 401 Unauthorized?
On Cloud, check JIRA_USERNAME is your Atlassian email and the token is an API token, not your password. On Server or Data Center, use JIRA_PERSONAL_TOKEN instead of the username and token pair.
Can I use MCP Atlassian with only Jira or only Confluence?
Yes. Set only the variables for the product you want. The other product's tools are left out, which also shortens the tool list the assistant has to choose from.
MCP Atlassian (Jira and Confluence) README
This is the project's own README from sooperset/mcp-atlassian, written by sooperset and community contributors (not Atlassian), and shared under its MIT licence. We copied it on 27 Oct 2026, so the version on GitHub may be newer.
MCP Atlassian
Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Supports both Cloud and Server/Data Center deployments.
https://github.com/user-attachments/assets/35303504-14c6-4ae4-913b-7c25ea511c3e
Quick Start
1. Get Your API Token
Go to https://id.atlassian.com/manage-profile/security/api-tokens and create a token.
For Server/Data Center, use a Personal Access Token instead. See Authentication.
2. Configure Your IDE
Add to your Claude Desktop or Cursor MCP configuration:
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": ["mcp-atlassian"],
"env": {
"JIRA_URL": "https://your-company.atlassian.net",
"JIRA_USERNAME": "your.email@company.com",
"JIRA_API_TOKEN": "your_api_token",
"CONFLUENCE_URL": "https://your-company.atlassian.net/wiki",
"CONFLUENCE_USERNAME": "your.email@company.com",
"CONFLUENCE_API_TOKEN": "your_api_token"
}
}
}
}
Server/Data Center users: Use
JIRA_PERSONAL_TOKENinstead ofJIRA_USERNAME+JIRA_API_TOKEN. See Authentication for details.
Autohand Code
Use the same uvx server with your Atlassian credentials:
autohand mcp add mcp-atlassian env \
JIRA_URL=https://your-company.atlassian.net \
JIRA_USERNAME=your.email@company.com \
JIRA_API_TOKEN=your_api_token \
CONFLUENCE_URL=https://your-company.atlassian.net/wiki \
CONFLUENCE_USERNAME=your.email@company.com \
CONFLUENCE_API_TOKEN=your_api_token \
uvx mcp-atlassian
Add --scope project after add to keep the configuration in the current
project. See Autohand Code for current
installation and CLI details.
3. Start Using
Ask your AI assistant to:
- "Find issues assigned to me in PROJ project"
- "Search Confluence for onboarding docs"
- "Create a bug ticket for the login issue"
- "Update the status of PROJ-123 to Done"
Documentation
Full documentation is available at mcp-atlassian.soomiles.com.
Documentation is also available in llms.txt format, which LLMs can consume easily:
llms.txt— documentation sitemapllms-full.txt— complete documentation
| Topic | Description |
|---|---|
| Installation | uvx, Docker, pip, from source |
| Authentication | API tokens, PAT, OAuth 2.0 |
| Configuration | IDE setup, environment variables |
| HTTP Transport | SSE, streamable-http, multi-user |
| Tools Reference | All Jira & Confluence tools |
| Troubleshooting | Common issues & debugging |
Compatibility
| Product | Deployment | Support |
|---|---|---|
| Confluence | Cloud | Fully supported |
| Confluence | Server/Data Center | Supported (v6.0+) |
| Jira | Cloud | Fully supported |
| Jira | Server/Data Center | Supported (v8.14+) |
Key Tools
| Jira | Confluence |
|---|---|
jira_search - Search with JQL |
confluence_search - Search with CQL |
jira_get_issue - Get issue details |
confluence_get_page - Get page content |
jira_create_issue - Create issues |
confluence_create_page - Create pages |
jira_update_issue - Update issues |
confluence_update_page - Update pages |
jira_transition_issue - Change status |
confluence_add_comment - Add comments |
98 tools total — See Tools Reference for the complete list.
Security
Never share API tokens. Keep .env files secure. See SECURITY.md.
Contributing
See CONTRIBUTING.md for development setup.
License
MIT - See LICENSE. Not an official Atlassian product.
Two peas, one chat
Chat with AI about MCP Atlassian (Jira and Confluence)
Opens a chat primed with MCP Atlassian (Jira and Confluence)’s README and setup docs from this page, or add it in Cursor to use its tools.
The Cursor button opens Cursor and asks before it adds the server. Fill in any keys it needs in Cursor’s MCP settings.
Peas in a pod
What are the alternatives to MCP Atlassian (Jira and Confluence)?
How MCP Atlassian (Jira and Confluence) lines up against its neighbours on the shelf. See every knowledge and work apps server.

MCP Atlassian (Jira and Confluence)This pea
Jira issues and Confluence pages, Cloud or self-hosted.
- Tools
- 98
- Runs on
- Your computer
- Licence
- MIT
- Stars
- 6.1K

Long-term memory as plain Markdown files you own.
- Tools
- 27
- Runs on
- Your computer
- Licence
- AGPL-3.0-or-later
- Stars
- 4.4K

Read LinkedIn profiles, companies and job posts with your own login.
- Tools
- 20
- Runs on
- Your computer
- Licence
- Apache-2.0
- Stars
- 4K

Search arXiv, download papers and read them in full.
- Tools
- 19
- Runs on
- Your computer
- Licence
- Apache-2.0
- Stars
- 3.2K

Prices, indicators, screeners and backtests for stocks, crypto and forex, no account needed.
- Tools
- 37
- Runs on
- Your computer or hosted
- Licence
- MIT
- Stars
- 5.2K

Search, read and edit the notes in your Obsidian vault.
- Tools
- 15
- Runs on
- Your computer
- Licence
- MIT
- Stars
- 4.5K
Something wrong on this page? Tell us.
For bots & AI agents
Machine-readable versions of MCP Atlassian (Jira and Confluence) and MCP Shelf. Fetch these instead of parsing this page.
This listing (.md)llms.txtllms-full.txtai.txtFull catalog (.md)API specMCP serverMCP manifestDeveloper docs