Linear MCP Server vs MCP Atlassian: both are productivity tools on Scriptiii AI Tools. Linear MCP Server pricing: Freemium. Free tier with paid upgrades. (reported by the maker) MCP Atlassian pricing: Free. Free to use. (reported by the maker) Both have 0 upvotes.
| Field | Linear MCP Server | MCP Atlassian |
|---|---|---|
| Page | Linear MCP Server | MCP Atlassian |
| Pricing (maker-reported) | Freemium. Free tier with paid upgrades. | Free. Free to use. |
| Upvotes | 0 | 0 |
| Best for | ai-agents, mcp-server, project-management | ai-agents, mcp-server, project-management |
| Tagline | Hosted remote MCP server for finding, creating and updating Linear issues and projects from AI clients. | Community MCP server for Atlassian Confluence and Jira, supporting Cloud and Server/Data Center. |
| Website | Visit Linear MCP Server | Visit MCP Atlassian |
Pricing and pricing details come from the maker's submission. They are not independently verified.
Linear's MCP server is a centrally hosted, authenticated remote server that lets any MCP-compatible AI client read and modify your Linear workspace. Instead of building a custom integration, you connect Claude, Cursor, VS Code, Codex, Windsurf, Zed or another client to https://mcp.linear.app/mcp and the model can find, create and update issues, projects and comments.
It follows the authenticated remote MCP specification and uses Streamable HTTP as the primary transport, with OAuth 2.1 and dynamic client registration for setup.
https://mcp.linear.app/mcp/readonly, or request only the read OAuth scope on the standard endpoint, so the token cannot reach write APIs.Authorization: Bearer header instead of the interactive flow; a read-only API key gives read-only access.npx mcp-remote.Linear documents several agent patterns: turning a planning document into a project with issues and milestones; turning standup notes into comments on the right issues; drafting an implementation plan and then creating the parent issue plus sub-issues; and triaging incoming bugs with consistent labels and owners.
https://mcp.linear.app/mcp./mcp/readonly or request the read scope.~/.mcp-auth if auth gets stuck.https://mcp.linear.app/sse is a deprecated fallback; use /mcp for new setups.--transport sse-only is documented.The MCP server is included with Linear workspaces; no separate MCP add-on is required. See linear.app/pricing for plan limits.
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
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.
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.
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.
Ask your AI assistant to:
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 |
| 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+) |
| 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.
Never share API tokens. Keep .env files secure. See SECURITY.md.
See CONTRIBUTING.md for development setup.
MIT - See LICENSE. Not an official Atlassian product.