Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the Kenjo HR in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
Read Kenjo HR data: employees with names, job titles and reporting lines, companies, offices, departments and teams, time-off requests and types, attendance entries and recruiting positions. Read-only, through the Kenjo API v1.
Try asking
Example prompts for Kenjo HR
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Kenjo HR, paste your credentials, mint an MCP API key — done. No Docker, no
git clone, no local server.
Kenjo HR + Meta Muse
Read Kenjo HR data: employees with names, job titles and reporting lines, companies, offices, departments and teams, time-off requests and types, attendance entries and recruiting positions. Read-only, through the Kenjo API v1.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
KENJO_API_KEY
Step 1 — Get credentials
- API access is off by default: ask Kenjo support to have Customer Success enable it for your account.
- An admin opens Settings → Integrations → API and clicks Generate new API key. Copy the key at once, as Kenjo shows it only once (up to 5 keys per organisation).
- Employee data is always included; switch on attendance, time off and recruiting for the key if you want those tools. Put the key in
KENJO_API_KEY. - Start with
kenjo_list_employeesto find a person's_id, thenkenjo_get_employee. Turn ids into names withkenjo_list_companies,kenjo_list_offices,kenjo_list_departmentsandkenjo_list_teams.
The connector exchanges the key for a bearer token at POST /auth/login and renews it by itself; editing, regenerating or deleting the key in Kenjo invalidates its tokens. It calls the production API api.kenjo.io, so a sandbox key does not work. Nothing is written to Kenjo, and the financial section (bank and tax ids) is removed from employee records. Time-off requests take a range of at most 92 days, attendances at most 31; a 403 on those tools means the collection is not enabled for the key.
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Muse
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.
- In Muse, open Settings → Connectors and choose Add custom connector.
- Paste the MCP server URL
https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. - Muse opens the AnythingMCP sign-in page: sign in and approve access.
- In a chat, ask Muse for something that needs the
Kenjo HRtools.
You can also set it up from a chat, on the web, in the iOS and Android apps or in WhatsApp. Send Muse this message:
Create a Custom Connector for a new remote MCP server, then connect to it:
Name: AnythingMCP
Transport: remote streamable HTTP
URL: https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID
Auth: OAuth
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Muse connects from Meta's cloud, so localhost does not work.
Available tools
| Tool | What it does |
|---|---|
kenjo_list_employees | List all Kenjo employees with their _id, e-mail, first and last name, display name, job title, active status and company, office and… |
kenjo_get_employee | Get every section of one Kenjo employee: account (e-mail, active), personal (name, birthdate, nationality), work (job title, start date… |
kenjo_list_employee_accounts | List Kenjo employee accounts (_id, e-mail, external id, language, active status) |
kenjo_list_employee_work_details | List the work section of every employee: job title, start date, employee number, company, office, department, area and team ids, manager… |
kenjo_list_companies | List the companies (legal entities) set up in Kenjo with _id, name, city and country |
kenjo_list_departments | List the departments set up in Kenjo with _id and name |
kenjo_list_offices | List the office locations in Kenjo with _id, name, company id, holiday calendar id, street, postal code, city and country |
kenjo_list_teams | List the teams set up in Kenjo with _id and name |
kenjo_list_time_off_types | List the time-off types of the organisation (vacation, sick leave and so on) with _id and name |
kenjo_list_time_off_requests | List time-off requests in a date range of at most 92 days, with employee id, type id, policy, status, from/to, duration and per-day split |
kenjo_list_attendances | List attendance (worked time) entries of all employees in a date range of at most 31 days: employee id and e-mail, start and end time… |
kenjo_list_positions | List recruiting positions (job openings) with _id, job title, company, office and department ids, position type, status and job description |
FAQ
Where is Muse available? Meta currently offers Muse in the US and Canada, on the web, in the iOS and Android apps and in WhatsApp.
Does Meta review this connector? No. Meta doesn't review custom connectors. Muse sees only the tools you switched on for this MCP server in AnythingMCP, and you can disconnect it anytime under Settings → Connectors.
Next steps
Was this guide helpful?
