MCP server for managing a Jirrabit instance (an alternative to Jira)
MCP server for managing a Jirrabit instance (an alternative to Jira)
active Production-safe Score 90/100 http no auth
At a glance
| Endpoint | https://jirrabit-mcp.ricardorobles.es/mcp |
|---|---|
| Source | https://github.com/rroblf01/jirrabit-mcp |
| Transport | http |
| Tools | 114 |
| Auth | none |
| First seen | 2026-09-30 02:40:12 |
| Last checked | 2026-11-17 22:03:47 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 742 / 1040 ms |
| Last successful check | 2026-11-17 22:03:47 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (114)
addJiraAttachment— Attach a file to an issue. `data` is the base64 of the file with no data: prefix, at most 5 MB of raw bytes, which is about 6.7 MB once encoaddJiraProjectMember— Add a person to a project with a role. Needs admin on the project. An existing member is updated rather than rejected, so this is safe to caddOrEditJiraIssueComment— Add a comment, or edit an existing one. Pass commentId to replace an existing comment's body; omit it to create a new comment.addOrEditJiraIssueWorklog— Log time on a work item, or edit an existing worklog. Pass worklogId to edit; omit it to log new time. An edit moves the issue's time totalarchiveJiraIssue— Archive an issue, or bring a archived one back. Archiving hides it from the project list, from search and from JQL, and keeps everything: cobulkUpdateJiraBoard— Apply one field change to several work items at once — a status, an assignee, a priority, a sprint, an epic, or adding or removing one labelclearJiraRecentIssues— Empty the caller's "Recientes" list. The issues themselves are untouched; only the record that they were opened is forgotten. Per person, socloneJiraIssue— Copy a work item: summary, description, type, priority, assignee, labels, epic, story points, estimate and due date. The reporter becomes thcloseJiraSprint— Close a sprint, in two steps. Closing is not a state flip: jirrabit moves every issue in the sprint that is not already done to carriesTo,createJiraAdminUser— Create a user account. Superuser only. Omit the password and jirrabit creates one that cannot be logged into, so the person has to reset itcreateJiraApiKey— Mint an API key for the caller. Superuser only. This is the only time the token exists as text: jirrabit stores a hash. If the answer is locreateJiraCustomField— Add a custom field to a project. Needs admin on the project. Types are text, textarea, number, select, date, user and checkbox. The slug iscreateJiraEpic— Create an epic in a project. Needs admin on the project. This is the only way to create an epic in jirrabit: an epic is its own entity, notcreateJiraInvite— Mint a registration invite. Superuser only. This is the only response that carries the token and the registration URL, and the only way tocreateJiraIssue— Create a new Jira work item. Pass comment for an opening comment and watch to follow it as the caller, so filing with context is one call increateJiraIssueLink— Create a link between two Jira work items. The link is directional: outwardIssueKey is the issue being acted on and inwardIssueKey is the otcreateJiraIssueTemplate— Create an issue template in a project. Needs admin on the project: it is project configuration, and a template is what every future issue ofcreateJiraIssueType— Create an issue type. Superuser only.createJiraPriority— Create a priority. Superuser only.createJiraProject— Create a project. The key is the prefix of every issue key in it, so it cannot be changed later without renaming the project's issues. ThecreateJiraSavedFilter— Save the current query under a name, so it can be recalled by listJiraSavedFilters instead of being retyped. The query must be jirrabit's JQcreateJiraSprint— Create a sprint in a project. It starts as `future`; moving issues into it is a separate step, by assigning them with editJiraIssue's sprintcreateJiraStatus— Create a status. Superuser only. Omit `order` to put it at the end of the board's columns; passing 0 would put it at the front and reorder acreateJiraTeam— Create a team, a broadcast list that is not a permission boundary. Any authenticated caller may read teams; creating one needs admin. The screateJiraWebhook— Create a webhook on a project. Needs admin on the project. jirrabit dispatches these to in-process handlers that mostly log; there is no oudeleteJiraBoardView— Delete one of the caller's saved board views, by id from listJiraBoardViews. The issues it matched are untouched — it is a name and a set ofdeleteJiraIssueType— Delete an issue type. Superuser only, and refused with a 409 while any issue uses it.deleteJiraPriority— Delete a priority. Superuser only, and refused with a 409 while any issue uses it.deleteJiraStatus— Delete a status. Superuser only, and refused with a 409 while any issue still uses it — jirrabit will not silently strip the status from eveeditJiraIssue— Edit an existing work item; only fields you pass are changed. To change status, use transitionJiraIssue — jirrabit enforces its workflow theexportJiraIssuesCsv— Export a project's issues as CSV rows, as data rather than as a file. Honours the same filters the issue list does, so "export what I am logetJiraAttachment— Fetch one attachment. The body carries a `dataUrl` — a data: URL holding the base64 contents — which is the same shape the web UI uses for agetJiraCommentHistory— The previous bodies of one comment, newest first. Incomplete by construction, and the tool says so: only two code paths in jirrabit write agetJiraCurrentUser— Details for the current Jira user, i.e. the owner of the API key in use.getJiraEpic— Read one epic, with its summary, colour and whether it is closed. listJiraEpics is usually enough; this is for one epic by id.getJiraIssue— Get a Jira work item by ID or key.getJiraIssueChangelog— What changed on one issue, field by field, newest first. Optional `field` narrows it to a single one, which is the honest way to ask "when dgetJiraIssueCustomFields— An issue's custom field values, keyed by slug. Empty object when none are set.getJiraIssueLinks— List the links on an issue, in both directions. Each link names the other end, so this is how you confirm a createJiraIssueLink landed or figetJiraIssueTimer— The caller's running timer on an issue, and how long it has been running. Errors when no timer is running on it.getJiraProject— Get one Jira space by key. Use it to read a project's description, rather than listing every project and picking from that.getJiraProjectActivity— A project's activity feed: creates, updates and deletes, with the actor and a timestamp. `verb` narrows it to one kind, e.g. 'deleted'. ThigetJiraProjectBurndown— A sprint's burndown in story points plus recent velocity: committed vs completed per closed sprint, and the ideal line against what actuallygetJiraProjectReports— Throughput per ISO week for the last eight weeks, cycle-time stats over issues resolved in the last ninety days, and a WIP-by-status snapshogetJiraProjectSla— Open issues stuck in one status longer than a threshold, oldest first. "Time at current status" is the newest status-change row, or the issugetJiraProjectWiki— A project's wiki page as Markdown. An empty body means it has never been written, which is a normal state rather than a missing page: jirrabgetJiraSprint— Get one sprint by numeric id, including its goal and dates.getJiraUser— Get one user by numeric id or username, with their display name and email. Use it to turn an assignee id into a name, or to confirm a usernaimportJiraIssuesCsv— Create issues in a project from CSV text. Needs edit rights on the project. It is two phases and the first one is the default. Without `drylinkJiraBranchToIssue— Link a branch or a commit to an issue, so the code and the work item point at each other. Idempotent on the issue, branch and commit togethelistJiraAdminUsers— List every user on the instance, with privilege flags. Superuser only. This is not the same as listJiraUsers, which any caller may use andlistJiraApiKeys— List the caller's own API keys: their names, prefixes, and when each was last used or revoked. The secret is never returned — only a prefixlistJiraBoardViews— List the caller's saved board views for a project: a name, the board filters it applies, whether it is the default, and the board URL it reolistJiraCommentMentions— Who was @mentioned in a comment, and whether they have since opened the issue. Use it to answer "did anyone see what I asked". Naming someblistJiraCommentReactions— The reactions on a comment, as counts per emoji, plus which of them are the caller's. Counts rather than a list of people: a reaction is a slistJiraCustomFields— A project's custom field definitions, with their slugs. The slug is the key an issue's values are stored under, so getJiraIssueCustomFieldslistJiraEpics— List the epics of a project. Call this to get the ids to pass as epicId, and to see which issues are grouped under which epic. Epics are notlistJiraInvites— List the instance's registration invites, with who made them, when they expire and whether they were used. Superuser only. The tokens are nlistJiraIssueAttachments— List the files attached to an issue, with their size and content type. The bytes are not in this response — getJiraAttachment fetches one —listJiraIssueBranchLinks— The branches and commits linked to an issue, newest first. Use it to see what code has already been written for a work item.
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 22:03:47 | ✓ | ✓ | 775 ms | 90 | active |
| 2026-11-17 21:48:42 | ✓ | ✓ | 772 ms | 90 | active |
| 2026-11-17 21:33:35 | ✓ | ✓ | 980 ms | 90 | active |
| 2026-11-17 21:18:24 | ✓ | ✓ | 708 ms | 90 | active |
| 2026-11-17 21:03:20 | ✓ | ✓ | 770 ms | 90 | active |
| 2026-11-17 20:48:01 | ✓ | ✓ | 916 ms | 90 | active |
| 2026-11-17 20:32:55 | ✓ | ✓ | 697 ms | 90 | active |
| 2026-11-17 20:17:51 | ✓ | ✓ | 837 ms | 90 | active |
| 2026-11-17 20:02:15 | ✓ | ✓ | 907 ms | 90 | active |
| 2026-11-17 19:46:53 | ✓ | ✓ | 791 ms | 90 | active |
| 2026-11-17 19:31:50 | ✓ | ✓ | 791 ms | 90 | active |
| 2026-11-17 19:16:41 | ✓ | ✓ | 551 ms | 90 | active |
| 2026-11-17 19:01:00 | ✓ | ✓ | 553 ms | 90 | active |
| 2026-11-17 18:45:58 | ✓ | ✓ | 1014 ms | 86 | active |
| 2026-11-17 18:30:56 | ✓ | ✓ | 838 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://jirrabit-mcp.ricardorobles.es/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/jirrabit-mcp-ricardorobles-es-mcp # JSON