Issue Creation With Custom Field Mapping

Search, create, and manage Jira issues and sprints via MCP.

Unique: Implements client-side field validation and type coercion before API submission using a pre-loaded field registry, reducing failed requests and enabling AI agents to work with custom fields by name rather than opaque field IDs. Automatic format adaptation between Cloud and Server/Data Center field representations.

vs others: Faster iteration than manual Jira UI because validation happens before API call, and field discovery is cached rather than queried per-request. More robust than raw REST clients because it validates custom field types and coerces values to expected formats.

via “issue creation with field validation and custom field mapping”

** A modular and extensible MCP server designed to interact with Jira Cloud, providing tools to query boards, issues, and user data — ideal for integrating Jira with AI agents, bots, or automation systems

Unique: Implements pre-flight schema validation and custom field ID mapping as part of the MCP tool, reducing caller burden of field ID lookup and validation; modular design allows custom field mappings to be configured per project

vs others: Safer than raw REST API calls because it validates fields before submission; more flexible than simple issue templates because it supports custom field mapping and dynamic field population

via “task and revision creation with field mapping”

** - Interacting with Phabricator API

Unique: Implements field mapping layer that translates generic task/revision input (title, description, assignee) into Phabricator's custom field schema, handling type coercion and validation. Exposes creation as MCP tools so agents can trigger task generation without understanding Phabricator's internal field structure.

vs others: Abstracts Phabricator's complex custom field system from agent logic, whereas direct Conduit API calls require agents to know exact field keys and types for each Phabricator instance.

via “custom-field-mapping”