Skip to main content
Glama
dpesch

MantisBT MCP Server

by dpesch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Issue

create_issue

Create a new MantisBT issue with required summary, description, project, and category, returning its ID, status, priority, severity, and view URL.

Instructions

Create a new MantisBT issue. Returns the full created issue object including the assigned id, summary, status, priority, severity, category, reporter, created_at, and view_url.

Required fields: summary, description, project_id, category. All other fields are optional with sensible defaults (priority: "normal", severity: "minor").

Recommended workflow:

  1. Call get_project_categories to obtain a valid category name

  2. Optionally call get_project_versions to obtain version names

  3. Optionally call find_project_member to resolve the assignee's username

Both priority and severity accept canonical English names or localized labels from the connected MantisBT instance — call get_issue_enums to see all available values.

For the handler, prefer the username field (resolved server-side) over handler_id when working interactively.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handlerNoMantisBT login name of the assignee. The server resolves the name to a user ID from the project member list. Use find_project_member or get_project_users to look up valid login names.
summaryYesIssue summary/title (required)
versionNoAffected product version name. Use get_project_versions to list available version names for the project.
categoryYesCategory name (required). Use get_project_categories to list available categories for the project.
priorityNoPriority level. Canonical English names: none, low, normal, high, urgent, immediate. Default: "normal". Use get_issue_enums to see localized labels.normal
severityNoSeverity level. Canonical English names: feature, trivial, text, tweak, minor, major, crash, block. Default: "minor". Use get_issue_enums to see localized labels.minor
handler_idNoNumeric user ID of the assignee. Alternative to the handler field — use one or the other, not both.
project_idYesProject ID the issue belongs to — use list_projects to discover project IDs
view_stateNoVisibility of the issue: "public" (visible to all, default) or "private" (restricted to higher-access users).
descriptionYesDetailed issue description (required). Do not create issues without a description. Plain text or Markdown.
custom_fieldsNoCustom field values: [{field: {id|name}, value: "<string>"}]. Use get_issue_fields or get_metadata to discover available custom fields per project.
target_versionNoTarget fix version — version in which the issue is planned to be resolved. Use get_project_versions to list available version names.
reproducibilityNoHow reliably the issue reproduces. Canonical English names: always, sometimes, random, have not tried, unable to reproduce, N/A. Use get_issue_enums to see localized labels.
fixed_in_versionNoVersion in which the issue was fixed. Use get_project_versions to list available version names.
steps_to_reproduceNoStep-by-step instructions to reproduce the issue. Plain text or Markdown.
additional_informationNoAdditional context or notes about the issue. Plain text or Markdown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.14.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / custom_fields / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / custom_fields / items / properties / field / additionalProperties
      Removed value: -false
    • changedInput schema / properties / custom_fields / items / required
      Previous value: -[
-  "field"
-]New value: +[
+  "field",
+  "value"
+]
    • addedInput schema / properties / handler_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / project_id / maximum
      Added value: +9007199254740991
  2. Changed1 schema field changedv1.10.5
    • addedInput schema / properties / custom_fields
      Added value: +{
+  "description": "Custom field values: [{field: {id|name}, value: \"<string>\"}]. Use get_issue_fields or get_metadata to discover available custom fields per project.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "field": {
+        "additionalProperties": false,
+        "description": "Custom field reference: { id } or { name }",
+        "properties": {
+          "id": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "value": {
+        "description": "Field value as string",
+        "type": "string"
+      }
+    },
+    "required": [
+      "field"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  3. Addedv1.10.4
  4. Removed
  5. Changed15 schema fields changedv1.10.3
    • changedInput schema / properties / additional_information / description
      Previous value: -"Additional information about the issue. Plain text or Markdown."New value: +"Additional context or notes about the issue. Plain text or Markdown."
    • changedInput schema / properties / category / description
      Previous value: -"Category name (use get_project_categories to list available categories)"New value: +"Category name (required). Use get_project_categories to list available categories for the project."
    • changedInput schema / properties / description / description
      Previous value: -"Detailed issue description. Required — do not create issues without a description. Plain text or Markdown."New value: +"Detailed issue description (required). Do not create issues without a description. Plain text or Markdown."
    • changedInput schema / properties / fixed_in_version / description
      Previous value: -"Version name in which the issue was fixed (use get_project_versions to list available versions)"New value: +"Version in which the issue was fixed. Use get_project_versions to list available version names."
    • changedInput schema / properties / handler / description
      Previous value: -"Username (login name) of the person to assign the issue to. Alternative to handler_id — the server resolves the name to a user ID from the project members. Use get_project_users to see available users."New value: +"MantisBT login name of the assignee. The server resolves the name to a user ID from the project member list. Use find_project_member or get_project_users to look up valid login names."
    • changedInput schema / properties / handler_id / description
      Previous value: -"User ID of the person to assign the issue to"New value: +"Numeric user ID of the assignee. Alternative to the handler field — use one or the other, not both."
    • changedInput schema / properties / priority / description
      Previous value: -"Priority: canonical English name (none, low, normal, high, urgent, immediate) or localized label. Default: \"normal\". Use get_issue_enums to see all available values."New value: +"Priority level. Canonical English names: none, low, normal, high, urgent, immediate. Default: \"normal\". Use get_issue_enums to see localized labels."
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID the issue belongs to"New value: +"Project ID the issue belongs to — use list_projects to discover project IDs"
    • changedInput schema / properties / reproducibility / description
      Previous value: -"Reproducibility: canonical English name or localized label (always, sometimes, random, have not tried, unable to reproduce, N/A). Use get_issue_enums to see all available values."New value: +"How reliably the issue reproduces. Canonical English names: always, sometimes, random, have not tried, unable to reproduce, N/A. Use get_issue_enums to see localized labels."
    • changedInput schema / properties / severity / description
      Previous value: -"Severity: canonical English name (feature, trivial, text, tweak, minor, major, crash, block) or localized label. Default: \"minor\". Use get_issue_enums to see all available values."New value: +"Severity level. Canonical English names: feature, trivial, text, tweak, minor, major, crash, block. Default: \"minor\". Use get_issue_enums to see localized labels."
    • changedInput schema / properties / steps_to_reproduce / description
      Previous value: -"Steps to reproduce the issue. Plain text or Markdown."New value: +"Step-by-step instructions to reproduce the issue. Plain text or Markdown."
    • changedInput schema / properties / summary / description
      Previous value: -"Issue summary/title"New value: +"Issue summary/title (required)"
    • changedInput schema / properties / target_version / description
      Previous value: -"Target version name — version in which the issue is planned to be fixed (use get_project_versions to list available versions)"New value: +"Target fix version — version in which the issue is planned to be resolved. Use get_project_versions to list available version names."
    • changedInput schema / properties / version / description
      Previous value: -"Affected product version name (use get_project_versions to list available versions)"New value: +"Affected product version name. Use get_project_versions to list available version names for the project."
    • changedInput schema / properties / view_state / description
      Previous value: -"Visibility of the issue: \"public\" (default) or \"private\""New value: +"Visibility of the issue: \"public\" (visible to all, default) or \"private\" (restricted to higher-access users)."
  6. Changed3 schema fields changedv1.5.15
    • changedInput schema / properties / priority / description
      Previous value: -"Priority name — must be a canonical English name: none, low, normal, high, urgent, immediate. Default: \"normal\". Call get_issue_enums to see localized labels."New value: +"Priority: canonical English name (none, low, normal, high, urgent, immediate) or localized label. Default: \"normal\". Use get_issue_enums to see all available values."
    • changedInput schema / properties / reproducibility / description
      Previous value: -"Reproducibility — must be a canonical English name: always, sometimes, random, have not tried, unable to reproduce, N/A. Call get_issue_enums to see localized labels."New value: +"Reproducibility: canonical English name or localized label (always, sometimes, random, have not tried, unable to reproduce, N/A). Use get_issue_enums to see all available values."
    • changedInput schema / properties / severity / description
      Previous value: -"Severity name — must be a canonical English name: feature, trivial, text, tweak, minor, major, crash, block. Default: \"minor\". Call get_issue_enums to see localized labels."New value: +"Severity: canonical English name (feature, trivial, text, tweak, minor, major, crash, block) or localized label. Default: \"minor\". Use get_issue_enums to see all available values."
  7. Changed7 schema fields changedv1.5.14
    • addedInput schema / properties / additional_information
      Added value: +{
+  "description": "Additional information about the issue. Plain text or Markdown.",
+  "type": "string"
+}
    • addedInput schema / properties / fixed_in_version
      Added value: +{
+  "description": "Version name in which the issue was fixed (use get_project_versions to list available versions)",
+  "type": "string"
+}
    • addedInput schema / properties / reproducibility
      Added value: +{
+  "description": "Reproducibility — must be a canonical English name: always, sometimes, random, have not tried, unable to reproduce, N/A. Call get_issue_enums to see localized labels.",
+  "type": "string"
+}
    • addedInput schema / properties / steps_to_reproduce
      Added value: +{
+  "description": "Steps to reproduce the issue. Plain text or Markdown.",
+  "type": "string"
+}
    • addedInput schema / properties / target_version
      Added value: +{
+  "description": "Target version name — version in which the issue is planned to be fixed (use get_project_versions to list available versions)",
+  "type": "string"
+}
    • addedInput schema / properties / version
      Added value: +{
+  "description": "Affected product version name (use get_project_versions to list available versions)",
+  "type": "string"
+}
    • addedInput schema / properties / view_state
      Added value: +{
+  "description": "Visibility of the issue: \"public\" (default) or \"private\"",
+  "enum": [
+    "public",
+    "private"
+  ],
+  "type": "string"
+}
  8. Changed6 schema fields changedv1.5.13
    • removedInput schema / properties / description / default
      Removed value: -""
    • changedInput schema / properties / description / description
      Previous value: -"Detailed issue description"New value: +"Detailed issue description. Required — do not create issues without a description. Plain text or Markdown."
    • addedInput schema / properties / description / minLength
      Added value: +1
    • addedInput schema / properties / priority / default
      Added value: +"normal"
    • changedInput schema / properties / priority / description
      Previous value: -"Priority name — must be a canonical English name: none, low, normal, high, urgent, immediate. Call get_issue_enums to see localized labels."New value: +"Priority name — must be a canonical English name: none, low, normal, high, urgent, immediate. Default: \"normal\". Call get_issue_enums to see localized labels."
    • changedInput schema / required
      Previous value: -[
-  "summary",
-  "project_id",
-  "category"
-]New value: +[
+  "summary",
+  "description",
+  "project_id",
+  "category"
+]
  9. Changed2 schema fields changedv1.5.9
    • changedInput schema / properties / priority / description
      Previous value: -"Priority name (e.g. \"normal\", \"high\", \"urgent\", \"immediate\", \"low\", \"none\")"New value: +"Priority name — must be a canonical English name: none, low, normal, high, urgent, immediate. Call get_issue_enums to see localized labels."
    • changedInput schema / properties / severity / description
      Previous value: -"Severity name (e.g. \"minor\", \"major\", \"crash\", \"block\", \"feature\", \"trivial\", \"text\") — default: \"minor\""New value: +"Severity name — must be a canonical English name: feature, trivial, text, tweak, minor, major, crash, block. Default: \"minor\". Call get_issue_enums to see localized labels."
  10. First observedv1.5.6

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare the write semantics (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the description only needs to add context, which it does: required vs optional fields, defaults for priority/severity, and the server-side resolution of handler. It stops short of describing failure modes (e.g. invalid category or duplicate issues), so not a full 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose and return shape, then organizes the workflow as a short numbered list and the field rules as compressed sentences. Slightly long overall, but no sentence is filler given the 16-parameter surface.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter creation tool with no output schema, the description covers the essentials: required fields, defaults, return payload contents, dependency tools for resolving foreign keys, and assignee field preference. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline would be 3; the description adds real value by noting that priority/severity accept canonical English names or localized labels and by steering the agent to prefer handler over handler_id. It does not add syntax beyond the schema for the remaining fields, so it is good but not exhaustive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a new MantisBT issue') and immediately enumerates what the returned object contains, distinguishing it clearly from read/update/delete siblings like get_issue, update_issue, and delete_issue.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit numbered workflow (resolve category via get_project_categories, versions via get_project_versions, assignee via find_project_member) and a concrete preference rule for handler vs handler_id when working interactively. Also names get_issue_enums for localized enum values.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools