Jibble MCP. Audit Time Logs, Personnel Data & Projects.
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.
Claude 
ChatGPT 
Cursor 
Gemini 
Windsurf 
VS Code 
JetBrains 
Vercel Give Claude and any AI agent real-world access
Retrieve core details about your entire Jibble organization account.
Fetch comprehensive profiles for individual team members, including contact and ID information.
Get detailed data on a single recorded time entry, including location and notes for auditing purposes.
Pull lists of all defined groups, clients, projects, activities, or locations used across the company.
Retrieve a list of all existing time entries to monitor total hours worked by the workforce.
Ask an AI about this
Waiting for input…
What AI agents can do with Jibble: Workforce Management Tools (10)
Use these ten tools to analyze every facet of your workforce, from listing all employees to auditing specific time entries against defined projects.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Jibble MCPGet 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...
List Clients
Provides a list of all external clients tracked by the organization for billing...
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...
List Projects
Lists all current and inactive projects set up in the system for time tracking...
List Time Entries
Gathers a list of every recorded time entry, including who logged it and how long...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Jibble integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Jibble, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Jibble. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The Payroll Report Nightmare
Right now, generating an accurate payroll report means juggling three different sources: the timesheet system, the project management board, and the internal HR roster. You spend hours exporting CSVs from each, then manually merging them in Excel—checking if employee IDs match, if locations are correct, and if every time entry links back to a valid client.
With this MCP, your agent handles that entire mess. Instead of clicking through five separate dashboards and copy-pasting into one master sheet, you simply ask the question: 'Give me all billable hours for Q2.' You get clean, structured data instantly.
Accessing Project Data with list_time_entries
Previously, if you wanted to know the total time logged on 'Project Alpha' for a specific employee, you had to search through every single entry record manually. You couldn't easily filter by both project and person simultaneously.
Now, your agent uses list_time_entries to pull all relevant records and filters them down instantly. The data shows exactly how long the person worked on that project, making audit trails immediate.
What Jibble MCP does for your AI
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.
019d75bc-f6c3-72d7-b600-4d7e149658b2 
How to set up Jibble MCP
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.
Your AI client first authenticates with your Jibble account using Vinkius.
You ask your agent a question, like 'Show me all time entries for Q3.'
The MCP executes the necessary tool calls (e.g., list_time_entries) and returns clean, structured data to your client.
Who uses Jibble MCP
HR Operations Managers who are sick of manual compliance checks; Payroll Specialists needing accurate time logs for billing; or Project Leads who struggle to prove billable hours by cross-referencing multiple spreadsheets. If your job involves verifying 'who did what, where, and when,' this is for you.
Uses the MCP to verify employee details (get_person) or check if groups (list_groups) are correctly set up before a large company policy change.
Runs checks on all time entries using list_time_entries and get_time_entry to ensure hours match pay periods accurately.
Queries the MCP to pull project details (list_projects) and correlate them with employee activities (get_person, list_activities) to measure utilization rates.
Benefits of connecting Jibble MCP
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.
Jibble MCP 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.
Jibble MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Treating it like a simple directory lookup
Asking only for 'list_people' and assuming that gives you project allocation data. You get names, but no context on what they worked on.
To link people to projects, first use list_people to identify the IDs, then run list_time_entries or list_projects to pull the associated time logs. Never rely on a single tool for complex reports.
Forgetting about organizational scope
Running a query without first verifying account settings using get_organization, resulting in vague errors because your agent doesn't know what data is available.
Always start by calling get_organization. This verifies the full configuration and ensures that subsequent calls (like list_groups or list_locations) are scoped correctly for the entire organization.
Confusing activity with project type
Assuming 'list_activities' will tell you which client a meeting was for. Activities only track what they were doing, not who paid for it.
To get billing context, you must combine list_clients and list_projects with the time data from list_time_entries. Activities just categorize the work.
When to use Jibble MCP
Use this MCP if your primary need is auditing or reporting on time and workforce allocation. You need to know who logged hours, against which project, and at what location. Don't use it if you only need simple CRM functions; for example, if you just want to update a client's phone number without any time tracking context, a standard CRM connector is better.
However, don't use it either if your core pain point is managing payroll calculations itself—this MCP provides the raw data (list_time_entries) that feeds into payroll systems; it doesn't execute the calculation. If you need to manage internal knowledge bases or document retrieval alongside time logs, look for a dedicated indexing tool instead of relying on Jibble.
Frequently asked questions about Jibble MCP
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.