Skip to content
Agentmart
Submit a tool

rewelo

Prioritise a backlog with the relative weight method: score, rank, simulate and plan tickets

Connector by sebs · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 2
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/sebs-rewelo

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Prioritise a backlog with the relative weight method: score, rank, simulate and plan tickets

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools
24 read · 5 write · 13 delete
Secrets
None asked for
Install scripts
None found
Runs as
Node.js package

Tools by what they do 42

Read from the source code; the running server may list different tools.

Read 24 · Look things up without changing anything.

  • calc_priority
  • calc_weights
  • event_log
  • explain_priority
  • export_csv
  • export_json
  • project_diff
  • project_history
  • project_list
  • relation_list
  • relation_list_all
  • report_dashboard
Show 12 more tools
  • report_distribution
  • report_group
  • report_health
  • report_summary
  • report_times
  • server_version
  • simulate
  • suggest_scores
  • tag_list
  • ticket_history
  • ticket_list
  • weight_get

Write 5 · Create, change, send or run things.

  • import_csv
  • project_create
  • relation_create
  • tag_create
  • ticket_create

Delete 13 · Delete, drop, revoke or wipe things.

  • apply_changes
  • import_json
  • project_delete
  • relation_remove
  • tag_assign
  • tag_delete
  • tag_remove
  • tag_rename
  • ticket_delete
  • ticket_update
  • ticket_upsert
  • weight_reset
Show 1 more tools
  • weight_set

Secrets and settings it asks for

Other settings (environment variables or headers).

  • RW_DB_PATH

Network hosts it talks to 2

  • github.com · found in code
  • sebs.github.io · found in code

Tools (42)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • apply_changescan change or delete data

    Apply a list of changes in one transaction: all of them or, when one fails, none. Operations: ticket_create, ticket_update, ticket_delete, tag_assign and tag_remove (tag as prefix:value; a missing tag is created), relation_create, relation_remove, each with the parameters of the tool of that name. With dryRun, nothing is written: the result shows what the changes would do. Returns each operation's outcome and how the ranking of the open tickets (not state:done, as simulate ranks) changes; a ticket the changes close or reopen is marked done or reopened. Use it to groom a backlog in one step, an…

  • calc_priorityread-only

    Calculate weighted priorities for all tickets, sorted descending. Inline w1-w4 override stored weights for this call only. Returns {title, priority, weighted} per ticket. For de-risk-first ordering, use ticket_list with sort='risk' instead.

  • calc_weightsread-only

    Calculate each ticket's relative share of total value and cost as fractions between 0 and 1 (0.25 = 25%). Shows how one ticket compares to the whole backlog, or to a tagged subset when tag is given.

  • event_logread-only

    Get a unified event stream combining ticket creates, updates, deletes, and tag changes. Without since/after: the newest events, newest first. With since or after: the events after it, oldest first. To poll incrementally without missing events, pass the sequence of the last event received as the next after.

  • explain_priorityread-only

    Explain one ticket's priority: the formula with its scores and the project's weights, its rank among the open tickets (not state:done) as calc_priority ranks, and what it would take to reach the top N: the priority to beat, and the smallest change of each single score that gets there.

  • export_csvread-only

    Export all tickets as CSV. Optionally includes calculated value, cost, and priority columns. Over 5 MB, returns a link to the resource with the CSV instead.

  • export_jsonread-only

    Export a project as JSON: tickets, tags, relations and weights; with withHistory also each ticket's createdAt, updatedAt, revisions and tagChanges, and the project's deleted tickets (deletions), so lead and cycle times and the event log survive a restore. Use for backups of a single project; import_json restores it. Over 5 MB, returns a link to the resource with the export instead.

  • import_csv

    Import tickets from CSV string. Only 'title' column is required; missing score columns default to 1. Tags column optional (comma-separated prefix:value). Columns other than title, description, benefit, penalty, estimate, risk, tags (and the calculated value, cost, priority) are rejected.

  • import_jsoncan change or delete data

    Import a project from JSON as export_json writes it: {tickets: [{title, description?, benefit?, penalty?, estimate?, risk?, tags?: [{prefix, value}], createdAt?, updatedAt?, revisions?, tagChanges?}], tags?, relations?: [{source, type, target}], weights?: {w1, w2, w3, w4}, deletions?: [{title, createdAt, deletedAt}]}. The history keys (createdAt, updatedAt, revisions, tagChanges, deletions) come from export_json with withHistory: pass them back as they are. Unknown keys are refused. Tags are created as needed and the project if it does not exist. Relations are added, and weights in the file re…

  • project_create

    Create a new project. Name must be unique; letters, digits, spaces, hyphens and underscores (not starting with a space), max 100 characters.

  • project_deletecan change or delete data

    Delete a project and all its tickets, tags, relations, and history. Irreversible. When the client supports forms (elicitation), the user is asked to confirm first, as rw project delete does.

  • project_diffread-only

    Compare project state against a point in time. Returns new tickets, title/description/score changes, deleted tickets, and tag changes since the timestamp.

  • project_historyread-only

    List revision history across all tickets in a project: newest first, or with since the revisions right after it, oldest first. Use instead of calling ticket_history per ticket. Page with limit and offset.

  • project_listread-only

    List all projects with their IDs and creation dates.

  • relation_create

    Create a bidirectional relation between two tickets. Types: blocks, depends-on, relates-to, duplicates, supersedes, precedes, tests, implements, addresses, splits-into, informs, see-also.

