# Your HR records. Answers without the hunt. Source: https://corespeed.io/integrations/bamboohr Connect BambooHR to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent reads the employee directory, who is out, time-off requests and saved reports, and answers people questions. It acts as the BambooHR user who owns the API key, sees only the employees and fields that user can, and changing a record is a separate call. ## 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 BambooHR after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up ## Know who is out. Plan the cover Ask your agent who is away and which requests still need a decision. It reads BambooHR with your own user's permissions. You ask your agent: "Check BambooHR for who is out next week and which time-off requests are still waiting. Draft a coverage note for the team leads. Do not approve or deny anything." It calls CoreSpeed: - `bamboohr__get_whos_out`: ok, 388 ms - `bamboohr__list_time_off_requests`: ok, 452 ms It reads from: BambooHR. ### Coverage note: Next week, covered. Three people are out next week. Thursday is thin in Design, and one request still needs a decision. **Out next week** - Reid, Monday to Wednesday. - Mira, Thursday. **Needs a decision** - Dylan asked for Thursday and Friday. Two designers would be out on Thursday. _Illustrative example · Fictional data · No request approved or denied_ All connectors: https://corespeed.io/docs/connectors ## People questions, answered from BambooHR Requests you can make once BambooHR is connected. The data is fictional. ### See who is out Next week · who is out · Time off at a glance - Out: 3 people across 2 teams - Overlap: Two designers on Thursday - From the employees your user can see ### Hold the approval for a person A time-off decision · Approvals - Request: Dylan, Thursday and Friday - Rule: Ask before changing an HR record - Waiting for you Full example: https://corespeed.io/solutions/agent-approvals (Markdown: https://corespeed.io/solutions/agent-approvals.md) ### Read a saved report Headcount by department · A report you already keep - Report: Headcount by department - Change: Engineering up two this quarter - No record changed ## 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 BambooHR**: 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 employee data can the agent see? Only what the BambooHR user behind the API key can see. BambooHR applies that user's permissions to every employee and field. ### Can the agent approve time off or edit a record? Only if that user can. Approving a request or editing an employee is a separate tool call, and approvals can hold it for a person. How approvals work: https://corespeed.io/docs/approvals ### Does this replace BambooHR? No. BambooHR stays your system of record. CoreSpeed lets the agent you already use read it and draft the answer. ### 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/bamboohr ## 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. - [Ashby for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/ashby): Bring your Ashby jobs, candidates and interviews into your agent. Get a pipeline summary without changing a stage. - [App integrations for Claude Code, Codex, and Cursor](https://corespeed.io/integrations): Connect Gmail, Slack, Notion, GitHub, and more to Claude Code, Codex, Cursor, and other MCP clients. Manage private and shared connections. ## Sources - Connectors: https://corespeed.io/docs/connectors - BambooHR API: getting started: https://documentation.bamboohr.com/docs/getting-started 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)