mcp server spec builder

I have generated the complete MCP server specification for your Jira integration. This spec includes standardized tool naming, cursor-based pagination for searches, and a robust error handling framework.

MCP Server Specification: jira-mcp-server

1. Overview

• Description: MCP server for interacting with Jira Cloud APIs to manage issues and comments.
• Protocol Version: 2025-03-26
• Transport: stdio (default)
• Capabilities: tools, resources

2. Shared Definitions

{
  "Pagination": {
    "type": "object",
    "properties": {
      "next_cursor": { "type": ["string", "null"] }
    }
  },
  "Error": {
    "type": "object",
    "properties": {
      "code": { "type": "string" },
      "message": { "type": "string" },
      "retryable": { "type": "boolean" }
    }
  }
}

3. Tools

Tool: create_issue

• Description: Creates a new issue in a specific project.
• Input Schema:

{
  "$id": "create_issue",
  "type": "object",
  "properties": {
    "project_key": { "type": "string" },
    "summary": { "type": "string" },
    "description": { "type": "string" },
    "issue_type": { "type": "string", "default": "Task" },
    "idempotency_key": { "type": "string" }
  },
  "required": ["project_key", "summary"],
  "additionalProperties": false
}

• Structured Errors: invalid_params, unauthorized, conflict

Tool: search_issues

• Description: Search for issues using JQL.
• Input Schema:

{
  "$id": "search_issues",
  "type": "object",
  "properties": {
    "jql": { "type": "string" },
    "limit": { "type": "integer", "minimum": 1, "maximum": 500, "default": 50 },
    "cursor": { "type": "string" }
  },
  "required": ["jql"],
  "additionalProperties": false
}

4. Resources

• Resource: user_dashboard
• URI Template: jira://current-user/dashboard
• Mime Type: application/json

5. Assumptions & Decisions Log

• Rule 1: Defaulted search limit to 50 items.
• Rule 9: Applied cursor-based pagination for search_issues.
• Decision: Assumed Bearer Token via X-API-Key for auth.

Next steps

1. Review the $id fields in the JSON schemas to ensure they match your internal registry.
2. Verify the project_key validation regex matches your Jira instance constraints.
3. Pass this spec to an implementation agent to generate the TypeScript or Python server code.