
Belong CheckIn provides MCP Tools — Notes for people who manage event information with MCP. The capability gives organizers and venue teams five defined note operations: get-note, list-notes, create-note, update-note, and delete-note.
Together, these tools cover the full documented note workflow. A connected assistant can create a note, return one note by its identifier, list a set of notes, change permitted fields, or delete a note. Each tool returns its result as JSON text, so the response format remains consistent across the workflow.
The tools are separate by design. Use create-note when a note does not yet exist. Use get-note when the note identifier is already known. Use list-notes when notes need to be filtered, searched, sorted, or paginated. Use update-note for a partial change to an existing note, and use delete-note when an identified note should be removed.
This separation helps the caller choose the operation that matches the immediate task. It also makes the required input clear: some operations need only an id, while listing and creation accept different bodies or optional parameters.
create-note. Pass a CreateNotesBody. The creation body does not include an id or timestamps, and userId is optional. The tool returns the created note as JSON text. This is the starting point when the information needs a new note rather than a change to an existing one.list-notes. The listing tool accepts optional hubId, userId, search, take, skip, cursor, sort, and order inputs. It returns an array of notes as JSON text. Use the relevant optional fields to narrow the list, search it, control how many entries are requested, move through results, or set sorting and ordering.get-note. Pass the note’s id. The result is that note as JSON text. This operation is the direct choice when the caller already has the identifier and needs the individual record rather than an array.update-note. Pass the note id and data. The data value uses UpdateNotesBody and may be partial, so the caller can submit the permitted changes rather than a complete replacement. The update cannot change hubId or createdAt. The tool returns the updated note as JSON text.delete-note. Pass the note’s id. The tool returns the deleted note as JSON text. Because deletion is its own operation and is addressed by identifier, it should be used when the target note is known.The distinction between get-note and list-notes is important. get-note takes one required id and returns one note. list-notes works with optional selection and navigation inputs and returns an array. If the identifier is unknown, the list operation provides the documented search and filtering path; if it is known, the get operation is more direct.
The creation and update inputs also differ. create-note receives CreateNotesBody, excludes identifiers and timestamps, and allows an optional userId. update-note receives an id plus partial data, while protecting the existing hubId and createdAt from change.
MCP Tools — Notes is for organizers and venue teams using a connected assistant to manage notes associated with their event work. It is useful when the caller needs a defined operation for adding, locating, reading, revising, or removing note records.
Use create-note at the point when a new record is required. Later, use list-notes when the relevant note has to be located among other notes. The available hubId and userId filters can narrow the request, while search can be used when searching is needed. The take, skip, and cursor options support documented ways to move through a list, and sort with order controls its arrangement.
Once a note’s id is available, get-note retrieves that exact note. If its permitted information needs to change, update-note accepts a partial update. If it needs to be removed, delete-note handles that final operation by id.
The tool set is also useful when the response needs to be handled consistently. The single-note operations return a note as JSON text, while list-notes returns an array of notes as JSON text. A caller can therefore choose between one record and a collection without treating listing as if it were direct retrieval.
Consider an organizer who needs to work with an existing event note but does not have its identifier at hand. The organizer can use list-notes with a relevant hubId and, when useful, search to request an array of matching notes. The list can also use take, skip, cursor, sort, or order when the request needs those documented controls.
After identifying the intended note, the organizer can pass its id to get-note and receive the individual note as JSON text. If a permitted field needs revision, update-note takes the same id and partial data; the note’s hubId and createdAt remain unchanged because those fields cannot be changed through the update tool. If the note should instead be removed, delete-note takes the id and returns the deleted note as JSON text.
For a new note, the organizer begins with create-note and supplies CreateNotesBody without an id or timestamps. The returned created note can then participate in the same retrieve, list, update, and delete workflow.
Read the complete MCP Tools — Notes documentation to review every tool, input, and output. The page lists the five operations and the exact parameters documented for each one.
Then open Belong CheckIn to get started. When building the note workflow, match each action to its documented tool: create for a new note, list for an array, get for one known identifier, update for permitted partial changes, and delete for removal by identifier.
It can create, list, retrieve, update, and delete notes. The documented tools are create-note, list-notes, get-note, update-note, and delete-note, and their results are returned as JSON text.
Use list-notes. It accepts optional hubId, userId, search, take, skip, cursor, sort, and order inputs and returns an array of notes as JSON text.
No. update-note accepts an id and partial data, but the documented update body cannot change hubId or createdAt. The operation returns the updated note as JSON text.