Cesure

Write, edit, transpose and play guitar tabs and staff notation in Cesure.

Should I use this

Quality & Safety

A
Description quality
99%
Schema completeness
98%
Naming quality
94%
Poisoning risk
60%
Permission match
100%
Protocol compliance
100%

Findings (3)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool description contains URL to non-standard domainin create_score
  • MEDIUMTool description contains URL to non-standard domainin edit_measures

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~4,616Tokens (tool definitions)
~1.1 KBTypical response size
Significant attention impact (3.61% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "cesure": {
      "url": "https://api.cesure.app/mcp"
    }
  }
}

Remote endpoints

https://api.cesure.app/mcpstreamable-http

What it can do

Tool inventory

Tools (14)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟡create_score(score)

Create a score you write as a .cesure and open it as a draft, e.g. {"version":2,"score":{"title":"Song","tempo":96,"tracks":[{"name":"Guitar","instrument":"GUITAR","measures":[{"staves":[{"voices":["(0.6 2.5 2.4).2 r.2"]}]}]},{"name":"Bass","instrument":"BASS","tuning":[{"note":"G","octave":2},{"note":"D","octave":2},{"note":"A","octave":1},{"note":"E","octave":1}],"measures":[{"staves":[{"voices":["0.4.2 r.2"]}]}]}]}} (a track without tuning is a guitar in standard tuning; tuning lists the open strings from string 1). Every measure must read and fill its time signature, or nothing is created and the refusal names each fault with its place. Measure notation (.cesure): each voice is one string of beats separated by spaces. beat = content.duration[{d | tu 3}]; content = fret.string[{note props}] | pitch | (note note …) | r. Durations, on EVERY beat: 1 whole, 2 half, 4 quarter, 8, 16, 32, 64. Strings from 1 (the highest); x as fret mutes. A pitch (C4 = middle C, F#3, Bb2) lets Cesure choose string and fret; a staff is all by pitch or all fret.string. Beat props: d dotted, tu 3 triplet on each beat of the group. Note props: t tie, h hammer/pull-off and sl slide to the next note on that string, v vibrato, b (0 4) a whole-tone bend. EACH VOICE FILLS ITS TIME SIGNATURE EXACTLY: 4/4 = 4 quarters = 8 eighths, 3/4 = 3 quarters, 6/8 = 6 eighths; rests complete a short one. A measure without numerator/denominator is 4/4, whatever came before. A second voice (a bass under a melody) is a second string in voices. Examples (4/4): "5.3.4 7.3.4 r.2" (fret 5 then 7 on string 3 (strings from 1, the highest), quarters; a half rest); "(0.1 1.2 0.3).2 x.6.4 r.4" (a chord, a half; a muted note); "E4.8 F#4.8 G4.4 Bb3.2" (notes by pitch (C4 = middle C): Cesure chooses string and fret); "5.3.4{d} 5.3.8 2.1.8{tu 3} 3.1.8{tu 3} 5.1.8{tu 3} 7.2{h}.8 8.2.8" (dotted quarter; a triplet of eighths (each beat carries it); a hammer-on to the next note); "5.3.2 5.3{t}.4 7.2{sl}.8 9.2{v}.8" (a tie to the note before, a slide, a vibrato). A measure: {"id":"p2","numerator":3,"denominator":4,"staves":[{"voices":["0.1.8 2.1.8 3.1.4 5.1.4","0.6.2{d}"]}]}. The full format: https://cesure.app/format

Input Schema

{
  "type": "object",
  "properties": {
    "score": {
      "type": "string",
      "description": "The score, a .cesure written in the notation described above."
    }
  },
  "required": [
    "score"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {}
}
⚪import_score(score)

Open as a draft a score the person gives whole: a .cesure file's text, AlphaTex, or an "Open in Cesure" link. The score is taken as it is, never rewritten.

Input Schema

{
  "type": "object",
  "properties": {
    "score": {
      "type": "string",
      "description": "The .cesure text, AlphaTex, or Open in Cesure link, verbatim."
    }
  },
  "required": [
    "score"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {}
}
🟢read_score(draft, track, from, to)

Read measures from..to of a track of the draft (all by default, 200 at most a call: past them, the answer's more says where to go on) as .cesure measures — id, time signature, voices in the compact notation (second voice, hands, ties included) — with the repeat signs and tempo changes of those measures, by id, a summary of the score and one of the track.

Input Schema

{
  "type": "object",
  "properties": {
    "draft": {
      "type": "string",
      "description": "The draft: the id a previous tool gave (draft)."
    },
    "track": {
      "type": "integer",
      "description": "The track, from 1 (default 1).",
      "minimum": 1
    },
    "from": {
      "type": "integer",
      "description": "First measure, from 1 (default 1).",
      "minimum": 1
    },
    "to": {
      "type": "integer",
      "description": "Last measure (default the last; at most 200 are read a call).",
      "minimum": 1
    }
  },
  "required": [
    "draft"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {}
}
🔴edit_measures(draft, track, from, to, measures)

Rewrite measures from..to (numbers, inclusive) of ONE track of the draft with .cesure measures, as read_score returns them; to = from - 1 inserts before from. A measure written with its id stays that measure, even rewritten; one written without its id is a new measure, and the one it stood for is removed with what it carried (a repeat it opened, say). A measure of the range left out is removed, and measures [] removes the whole range. Unlike the format's own advice (a range of ids, every track rewritten), the other tracks follow column by column, as in the editor: a column is inserted, removed or given a time signature on every track; its repeat signs are carried as the editor carries them, and a tempo change stays on its column (on the next one when its column is removed), so no other column changes tempo. A note may be written by its pitch (E4, Bb3) in place of fret.string: Cesure chooses its string and fret, and never moves a note written with its string. The answer names the measures written. Every measure you write must read and fill its time signature, or nothing is written and the refusal names each fault with its place; one handed back as it is (id and content) is not judged. Measure notation (.cesure): each voice is one string of beats separated by spaces. beat = content.duration[{d | tu 3}]; content = fret.string[{note props}] | pitch | (note note …) | r. Durations, on EVERY beat: 1 whole, 2 half, 4 quarter, 8, 16, 32, 64. Strings from 1 (the highest); x as fret mutes. A pitch (C4 = middle C, F#3, Bb2) lets Cesure choose string and fret; a staff is all by pitch or all fret.string. Beat props: d dotted, tu 3 triplet on each beat of the group. Note props: t tie, h hammer/pull-off and sl slide to the next note on that string, v vibrato, b (0 4) a whole-tone bend. EACH VOICE FILLS ITS TIME SIGNATURE EXACTLY: 4/4 = 4 quarters = 8 eighths, 3/4 = 3 quarters, 6/8 = 6 eighths; rests complete a short one. A measure without numerator/denominator is 4/4, whatever came before. A second voice (a bass under a melody) is a second string in voices. Examples (4/4): "5.3.4 7.3.4 r.2" (fret 5 then 7 on string 3 (strings from 1, the highest), quarters; a half rest); "(0.1 1.2 0.3).2 x.6.4 r.4" (a chord, a half; a muted note); "E4.8 F#4.8 G4.4 Bb3.2" (notes by pitch (C4 = middle C): Cesure chooses string and fret); "5.3.4{d} 5.3.8 2.1.8{tu 3} 3.1.8{tu 3} 5.1.8{tu 3} 7.2{h}.8 8.2.8" (dotted quarter; a triplet of eighths (each beat carries it); a hammer-on to the next note); "5.3.2 5.3{t}.4 7.2{sl}.8 9.2{v}.8" (a tie to the note before, a slide, a vibrato). A measure: {"id":"p2","numerator":3,"denominator":4,"staves":[{"voices":["0.1.8 2.1.8 3.1.4 5.1.4","0.6.2{d}"]}]}. The full format: https://cesure.app/format

Input Schema

{
  "type": "object",
  "properties": {
    "draft": {
      "type": "string",
      "description": "The draft: the id a previous tool gave (draft)."
    },
    "track": {
      "type": "integer",
      "description": "The track, from 1 (default 1).",
      "minimum": 1
    },
    "from": {
      "type": "integer",
      "description": "First measure replaced, from 1.",
      "minimum": 1
    },
    "to": {
      "type": "integer",
      "description": "Last measure replaced; from - 1 to insert.",
      "minimum": 0
    },
    "measures": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "The new measures, .cesure measure objects as read_score returns them; [] removes the range."
    }
  },
  "required": [
    "draft",
    "from",
    "to",
    "measures"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {}
}
🔴transpose(draft, semitones, notesOffTheNeck, harmonicsOffTheNeck)

Shift the notes of the draft by some semitones; the placement follows, and no note keeps a wrong pitch. A note no string of its track carries at its shifted pitch goes where notesOffTheNeck says: retune_lowest_string tunes the lowest string of the track down to the lowest of those it carries (4 semitones at most), then moves the others by octaves; change_octave moves each by the octaves that put it on the neck. A harmonic that rings in its own form at no shifted string goes where harmonicsOffTheNeck says: keep_harmonic keeps it a harmonic at the octave that holds it, play_fretted plays it as a fretted note at its pitch, losing the harmonic's timbre. By default the lowest string when it carries the notes with no octave, else octaves, and harmonics kept when an octave holds them; play_fretted when no harmonic leaves the neck changes nothing. A choice that cannot place the notes is refused, saying why and naming the one that can. The answer names each string tuned down (retunedStrings: track, string, from, to) and counts the notes moved by octaves (notesMovedByOctaves) and the harmonics played fretted (harmonicsPlayedFretted).

Input Schema

{
  "type": "object",
  "properties": {
    "draft": {
      "type": "string",
      "description": "The draft: the id a previous tool gave (draft)."
    },
    "semitones": {
      "type": "integer",
      "description": "Semitones, -24 to 24.",
      "minimum": -24,
      "maximum": 24
    },
    "notesOffTheNeck": {
      "type": "string",
      "description": "retune_lowest_string or change_octave (default the first when it carries the notes with no octave).",
      "enum": [
        "retune_lowest_string",
        "change_octave"
      ]
    },
    "harmonicsOffTheNeck": {
      "type": "string",
      "description": "keep_harmonic or play_fretted (default the first when an octave holds the harmonic).",
      "enum": [
        "keep_harmonic",
        "play_fretted"
      ]
    }
  },
  "required": [
    "draft",
    "semitones"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {}
}
🔴refinger(draft, track, mode, searchCapo)

Place the notes of the draft again on the neck (string and fret), keeping their pitches: mode auto, standard (lowest frets) or optimized (fewest hand moves); searchCapo lets it choose a capo.

Input Schema

{
  "type": "object",
  "properties": {
    "draft": {
      "type": "string",
      "description": "The draft: the id a previous tool gave (draft)."
    },
    "track": {
      "type": "integer",
      "description": "The track, from 1 (default every track).",
      "minimum": 1
    },
    "mode": {
      "type": "string",
      "description": "auto (default), standard or optimized.",
      "enum": [
        "auto",
        "standard",
        "optimized"
      ]
    },
    "searchCapo": {
      "type": "boolean",
      "description": "Let the placement choose a capo (default false)."
    }
  },
  "required": [
    "draft"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {}
}
🔴undo_last_change(draft)

Give the draft back the score it held before its last change (edit_measures, transpose, refinger, or an undo): the score it holds now becomes the one before, so calling it again redoes. One step only, and only when Cesure had room to keep that score; it says so when it had not.

Input Schema

{
  "type": "object",
  "properties": {
    "draft": {
      "type": "string",
      "description": "The draft: the id a previous tool gave (draft)."
    }
  },
  "required": [
    "draft"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {}
}
🟢search_catalog(query, language)

Search Cesure's catalog of free pieces by title or composer; returns title, artist, licence and link.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Words of a title or a composer; empty lists the catalog."
    },
    "language": {
      "type": "string",
      "description": "en (default), fr or es.",
      "enum": [
        "en",
        "fr",
        "es"
      ]
    }
  },
  "required": [],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {}
}
🟢open_in_cesure(draft)

Show the draft in the Cesure player, to read and hear it. Where the host draws apps, the player plays the draft in the conversation; everywhere, the answer gives the short link that opens it in Cesure, with no account, and the score's summary.

Input Schema

{
  "type": "object",
  "properties": {
    "draft": {
      "type": "string",
      "description": "The draft: the id a previous tool gave (draft)."
    }
  },
  "required": [
    "draft"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {}
}
🟢list_my_scores(offset)

The scores of the person's linked Cesure account ("My scores"), the most recently changed at the top, 200 a call (offset skips that many; when there are more, the answer's more gives the next offset): id, title, when last changed, and its tags; then every tag of the account, with how many scores carry it. Needs the account linked.

Input Schema

{
  "type": "object",
  "properties": {
    "offset": {
      "type": "integer",
      "description": "How many scores to skip, most recent first (default 0): the answer's more gives the next.",
      "minimum": 0
    }
  },
  "required": [],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {}
}
🟢read_my_score(id)

Open one score of the linked account as a draft, by the id list_my_scores gives: the answer is the draft and the score's summary; read_score reads its measures. Needs the account linked.

Input Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "The score's id, as list_my_scores gives it."
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {}
}
🟡save_new_score(draft, title)

Save the draft as a NEW score in the linked account's library (never overwrites one; a free account keeps 3 scores), under a title (default the score's own). Needs the account linked.

Input Schema

{
  "type": "object",
  "properties": {
    "draft": {
      "type": "string",
      "description": "The draft: the id a previous tool gave (draft)."
    },
    "title": {
      "type": "string",
      "description": "The title in the library (default the score's own)."
    }
  },
  "required": [
    "draft"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {}
}
🔴update_my_score(draft)

Write the draft back over the score of the linked account's library it was opened from (read_my_score), as saving in the app does: refused, nothing overwritten, when the score was saved in Cesure since. The library keeps the score's earlier version. Needs the account linked.

Input Schema

{
  "type": "object",
  "properties": {
    "draft": {
      "type": "string",
      "description": "The draft: the id a previous tool gave (draft)."
    }
  },
  "required": [
    "draft"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {}
}
🔴organize_my_scores(create_tags, add, remove, delete_unused_tags)

Organize the scores of the linked account with tags, in ONE batch applied whole or not at all (at most 500 changes, counting the tags add creates): create_tags creates tags, add puts a tag on a score (creating the tag if the account has none of that name; names compare without case), remove takes it off, delete_unused_tags deletes tags no score carries. It never renames, deletes or changes a score, and no score's date moves. The opposite changes reverse an organizing (remove what add put, delete_unused_tags for the tags it created). Needs the account linked.

Input Schema

{
  "type": "object",
  "properties": {
    "create_tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tags to create, by name."
    },
    "add": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "score": {
            "type": "string",
            "description": "The score's id, as list_my_scores gives it."
          },
          "tag": {
            "type": "string",
            "description": "The tag's name, 1 to 30 characters."
          }
        },
        "required": [
          "score",
          "tag"
        ]
      },
      "description": "Tags to put on scores."
    },
    "remove": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "score": {
            "type": "string",
            "description": "The score's id, as list_my_scores gives it."
          },
          "tag": {
            "type": "string",
            "description": "The tag's name, 1 to 30 characters."
          }
        },
        "required": [
          "score",
          "tag"
        ]
      },
      "description": "Tags to take off scores."
    },
    "delete_unused_tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tags to delete if no score carries them, by name."
    }
  },
  "required": [],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {}
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded14 tools