Jibble MCP server

What the model can do

Jibble time tracking and attendance: team members, who is clocked in now, raw clock-in and clock-out entries, daily timesheet totals with overtime, tracked time by person or project, time off requests and approval periods, and the projects, activities, clients, groups, locations and leave policies they use; when you ask, can clock someone in or out, edit or remove a time entry, request, approve or reject time off, approve, reject or reopen a timesheet period, add, edit, archive or delete a member, and create projects, clients, activities and holidays.

Reads

• jibble_list_peopleTeam members: name, preferred name, member code, status (Joined, PendingInvitation, NotInvited, Removed), group and join date, with their Jibble ids.
• jibble_who_is_workingWho is clocked in right now, with what project or activity and since when, plus how many people are in, out and on a break.
• jibble_list_time_entriesRaw clock-in, clock-out and break entries in time order for a date range (by the day each entry belongs to), with person, project, activity and note…
• jibble_timesheets_summaryDaily timesheet totals per person for a date range: hours tracked, regular and overtime each day, first in and last out, and each person's total.
• jibble_tracked_time_reportTracked time for a period grouped by member or project, optionally split by the other, with billable amounts.
• jibble_list_time_offTime off requests: person, leave policy, full-day or hourly, start and end, length and status (Pending, Approved, Rejected, Cancelled).
• jibble_list_pay_periodsTimesheet approval periods per person: start and end, hours tracked, regular, overtime and time off, status (Open, Submitted, Approved, Rejected…
• jibble_list_referenceThe ids and names behind time entries and requests: projects (with client), activities, clients, groups, locations, schedules…

Acts, when you ask

These change something in Jibble. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• jibble_clock_inClocks a team member in now, on a project, activity or location if given; it appears on their timesheet and in who is working…
• jibble_clock_outClocks a team member out now, ending their current shift on the timesheet.
• jibble_update_time_entryChanges a time entry's project, activity or note; only the fields passed change, and the timesheet is recalculated.
• jibble_remove_time_entryRemoves a time entry from the timesheet (Jibble archives it, its documented delete), so its hours stop counting.
• jibble_request_time_offCreates a time off request for a team member under a leave policy, pending approval: full days with start_date and end_date…
• jibble_decide_time_offApproves, rejects or cancels a time off request (or sets it back to Pending), which changes the person's leave balance and timesheet…
• jibble_change_pay_period_statusApproves, rejects or reopens a person's timesheet approval period.
• jibble_create_memberAdds a team member to the Jibble organisation.
• jibble_update_memberChanges a team member's name, preferred name, group or work schedule; only the fields passed change.
• jibble_archive_memberArchives a team member (status Removed), ending their access to Jibble while keeping their time data.
• jibble_delete_memberPermanently deletes a team member and their data from Jibble; this cannot be undone (jibble_archive_member keeps the data).
• jibble_create_projectCreates a project that time can be tracked against, optionally for a client and location.
• jibble_create_clientCreates a client that projects can belong to.
• jibble_create_activityCreates an activity (a kind of work, such as Design or Driving) that time can be tracked against.
• jibble_add_holidayAdds a holiday on a date to a holiday calendar, which changes expected hours and overtime for everyone on that calendar.

Connect it

First connect Jibble on Dashboard → Connections, then add Memtro to your client once. The Jibble tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Jibble connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Who is clocked in right now?
• › How many hours did the team track last week, including overtime?
• › Which time off requests are pending?
• › How much time went on the Website project this month?
• › Clock Dan Fletcher out.

Questions

Is this an official Jibble MCP server?

No. It is Memtro's MCP server with Memtro's Jibble connector behind it: the connector reads Jibble through its API with the credentials you connect on Dashboard → Connections, and Jibble publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Jibble?

Only when you ask, and only what it has been granted: clock a team member in; clock a team member out; edit a time entry's project, activity or note; remove (archive) a time entry; request time off for a team member; approve, reject or cancel a time off request; approve, reject or reopen a timesheet approval period; add a team member, optionally emailing an invitation; edit a team member's name, group or schedule; archive a team member, ending their access; delete a team member permanently; create a project; create a client; create an activity; add a holiday to a calendar. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · People and HR

• BambooHR MCP server
• Personio MCP server
• Microsoft Entra ID MCP server
• Google Workspace MCP server
• HiBob MCP server
• Greenhouse MCP server