Key Features
Use Cases
Explore
Ask Claude, ChatGPT, Cursor, Codex, and other AI agents about hours, budgets, payroll, and leave in plain language. And get the answer immediately. Set up in two minutes.
No credit card required
Free up to 10 users
Cancel anytime
Join 29,000+ Organizations
You ask:
Is anyone quietly burning out? Look for people whose tracked hours have climbed for three or more consecutive weeks, and tell me what they've been working on.
ChatGPT answers:
Two people fit. One has gone from 38 to 51 weekly hours over four weeks, almost entirely on a single project. The other has climbed more gradually and is spread across five projects, with rising late-evening activity. Neither has taken leave in the period.
You ask:
What's about to go over budget? Not what already has.
Codex answers:
Four projects are past 80% of allocated hours with work still open. At the current weekly burn, two of them will cross budget within nine days. One of those has three unassigned tasks still in scope.
You ask:
Which clients were least profitable last quarter? Compare billable hours against what we actually invoiced them, and factor in the unbilled time.
Claude answers:
Three clients came in below margin. Northwind logged 412 hours against 340 invoiced; 72 hours unbilled, roughly $6,100 at their rate. Two smaller accounts show similar gaps but under 20 hours each. Northwind's overage is concentrated in revisions logged after the milestone date.
What it covers
Timesheets
Timesheets, idle time, live tracking status, latest member activity
Reports
Clock in/out records, time and activity, manual entries, activity trends
Apps & URLs
App and website usage, org-wide top usage, suspicious activity logs
Projects
Projects, tasks, memberships, billable rates, client project lists
Payroll
Invoices, payment logs, payment settings, payables, payroll summaries
Leave
Leave applications, assignments, balances, periods, policies, types
Organization
Organization details, members, teams, client records
Screen monitoring
Screenshots
Settings → API & MCP → Generate Key. Tick the areas it should reach.
Every client connects to the same Streamable HTTP endpoint:
https://mcp.apploye.com/mcp
Paste the setup snippet into your AI assistant, then ask it about your Apploye data. Setup snippets for Claude Code, Cursor, Codex, and OpenCode are in the docs. Copy, paste, done.
Read DocumentationGenerate a Key
Settings → API & MCP → Generate Key. Tick the areas it should reach.
Point Your Assistant at the Server
Every client connects to the same Streamable HTTP endpoint: https://mcp.apploye.com/mcp
Ask Something
Paste the setup snippet into your AI assistant, then ask it about your Apploye data. Setup snippets for Claude Code, Cursor, Codex, and OpenCode are in the docs. Copy, paste, done.
Read Documentation
Every tool is read-only. Nothing in your account can be created, edited, or deleted through MCP. So it cannot modify timesheets, invoices, leave balance, or anything else.
View Permissions
All seven other areas are on when you create a key. Screenshots are not. They can contain private information that has nothing to do with work, and exposing it to an AI system should be a deliberate choice. So we made it a deliberate second step.
Manage Access
Give a key access to projects and payroll and nothing else, and the tools for everything else never appear. Your assistant doesn't get told no. It never learns there was anything to ask for.
Set Scopes
Separate credentials, separate lifecycle. Revoke, rotate, or replace your MCP key without affecting anything else you've built.
Manage Keys
An open standard for connecting AI assistants to real data. Instead of pasting a report into a chat, the assistant queries your account directly and works from what's live.
No. Read-only for every tool, no exceptions. It can tell you an invoice is unpaid. It cannot mark it paid.
Claude Code, Cursor, Codex, and OpenCode connect to the same endpoint over Streamable HTTP.
Only if you switch that on yourself; it's the one area that's off by default.
Access ends immediately. The tools vanish from your assistant on its next request.
No. MCP key has separate credentials, separate scopes, and a separate lifecycle.
The MCP server is included in the API Access add-on, which costs $1/user/month. This add-on also comes in the Apploye Power plan. The plan costs $8/user/month annually.