Show 27 more tools
  • relation_listread-only

    List relations for a single ticket. For all relations in a project, use relation_list_all instead.

  • relation_list_allread-only

    List every relation in a project in one call. Returns source/target IDs, titles, and relation type. Use instead of calling relation_list per ticket.

  • relation_removecan change or delete data

    Remove a relation between two tickets (removes both directions). Errors if the relation does not exist.

  • report_dashboardread-only

    Render a self-contained HTML dashboard (tickets, distribution, health, relations). Returns the HTML document as text, or, when it is over 5 MB, a link to the resource with it.

  • report_distributionread-only

    Count how many tickets use each Fibonacci score (1-21), per dimension (benefit, penalty, estimate, risk).

  • report_groupread-only

    Group tickets by the values of one tag prefix (e.g. team), with ticket count and average priority per value.

  • report_healthread-only

    Assess backlog health: high/low priority ratio, open ticket count, total cost. highToLowRatio is null when no open ticket is low priority, also when there are no open tickets.

  • report_summaryread-only

    Get project overview: total tickets, breakdown by state tag, and the top-N open (not state:done) tickets by priority. Good starting point for any project.

  • report_timesread-only

    Calculate lead time (created→done) and cycle time (wip→done) per ticket, plus their averages (whole days; null where there is no value). Prerequisite: assign state:wip and state:done tags to tickets.

  • server_versionread-only

    Return the server version string. Use to verify which build is running.

  • simulateread-only

    What-if: rank the open tickets (not state:done) as calc_priority does, under hypothetical score changes, new or removed tickets and weights, and compare with the current ranking. Nothing is written; use ticket_update to apply a scenario. Returns the scenario's top tickets and every ticket that is changed, added, removed or moves, with its rank and priority before and after.

  • suggest_scoresread-only

    Material to score a new ticket relative to the project's own backlog, before ticket_create: the most similar existing tickets (possible duplicates) with their scores; for each dimension and each score, the existing ticket closest to the new one as a reference; and the project's score distribution. With sample, and when the client supports MCP sampling, the client's model is also asked for scores, returned as suggestion.

  • tag_assigncan change or delete data

    Assign tags to tickets, creating tags that don't exist yet (marked tagCreated), as rw tag assign does. Supports batch: single or multiple tags × single or multiple tickets in one call. A ticket holds one value per prefix: assigning state:done replaces state:wip (reported as 'replaced'), and requesting two values of one prefix is an error.

  • tag_create

    Create a tag (prefix:value) without assigning it; tag_assign creates missing tags itself. Prefix and value must be lowercase alphanumeric/hyphens. Must be unique per project.

  • tag_deletecan change or delete data

    Delete a tag that no ticket holds (use tag_remove on its tickets first). Tickets' tag history is kept.

  • tag_listread-only

    List all tags defined in a project, sorted by prefix then value.

  • tag_removecan change or delete data

    Remove a tag assignment from a ticket. The tag itself is not deleted.

  • tag_renamecan change or delete data

    Rename a tag's value. All ticket assignments carry over. New value must not conflict with an existing tag under the same prefix.

  • ticket_create

    Create a new ticket with Fibonacci scores (1,2,3,5,8,13,21). Title must be unique per project. When the client supports forms (elicitation), the user is asked for omitted scores; otherwise, or when the user declines, they default to 1. Priority = (benefit + penalty) / (estimate + risk). Use ticket_upsert instead if the title may already exist.

  • ticket_deletecan change or delete data

    Delete a ticket and its relations, revisions, and tag assignments. Irreversible.

  • ticket_historyread-only

    Show revision history for a single ticket. Provide title or id. For project-wide history, use project_history instead.

  • ticket_listread-only

    List tickets with calculated value, cost, and priority. Supports tag filters (intersection), exclude-tags, title search, score thresholds, sort, and limit/offset pagination. Returns {total, offset, items[]}.

  • ticket_updatecan change or delete data

    Update a ticket's title, description, or scores. Only provided fields are changed. Identified by current title.

  • ticket_upsertcan change or delete data

    Create or update a ticket matched by exact title. Returns {ticket, action: 'created'|'updated'|'unchanged'}. Idempotent — safe to call repeatedly without duplicate errors.

  • weight_getread-only

    Get the weight configuration (w1-w4) for a project. Defaults are all 1.5 if not customized.

  • weight_resetcan change or delete data

    Reset weight configuration to defaults (all 1.5).

  • weight_setcan change or delete data

    Set weight configuration (w1-w4) for a project. Each weight is 0 or between 0.01 and 100. Only provided weights change; omitted ones keep their current value.

Signals

Stars
2
Forks
0
Open issues
0
Last commit
Sep 26, 2026 (1 month ago)
Last release
Sep 26, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name
io.github.sebs/rewelo
Version
0.7.3
Auth
No auth
Packages
npm rewelooci ghcr.io/sebs/rewelo:0.7.3
License
MIT
Repository
github.com/sebs/rewelo
Website
sebs.github.io/rewelo/
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
Official MCP Registrygithub-graphql
Cite this page

rewelo MCP server. Agent Mart. https://agentmart.dev/connectors/sebs-rewelo (last updated 2026-10-24)