Jostle MCP by usefulapi

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.usefulapi/jostle and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 5 Nov 2026. Not supplied by the maker.

• jostle_list_users

  List the users in the Jostle instance with their id, username and display name. Use the id or username when you create or update a task. Jostle API: GET /v2/people.

• jostle_list_presets

  List the Jostle list presets (named groups of users for assignees or collaborators). Use a preset id when you create a task. Jostle API: GET /v2/people/list-presets.

• jostle_get_task

  Get one task by id: title, description, due date, assignee, collaborators, completion status and comment count. The token user must be the assignee or a collaborator. Jostle API: GET /v2/tasks/task/{i

• jostle_list_task_comments

  List the comments on a task, newest page first, with paging. Jostle API: GET /v2/tasks/task/{id}/comments.

• jostle_create_task

  Create a task in the Tasks of one assignee. Give the assignee as userId, username or employeeId, and optional collaborators or a preset. Due dates are saved in Eastern Standard Time. Jostle API: POST

• jostle_update_task

  Change a task with JSON Patch operations (RFC 6902). Allowed paths: /title, /description, /dueDate, /assignee, /collaborators, /completionStatus. Jostle API: PATCH /v2/tasks/task/{id}.

• jostle_add_task_comment

  Add a comment to a task as the token user. Comments are visible to everyone who can see the task. Jostle API: POST /v2/tasks/task/{id}/comment.