# Jibble MCP > Jibble MCP connects your AI client directly to Jibble's full time tracking, attendance, and workforce management system. Your agent can list people, check specific time entries, track projects, or audit organization details using one simple connection. Stop switching tabs—manage all your team data through natural conversation. ## Overview - **Category:** human-resources - **Price:** Free - **Tags:** time-tracking, attendance-management, workforce-management, project-tracking, payroll-support ## Description Jibble helps you move beyond viewing dashboards. Instead of manually compiling reports across multiple spreadsheets, your AI client uses this MCP to pull precise workforce data directly from Jibble's platform. Need to know if a specific person clocked in at the right location? Your agent can get that detail instantly. Want to see how many billable hours were logged against a specific project last month? That’s just one query away. This connection lets your agent analyze who worked where, when they worked it, and what type of activity was recorded—all without you writing a single API call. It's powerful workforce management built into the Vinkius catalog so any MCP-compatible client can use it. ## Tools ### get_organization Retrieves basic configuration settings for your entire Jibble account. ### get_person Pulls detailed profile information for a single employee or team member. ### get_time_entry Fetches location data, activity notes, and device info for one specific time record. ### list_activities Lists every possible task type (like 'Meeting' or 'Break') an employee can select when clocking in. ### list_clients Provides a list of all external clients tracked by the organization for billing purposes. ### list_groups Lists all defined teams or work units (like 'Sales Team' or 'Remote Workers') within the company. ### list_locations Retrieves a list of all physical sites or offices where employees can clock in. ### list_people Returns a comprehensive directory listing every employee by name, email, and internal ID. ### list_projects Lists all current and inactive projects set up in the system for time tracking breakdowns. ### list_time_entries Gathers a list of every recorded time entry, including who logged it and how long they worked. ## Prompt Examples **Prompt:** ``` List all people in my Jibble organization. ``` **Response:** ``` I'll fetch the list of all members in your Jibble organization. ``` **Prompt:** ``` Show me the recent time entries. ``` **Response:** ``` I'll retrieve the latest time tracking entries from Jibble. ``` **Prompt:** ``` What are the active projects in Jibble? ``` **Response:** ``` I'll look up the list of configured projects in your account. ``` ## Capabilities ### Audit organizational settings Retrieve core details about your entire Jibble organization account. ### Look up employee records Fetch comprehensive profiles for individual team members, including contact and ID information. ### Review specific time logs Get detailed data on a single recorded time entry, including location and notes for auditing purposes. ### List configured resources Pull lists of all defined groups, clients, projects, activities, or locations used across the company. ### Query historical time activity Retrieve a list of all existing time entries to monitor total hours worked by the workforce. ## Use Cases ### Investigating Time Discrepancies A manager suspects an employee's time log is wrong. They ask their agent, 'Check the time entry for John Smith last Tuesday.' The agent uses get_time_entry and get_person to pull all relevant details—location, notes, and device info—immediately showing if the record is suspicious. ### Generating Project Utilization Reports A PM needs to prove how much time was spent on a specific client project. They ask their agent to cross-reference list_projects with list_time_entries, linking every logged hour back to the correct billing source. ### Onboarding and Role Mapping HR needs to update access for new hires. They first use list_people to find existing users, then check list_groups and list_locations to ensure the new employee is assigned to the correct department and site. ### Compliance Auditing An auditor needs proof that employees are only clocking in at authorized sites. They run a query comparing all entries from list_time_entries against the list_locations tool, flagging any site outside the approved network. ## Benefits - Stop guessing about who logged hours. Use list_people and get_person to build a definitive directory of all employees, ensuring your agent always has the correct IDs for time entry queries. - Never lose track of billing data again. By listing clients (list_clients) and projects (list_projects), you can instantly correlate work done against revenue-generating accounts. - Audit compliance faster than ever. Running list_time_entries allows your agent to pull the full history of time logged, letting you quickly verify dates and durations for payroll checks. - Identify team bottlenecks using list_groups and list_activities. You can programmatically check if a certain group is consistently clocking into non-standard activities, flagging potential policy issues. - Verify physical work locations effortlessly. List_locations allows your agent to confirm if an employee's recorded time entry (get_time_entry) matches the expected site for that project. - Centralize all workforce data. Instead of checking separate reports, you can query list_organization and get_organization details to verify account-wide settings in one go. ## How It Works The bottom line is, you tell your agent what you need in plain English, and it handles all the complex data pulling from Jibble's systems for you. 1. Your AI client first authenticates with your Jibble account using Vinkius. 2. You ask your agent a question, like 'Show me all time entries for Q3.' 3. The MCP executes the necessary tool calls (e.g., list_time_entries) and returns clean, structured data to your client. ## Frequently Asked Questions **How do I find out what activities employees can select using Jibble MCP?** You use list_activities. This tool retrieves a complete list of all predefined work categories, like 'Meeting' or 'Break,' that staff members have available when clocking in. **Can I check if an employee exists before querying their time using Jibble MCP?** Yes. You should run list_people first to get the comprehensive directory and confirm the correct internal ID. Then, use that ID when calling get_person or list_time_entries. **What data does get_time_entry return for auditing purposes?** get_time_entry returns detailed information about a single time log, including the location where it was clocked and any notes attached to the entry. This is key for discrepancy checks. **How do I find out which clients are available in my Jibble organization?** Just call list_clients. This tool retrieves a comprehensive list of every client that the company tracks, which is vital when auditing billable hours. **Is there a way to see all configured projects using Jibble MCP?** Yes, you use list_projects. It pulls a full record of every project setup in your account, allowing you to track work against existing initiatives.