BambooHR MCP

Created By
encoreshaoa year ago
A Model Context Protocol (MCP) library for BambooHR, built with Node.js and TypeScript.
Overview

What is BambooHR MCP?

BambooHR MCP is a Model Context Protocol (MCP) library designed for seamless interaction with the BambooHR API, built using Node.js and TypeScript.

How to use BambooHR MCP?

To use BambooHR MCP, clone the repository, install the dependencies, and set up your environment variables with your BambooHR API token, company domain, and employee ID. You can then import the library into your Node.js or TypeScript application and utilize its methods to interact with the BambooHR API.

Key features of BambooHR MCP?

  • TypeScript types for all models and API responses
  • Simple, promise-based API for all major BambooHR endpoints
  • Easy to extend and integrate into your own projects

Use cases of BambooHR MCP?

  1. Fetching employee directories and details.
  2. Submitting work hours for specific projects.
  3. Retrieving information about employees who are out on a given day.

FAQ from BambooHR MCP?

  • How do I create a BambooHR API token?

Log in to your BambooHR account, navigate to API Keys, and generate a new key.

  • What environment variables do I need?

You need BAMBOOHR_TOKEN, BAMBOOHR_COMPANY_DOMAIN, and BAMBOOHR_EMPLOYEE_ID.

  • Can I extend the library?

Yes! You can add new methods in the designated files and export them.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
encoreshao
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago