MCPMarket
Vender SkillsPower Your AgentsConectar
  1. Inicio
  2. Servidores
  3. Atlassian

Atlassian

gregoryevezardbygregoryevezard
•
Herramientas para Desarrolladores
Productividad y Flujo de Trabajo
Herramientas de Colaboración

Integrates Confluence Cloud and Jira Cloud functionalities through a .NET Model Context Protocol (MCP) server.

Related MCPs

View more
  • neondatabase-labs

    Neon

    Enables natural language interaction with the Neon Management API and databases through the Model Context Protocol.

  • GLips

    Figma Context

    Provides AI coding agents with simplified Figma layout information via the Model Context Protocol.

  • 21st-dev

    Magic

    Generate modern UI components instantly from natural language descriptions within your IDE.

Related Skills

View all
  • openclaw

    Diagram Maker & Visualizer

    Generates professional SVG, HTML, and Excalidraw diagrams for software architecture, system flows, and educational concepts.

  • openclaw

    GH Issues Auto-Fixer

    Automates the end-to-end GitHub issue lifecycle by spawning sub-agents to implement code fixes, open pull requests, and resolve review comments.

  • openclaw

    Discord Integration

    Manages Discord operations including messaging, reactions, and channel management directly through Claude.

MCPMarket

Descubre servidores MCP que conectan clientes MCP como Claude y Cursor con tus herramientas favoritas. Explora MCP Market para empezar.

Explorar

  • Búsqueda MCP
  • Servidores MCP
  • Clientes MCP
  • Habilidades de Claude
  • MCP Market Hub
  • Categorías
  • ¿Qué es un servidor MCP?
  • Model Context Protocol

Clasificaciones

  • Top MCPs de Hoy
  • Top Habilidades de Claude de Hoy
  • Top 100 Habilidades de Claude
  • Top 100 Servidores MCP

Acerca de

  • Noticias
  • Enviar
  • Contacto

© 2026 MCP Market. Todos los derechos reservados.·Privacy·Terms

This .NET Model Context Protocol (MCP) server provides a standardized interface for seamless programmatic interaction with Atlassian Confluence Cloud (REST v2) and Jira Cloud (REST v3). It simplifies building applications or extensions by offering features like scoped API token authentication, automatic cloudId resolution, and a comprehensive set of tools to manage Confluence spaces and pages, as well as Jira projects and issues. It is designed to be easily integrated into development environments, such as through VS Code's Codex extension.

Características Principales

01Supports Scoped API Token + Basic Auth for secure access
02Automatic cloudId resolution for Atlassian Cloud sites
03Uses standard input/output (stdio) for MCP transport
040 GitHub stars
05Offers a wide array of exposed tools for Confluence (e.g., upsert page) and Jira (e.g., create issue)
06Provides Confluence REST v2 and Jira REST v3 integration

Casos de Uso

01Automating the creation, updating, and management of Confluence pages and spaces programmatically.
02Programmatically creating, querying, and managing Jira issues and projects within custom applications.
03Integrating Atlassian Cloud data and functionalities into external development tools or workflows.

Atlassian MCP Server (.NET)

.NET MCP server (transport stdio) for Confluence Cloud (REST v2) and Jira Cloud (REST v3).

Features

  • Scoped API Token + Basic Auth (email:token)
  • Automatic cloudId resolution via https://<site>/_edge/tenant_info
  • Confluence REST v2 via Atlassian gateway
  • Jira REST v3 via Atlassian gateway

Prerequisites

  • .NET SDK 10.0+
  • An Atlassian Cloud site (e.g. https://example.atlassian.net)
  • An API token with appropriate scopes for Confluence and/or Jira

Configuration (appsettings.json)

Copy the example and fill in your values:

cp src/Atlassian.McpServer/appsettings.exemple.json src/Atlassian.McpServer/appsettings.json

Example:

{
  "Atlassian": {
    "Site": "https://example.atlassian.net",
    "Email": "you@company.com",
    "ApiTokenConfluence": "your_confluence_token_scoped",
    "ApiTokenJira": "your_jira_token_scoped"
  }
}

Notes:

  • Never commit appsettings.json (use .gitignore).
  • If you only use one product (Confluence/Jira), leave the other token empty.

Build & Run

dotnet restore src/Atlassian.McpServer/Atlassian.McpServer.csproj
dotnet build   src/Atlassian.McpServer/Atlassian.McpServer.csproj -c Release
dotnet run     --project src/Atlassian.McpServer/Atlassian.McpServer.csproj -c Release

The MCP process listens on stdin/stdout.

Codex / VS Code Integration (DLL)

In Codex config.toml, add an MCP server pointing to the Release DLL:

[mcp_servers.atlassian]
command = "dotnet"
args = [
  "/path/to/repo/tools/atlassian-mcpserver/src/Atlassian.McpServer/bin/Release/net10.0/Atlassian.McpServer.dll"
]

Then restart VS Code (or the Codex extension) to reload the config.

Exposed Tools

Confluence

  • confluence_list_spaces(keys?, limit)
  • confluence_get_space_homepage_id(space_key)
  • confluence_get_space_info(space_key)
  • confluence_get_folder(folder_id, include_children)
  • confluence_get_page(page_id, include_children)
  • confluence_root_folders(space_key)
  • confluence_upsert_page(space_key, parent_id?, page_id?, title, body_storage_html, status?, version_message?, subtype?)
    • Recommended Jira reference: insert a Jira macro in body_storage_html: 
      <ac:structured-macro ac:name="jira">
  <ac:parameter ac:name="key">KEY</ac:parameter>
</ac:structured-macro>

Jira

  • jira_list_projects(query?, start_at, max_results, order_by?)
  • jira_get_project(project_id_or_key)
  • jira_get_issue(issue_id_or_key, fields_csv?, expand_csv?)
  • jira_search_jql(jql, max_results, next_page_token?)
  • jira_create_issue(project_key, issue_type, summary, description?, labels_csv?, parent_issue?)
  • jira_delete_issue(issue_id_or_key, delete_subtasks)

Exposed Resources

  • confluence://spaces
  • confluence://page/{pageId}
  • confluence://folder/{folderId}
  • confluence://root-folders/{spaceKey}
  • jira://projects
  • jira://project/{projectIdOrKey}
  • jira://issue/{issueIdOrKey}
  • jira://issue/createmeta/{projectKey}
  • jira://issue/editmeta/{issueIdOrKey}

Notes

  • Logs are sent to stderr to avoid polluting the JSON-RPC stream.
  • The server uses ModelContextProtocol (C#). If needed: 
    dotnet add package ModelContextProtocol --prerelease