# Your logged hours. A week you can read. Source: https://corespeed.io/integrations/timely Connect Timely to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent reads logged hours, projects, tags, people and filtered reports in the Timely workspaces you belong to, and turns them into a weekly summary or a billing check. Timely grants one manage scope, so logging or changing time is a separate call that approvals can hold. ## Set up an agent Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)` It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Timely after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up ## See the whole week. Find the missing hours Ask your agent for last week's hours by client and by person, and the entries a billing check would catch. You ask your agent: "Summarize last week's Timely hours by client and by person. Flag anyone under 30 hours and any entry without a tag. Do not change any entries." It calls CoreSpeed: - `timely__filter_report`: ok, 612 ms - `timely__list_time_entries`: ok, 455 ms It reads from: Timely. ### Weekly hours: Last week, by client and person. 212 hours across three clients. One person is under 30 hours, and six entries have no tag. **By client** - Lakeside 74 h, Internal 70 h, Coastline 68 h. **Follow up** - Check in with Stewart about the 22 hours. - Tag six entries before billing. _Illustrative example · Fictional data · No entry changed_ All connectors: https://corespeed.io/docs/connectors ## From hours to the weekly check Requests you can make once Timely is connected. The data is fictional. ### See the week by client Last week · hours by client · Filtered report - Total: 212 hours - Largest: Lakeside, 74 hours - From the workspaces you belong to ### Find the gaps Hours by person · Under the weekly target - Under 30 h: Stewart, 22 hours - No tag: 6 entries - Nothing changed ### Log time with a check A time entry · Approvals - Entry: 2 h, Lakeside - Rule: Ask before writing to Timely - Waiting for you Full example: https://corespeed.io/solutions/agent-approvals (Markdown: https://corespeed.io/solutions/agent-approvals.md) ## Keep your agent. Bring your work One CoreSpeed account, across compatible agents. 1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in. 2. **Connect Timely**: Authorize the account and the content you need. 3. **Start with one task**: Ask for a summary, a brief, or a draft. Review the answer. Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor ## Questions ### Which Timely workspaces can the agent use? The workspaces the connected Timely user belongs to. Timely grants one scope that covers reading and writing there, so approvals are how you hold writes. ### Can the agent log time or start a timer? Yes, when you ask. Logging, editing or starting a timer is a separate tool call, and approvals can hold it for a person. How approvals work: https://corespeed.io/docs/approvals ### Does this replace Timely's automatic tracking? No. Timely keeps tracking and logging. CoreSpeed lets your agent read the hours and draft the summary. ### Do I have to switch agents? No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once. ### Can my agent access every account in our organization? No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private. ### Does this work without connecting an account? No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors Every tool and price: https://corespeed.io/catalog/timely ## Related pages - [Approval gates for AI agent tool actions](https://corespeed.io/solutions/agent-approvals): Set approval policies for writes through CoreSpeed. Review held tool actions while your team keeps using its preferred agents. - [Harvest for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/harvest): Ask your agent where last week's hours went and which Harvest project is near its budget. Logging time stays a separate step. - [Shared agent tools and controls for teams](https://corespeed.io/solutions/teams): Manage shared connections, approval policies, and tool usage for teams working across Claude Code, Codex, and other MCP clients. ## Sources - Connectors: https://corespeed.io/docs/connectors - Timely API documentation: https://developer.timely.com/ Reviewed 2026-11-10. ## Links - Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md) - All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md) - Documentation: https://corespeed.io/docs - Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)