TimeCamp
TimeCamp is a time tracking solution designed to help businesses of all sizes track time for projects to maximize their profits.
Verdict
Common use cases
- Draft weekly status updates by project
- Estimate team capacity against active work
- Generate project lists for client reports
- Cross-reference tasks during sprint planning
- Audit which projects are still open
Integration
- Vendor
- TimeCamp
- Category
- other
- Auth
- API_KEY
- Tools
- 1
- Composio slug
timecamp
Tools
- Get Projects List
This tool retrieves a list of all projects from timecamp. in timecamp's api, projects are represented as tasks with no parent id (root-level tasks). it requires the api token parameter for authentication and supports an optional 'format' pa
Setup
Setup guide
- 11. Open your TimeCamp account settings and navigate to the API section to generate a new API token. 2. Copy the token to your clipboard — you'll need it in the next step. 3. In Switchy, click Integrations in the left sidebar, then find TimeCamp in the MCP directory. 4. Click Connect and paste your API token when prompted. 5. Switchy will verify the token by fetching your project list — this takes 2-3 seconds. 6. Once connected, open any Space and type '@TimeCamp get my projects' to test the connection. 7. The AI will return a list of all root-level projects from your TimeCamp workspace. 8. Use this data in any prompt where you need to reference active projects by name or structure.
What teammates see: by default, memories from TimeCamp 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
Weekly Project Rollup
@TimeCamp get my projects, then create a weekly status update template with sections for each active project. Include placeholders for progress notes and blockers.Open in a Space →
Capacity Planning Check
@TimeCamp show me all projects, then estimate how many active initiatives our team is juggling right now. Flag if we're likely overcommitted.Open in a Space →
Client Report Prep
@TimeCamp retrieve our project list and format it as a bulleted summary suitable for a client-facing report. Group by status if possible.Open in a Space →
Sprint Planning Reference
@TimeCamp get all projects, then help me identify which ones should be prioritized in our next two-week sprint based on their names and structure.Open in a Space →
Project Audit
@TimeCamp pull the complete project list and flag any that look outdated, duplicated, or candidates for archiving based on naming patterns.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@TimeCamp show me all active projects in our account so I can see what we're tracking time against
Here are your TimeCamp projects: **Website Redesign** (ID: 12345, billable, 127 hours logged), **Mobile App Development** (ID: 12346, billable, 89 hours logged), **Internal Operations** (ID: 12347, non-billable, 43 hours logged), **Client Support** (ID: 12348, billable, 201 hours logged). All projects are currently active. The Website Redesign and Mobile App Development projects show the highest recent activity based on logged hours.
This example demonstrates the core read capability of the MCP. TimeCamp's API returns projects as root-level tasks, so the MCP translates that structure into a project list. You'll need a valid API key with read access to your TimeCamp account. The response reflects your account's current state—project names, IDs, and hours will vary.
@TimeCamp which project has the most time logged this month and break down the hours by team member
The **Client Support** project leads with 87 hours logged in December. Breakdown: Sarah Martinez logged 34 hours (39%), James Chen logged 28 hours (32%), and Maria Rodriguez logged 25 hours (29%). This represents a 23% increase from November's total. The team is averaging 21.75 hours per person on support work, suggesting this may need dedicated capacity planning for Q1.
This synthesis example shows the AI reasoning over TimeCamp data. The MCP retrieves the project list, but the AI must infer time-tracking patterns and calculate percentages from the available data structure. Note that TimeCamp's API may require separate calls for detailed time entries—this example assumes the MCP can access that granularity through the projects endpoint or related tools.
@TimeCamp I need to audit our billable vs non-billable projects—give me a summary with total hours for each category
**Billable Projects:** 4 projects totaling 417 hours logged (Website Redesign: 127h, Mobile App: 89h, Client Support: 201h). **Non-Billable Projects:** 1 project totaling 43 hours (Internal Operations). Your billable-to-non-billable ratio is 9.7:1, meaning 90.6% of tracked time is client-facing. This is healthy for a services business, though the 43 hours on internal operations may be underreported if admin work isn't consistently logged.
This example highlights analytical use cases where the AI synthesizes project metadata into business insights. The MCP provides raw project data (billable flags, hours), and the AI calculates ratios and offers context. Be aware that TimeCamp's billable flag is set at the project level—if your team tracks billable vs non-billable at the task level within projects, this summary may oversimplify your actual billing structure.
Use-case deep-dives
When TimeCamp MCP makes monthly invoicing less painful
A 6-person creative agency bills clients by project and needs to pull time entries into their invoicing flow every month. The TimeCamp MCP wins here because it surfaces the project list directly in Switchy—no tab-switching to export CSVs or copy-paste project IDs. Your finance lead can ask the AI to fetch all projects, filter by client name, and format the data for their billing template in one prompt. The single-tool limitation means you're only getting the project roster, not granular time entries or user breakdowns, so this works best when your invoicing logic lives elsewhere and you just need the project scaffold. If your agency runs 40+ active projects simultaneously, manually mapping project names to client codes gets tedious—at that scale, a direct TimeCamp-to-accounting integration beats an MCP middleman.
Why solo consultants skip this MCP for project lists
A solo consultant tracks 8-12 client projects in TimeCamp and wants to generate status updates or retrospectives using AI. The TimeCamp MCP technically works—it'll pull your project list into Switchy—but the juice isn't worth the squeeze for one-person shops. You're authenticating an API key to retrieve data you already see in TimeCamp's own dashboard, and the MCP doesn't expose time entries or task details, just the top-level project roster. For freelancers, the faster move is to export a TimeCamp report once a quarter and drop it into Switchy as a file upload, then query it without maintaining an API connection. This MCP makes sense when multiple people need programmatic access to the same project list, not when you're the only user and the data rarely changes.
When this MCP helps ops teams map project workload
A 10-person support ops team uses TimeCamp to track time across internal improvement projects (documentation rewrites, tooling upgrades, process audits). The team lead runs a monthly capacity review and needs to see which projects are still active versus archived. The TimeCamp MCP fits this scenario cleanly: it retrieves the full project list in Switchy, and the lead can ask the AI to group projects by keyword, flag stale ones with no recent activity (inferred from naming patterns), or cross-reference against a roadmap doc. The API key auth is straightforward for a single ops lead, and the one-tool scope is enough because the goal is project inventory, not granular time analysis. If your team needs to drill into who logged hours on which tasks, you'll hit the MCP's ceiling fast—at that point, TimeCamp's native reports or a BI tool is the right call.
Frequently asked
What does the TimeCamp MCP do in Switchy?
It pulls your TimeCamp project list into Switchy conversations. TimeCamp structures projects as root-level tasks in their API, so this MCP fetches those top-level items. You can reference project names, IDs, and hierarchy without switching to the TimeCamp web app. It's read-only — you can't create projects or log time through this integration.
Do I need admin access to connect TimeCamp?
No, but you need an API key from your TimeCamp account settings. Any TimeCamp user can generate their own key under Personal Settings > API. The MCP reads projects visible to that user, so if your account has restricted project access in TimeCamp, Switchy will see the same subset.
Can the TimeCamp MCP log time entries or start timers?
No. It only retrieves the project list. If you need to log hours or start a timer, use TimeCamp's web app or their official mobile apps. This MCP is for pulling project context into Switchy — think of it as a reference tool, not a time-tracking interface.
Why use this instead of just opening TimeCamp in a browser tab?
Speed and context. When you're drafting a proposal or reviewing a sprint in Switchy, the AI can fetch project names and IDs inline without you alt-tabbing. It's faster than searching TimeCamp's UI, and the data stays in your conversation history. For actual time tracking, you'll still use TimeCamp directly.
Does connecting TimeCamp count against my Switchy plan limits?
MCP connections don't count as seats. The API key belongs to one TimeCamp user, but any Switchy team member can query the projects in shared conversations. If your team has multiple TimeCamp accounts with different project visibility, you'll need to decide whose key to connect.