Everhour
Everhour is a time tracking and expense management software equipped with budgeting, forward resource planning, expense tracking, dashboards, and reports.
Verdict
Common use cases
- Log time entries during standup
- Create tasks from meeting notes
- Pull weekly time reports by project
- Add clients before kicking off work
- Check who logged hours yesterday
Integration
- Vendor
- Everhour
- Category
- other
- Auth
- API_KEY
- Tools
- 24
- Composio slug
everhour
Tools
- Create Client
Tool to create a new client in everhour. use when you need to add a client before tracking time or assigning it to projects.
- Create Project
Tool to create a new project in everhour. use after gathering project details to persist a new project.
- Create Section
Tool to create a new section in a project. use when you need to organize tasks under an existing project after confirming the project id.
- Create Task
Tool to create a new task in a project. use when you need to quickly add a task under a specific project id. example: "create a task named 'write tests' in project proj 123456".
- Delete a clientdestructive
Tool to delete a client. use when you need to permanently remove a client from everhour after confirming the client id.
- Delete a projectdestructive
Tool to delete a project. use when you need to permanently remove a project from everhour after confirming the project id.
- Delete a sectiondestructive
Tool to delete a section. use when you need to permanently remove a section from everhour after confirming the section id.
- Get Authenticated User Profile
Tool to retrieve profile information of the authenticated user. use after providing api key to fetch current user's profile details.
- Get Client by ID
Tool to retrieve a specific client by id. use when you need detailed client information after obtaining the client's id.
- Get Project
Tool to retrieve a specific project. use after you have the project id if you need its details.
- Get Section
Tool to retrieve a specific section. use when you need detailed section data by its id.
- List all projects
Tool to list all projects. use when you need to retrieve every project accessible by your authenticated api key.
- List Clients
Tool to list all clients. use when you need an overview of workspace clients.
- List Expense Categories
Tool to list all expense categories. use when you need to retrieve every category available for categorizing expenses after authenticating with your api key.
- List Expenses
Tool to retrieve all expenses. use when you need to review expense records across your workspace.
- List Invoices
Tool to list all invoices. use when you need to retrieve every invoice in your everhour workspace after authenticating with your api key.
- List Sections
Tool to list sections within a project. use when you need to retrieve all sections for a specified project after authenticating with your api key.
- List Tags
Tool to list all tags. use when you need to retrieve every tag in your everhour workspace after authenticating with your api key.
- List Team Members
Tool to list all team members. use when you need to retrieve your everhour team's current roster after authenticating with your api key.
- List Teams
Tool to list all teams. use to retrieve available teams for your api key.
- List Webhooks
Tool to list all webhooks. use when you need to retrieve every configured webhook for the account after authenticating with your api key.
- Start Timer
Tool to start a new timer for a task. use when you need to begin tracking time on a specific task.
- Update an existing project
Tool to update an existing project. use after confirming the project id when modifying project details.
- Update Client
Tool to update an existing client. use when you need to modify client details such as name, hourly rate, or archived status after confirming the client id.
Setup
Setup guide
- 11. Open your Switchy workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP Integration' and select Everhour from the list. 3. Log into your Everhour account at everhour.com and go to Settings > Integrations > API. 4. Generate a new API key and copy it to your clipboard. 5. Paste the key into the Switchy connection dialog and click 'Connect'. 6. Switchy will verify the key by fetching your user profile — if successful, you'll see a green checkmark. 7. Open any Space and type '@Everhour get my profile' to confirm the connection works. 8. To invoke a tool, @mention Everhour in a message and describe what you need — for example, '@Everhour create a task called Design review in project 12345'.
What teammates see: by default, memories from Everhour are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Log Time Entry
@Everhour log 3 hours to task 98765 with the note 'API integration work' for today's date.Open in a Space →
Create Project Task
@Everhour create a task named 'Update landing page copy' in project 54321 and assign it to me.Open in a Space →
Weekly Time Summary
@Everhour show me total time logged by project for the last 7 days, grouped by team member.Open in a Space →
Add New Client
@Everhour create a client named 'Acme Corp' so we can track time against their projects starting today.Open in a Space →
Check My Profile
@Everhour get my authenticated user profile and show me my email and role.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Everhour show me all time entries logged by the team this week, grouped by project
Based on the authenticated user's workspace, this week the team logged 127.5 hours across 4 active projects: 'Mobile App Redesign' (48 hours, 3 contributors), 'API Migration' (52.5 hours, 4 contributors), 'Marketing Site Updates' (18 hours, 2 contributors), and 'Internal Tools' (9 hours, 1 contributor). The Mobile App Redesign project shows the highest concentration on Tuesday and Wednesday. This is an illustrative example; actual output depends on your workspace's time-tracking data and the current date range.
This example demonstrates Everhour's read capabilities for aggregating time data. Requires an API key with read access to time records. The MCP can surface team utilization patterns, but the granularity depends on how your team logs time—if tasks aren't consistently tagged to projects, summaries may be incomplete.
@Everhour create a new project called 'Q2 Product Launch' under the client 'Acme Corp' and add three sections: Planning, Execution, Review
Project 'Q2 Product Launch' created successfully with ID proj_789012 under client 'Acme Corp' (client_456789). Three sections have been added: 'Planning' (section_111), 'Execution' (section_222), and 'Review' (section_333). The project is now available for task creation and time tracking. Team members with workspace access can begin logging hours against this project immediately. This is an illustrative example; actual IDs and client associations depend on your Everhour workspace configuration.
This example shows Everhour's project-creation workflow, chaining multiple tools (Create Client lookup, Create Project, Create Section). The MCP executes these actions sequentially, so if the client name doesn't match an existing record, it may prompt for clarification or create a new client. Be aware this writes permanent records to your Everhour workspace.
@Everhour analyze the last month of time entries and draft a summary of which projects are over budget based on estimated hours
Reviewing time entries from the past 30 days against project estimates: 'API Migration' is 18 hours over its 120-hour budget (now at 138 hours, 15% overrun), primarily due to unexpected database schema changes in week 3. 'Marketing Site Updates' is on track at 82% of its 60-hour estimate. 'Mobile App Redesign' is under budget by 12 hours, with most tasks completed ahead of schedule. Recommendation: consider reallocating buffer hours from Mobile App to API Migration if the schema work continues. This is an illustrative synthesis; actual budget analysis depends on whether estimates are set in your Everhour projects.
This example pairs Everhour's time-tracking data with AI reasoning to surface budget risks. The MCP retrieves raw time logs, but the AI interprets trends and suggests actions. Accuracy depends on your team consistently logging time and setting project estimates—if estimates are missing, the analysis will note gaps rather than calculate overruns.
Use-case deep-dives
When Everhour MCP streamlines new client setup for agencies
A 6-person design agency onboards 2-3 new clients each month, and each client needs a fresh project structure in Everhour before billable work starts. The Everhour MCP wins here because it chains Create Client, Create Project, and Create Section calls in one AI conversation instead of clicking through the web UI three times per client. The assistant can ask for client name and project scope, then scaffold the entire time-tracking hierarchy in 30 seconds. The trade-off: if your agency runs on fixed-fee contracts and rarely tracks hours by task, this MCP is overkill—you'd be better off with a simpler project-management integration. But for hourly billing shops where time entry structure matters, this MCP cuts onboarding friction by half.
Using Everhour MCP to archive stale projects in batch
A 12-person product studio wraps 8-10 client projects per quarter, and each finished project leaves behind a project shell and several sections in Everhour that clutter the active workspace. The Everhour MCP makes sense for this cleanup ritual because Delete a project and Delete a section tools let the team describe which projects to archive ("delete all projects tagged 'Q1 2024' that have zero hours logged this month") and the assistant handles the API calls in sequence. Without the MCP, someone clicks through each project manually or writes a one-off script. The boundary: if your studio keeps all historical projects visible for reference, deletion isn't the workflow—you'd want a read-heavy MCP instead. For teams that archive aggressively, this MCP turns a 20-minute chore into a 2-minute prompt.
When Everhour MCP isn't worth it for solo time tracking
A solo freelancer juggles 4 active clients and logs time daily across 15-20 tasks. The Everhour MCP offers Create Task and time-entry tools, but the setup cost (API key, MCP config, learning the assistant's task-creation syntax) outweighs the benefit for a one-person workflow. The native Everhour timer or mobile app is faster for quick "start timer on task X" actions because it's always one tap away. The MCP would make sense if this freelancer scaled to a 3-person team and needed to coordinate task creation across multiple people in Slack or a shared AI workspace—then the assistant becomes the shared interface. For solo use, stick with the vendor's own UX unless you're already living in an AI-first workspace for other reasons.
Frequently asked
What does the Everhour MCP let Switchy do?
It connects Switchy to your Everhour time tracking workspace so AI agents can create clients, projects, sections, and tasks, plus fetch user profiles. Agents can also delete entities when needed. This means you can ask Switchy to set up project structures or log tasks without opening Everhour's interface.
Do I need admin access to connect Everhour?
You need an Everhour API key, which any user can generate from their account settings. The MCP inherits whatever permissions that API key has — if your Everhour role can't create projects or delete clients, neither can the agent. Check your role before connecting if you want full write access.
Can the Everhour MCP log time entries or pull reports?
No. The 24 tools focus on workspace structure — creating and deleting clients, projects, sections, and tasks. Time entry logging and report generation aren't exposed. If you need those, use Everhour's web app or their REST API directly alongside this MCP for setup tasks.
Why use this instead of Everhour's web interface?
Speed and context. If you're already describing a project scope in Switchy, the agent can scaffold the Everhour structure in one prompt instead of you clicking through forms. It's faster for bulk setup or when project details live in a chat thread, not a spreadsheet.
Who on the team should connect the Everhour MCP?
Whoever manages your Everhour workspace structure — typically a project manager or ops lead. Their API key determines what the agent can touch. Don't connect it with a junior account unless you want agents limited to read-only or task-creation-only permissions in Everhour.