Skip to main content

The #1 agentic semantic tool search: 91.6% first-try accuracy on S1 Search Bench Explore Tool Discovery

Live 63 Actions

Kenjo MCP Server
for AI Agents

Connect your AI agent to StackOne's Kenjo MCP server and give it 63 MCP tools out of the box. Auth, tool execution, and security all managed.

Kenjo logo
Kenjo MCP Server
Built by StackOne StackOne
DrataGPLocalyzeFlipMindtoolsScreenloop

Coverage

63 Agent Actions

Create, read, update, and delete across Kenjo — and extend your agent's capabilities with custom actions.

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your Kenjo MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every Kenjo tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every Kenjo call.

Tools Discovery →

What is the Kenjo MCP Server?

A Kenjo MCP server lets AI agents read and write Kenjo data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's Kenjo MCP server ships with 63 pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, observability, and agent execution runtime. Connect it from MCP clients like Claude Desktop, Claude Code, Cursor, Goose, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

All Kenjo MCP Tools

Every action from Kenjo's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.

Employees

  • Create Employee

    Create a new employee

  • List Employees

    Get a list of all employees

  • Get Employee

    Get a specific employee by ID

Employee Accounts

  • List Employee Accounts

    Get a list of employee account sections

  • Update Employee Account

    Update the account section of an employee

Employee Personals

  • List Employee Personals

    Get a list of employee personal sections

  • Update Employee Personal

    Update the personal section of an employee

Employee Works

  • List Employee Works

    Get a list of employee work sections

  • Update Employee Work

    Update the work section of an employee

Employee Financials

  • List Employee Financials

    Get a list of employee financial sections

  • Update Employee Financial

    Update the financial section of an employee

Employee Homes

  • List Employee Homes

    Get a list of employee home sections

  • Update Employee Home

    Update the home section of an employee

Departments

  • Create Department

    Create a new department

  • List Departments

    Get a list of departments

  • Get Department

    Get a specific department by ID

  • Update Department

    Update a department

  • Delete Department

    Delete a department

Offices

  • Create Office

    Create a new office

  • List Offices

    Get a list of offices

  • Get Office

    Get a specific office by ID

  • Update Office

    Update an office

  • Delete Office

    Delete an office

Teams

  • Create Team

    Create a new team

  • List Teams

    Get a list of teams

  • Get Team

    Get a specific team by ID

  • Update Team

    Update a team

  • Delete Team

    Delete a team

Areas

  • Create Area

    Create a new area

  • List Areas

    Get a list of areas

  • Get Area

    Get a specific area by ID

  • Update Area

    Update an area

  • Delete Area

    Delete an area

Calendars

  • List Calendars

    Get a list of calendars

  • Get Calendar

    Get a specific calendar by ID

Attendances

  • Create Attendance

    Create a new attendance entry

  • List Attendances

    Get a list of attendance entries

  • Get Attendance

    Get a specific attendance entry by ID

  • Update Attendance

    Update an attendance entry

  • Delete Attendance

    Delete an attendance entry

Other (23)

  • Create Processed Time Off Request

    Create a pre-approved (processed) time off request

  • List Employee Addresses

    Get a list of employee address sections

  • List Employee Emergencies

    Get a list of employee emergency contact sections

  • List User Accounts

    Get a combined list of all employees with account, personal, and work data

  • List Companies

    Get a list of companies

  • List Custom Fields

    Get a list of custom fields

  • List Time Off Requests

    Get a list of time off requests

  • List Time Off Types

    Get a list of time off types

  • Get Time Off Balance Status

    Get time off balance status for an employee and type

  • List Attendance Categories

    Get a list of attendance categories

  • List Attendance Expected Time

    Get expected working time per employee for a date range

  • List Compensation Contracts

    Get a list of employment contracts

  • List Compensation Contract Types

    Get a list of contract types

  • List Compensation Salaries

    Get a list of salaries

  • List Additional Payments

    Get a list of additional payments

  • List Additional Payment Types

    Get a list of additional payment types

  • List Company Documents

    Get a list of company documents

  • Update Employee Address

    Update the address section of an employee

  • Update Employee Emergency

    Update the emergency contact section of an employee

  • Set Time Off Balance

    Set time off balance for an employee

  • Activate Employee

    Send activation email to an employee

  • Deactivate Employee

    Deactivate an employee

  • Track Attendance

    Track attendance time for an employee

Kenjo AI Agent Use Cases

Connect your AI agent to Kenjo and help your team scale the HR operations they run by hand today.

Employee Onboarding

Use StackOne to connect your AI agent to your HRIS, identity management, and LMS to automate employee onboarding.

View
WorkdayBambooHRPersonioHiBobGustoRipplingOkta360Learning
HR Policy Q&A Chatbot

Use StackOne to connect your AI agent to your HRIS, knowledge base, and messaging tools to automate HR policy Q&A.

View
WorkdayBambooHRPersonioHiBobGustoRipplingSharePointConfluence
Employee Offboarding

Use StackOne to connect your AI agent to your HRIS, identity management, and ITSM to automate employee offboarding and deprovisioning.

View
WorkdayBambooHRPersonioOktaServiceNowRipplingGustoJira

Set Up Your Kenjo MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to Kenjo in under 10 lines of code.

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

Check More HRIS / HCM MCP Servers

Kenjo MCP Server FAQ

Does StackOne have a Kenjo MCP server?
Yes. StackOne offers a hosted Kenjo MCP server with 63 pre-built actions, and every action is tested and QA'd by StackOne. Connect it to Claude, Cursor, and any other MCP client, or to any agent framework through the AI Action SDK. It ships with managed agent authentication, prompt injection defense, and tool discovery with server-side execution that preserve your agent's context window and keep reasoning performance.
Kenjo MCP server vs direct API integration — what's the difference?
A Kenjo MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling Kenjo. A Kenjo MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling Kenjo at runtime. StackOne provides both.
How does Kenjo authentication work for AI agents?
Kenjo authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Kenjo account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are Kenjo MCP tools vulnerable to prompt injection?
Yes — Kenjo MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a Kenjo agent and how do I avoid it?
Context bloat happens when Kenjo tool schemas and API responses eat your Kenjo agent's memory, preventing it from reasoning effectively. A single Kenjo query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my Kenjo agent can access?
Yes — you can limit which actions your Kenjo agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my Kenjo MCP server?
Yes — you can create custom agent actions for your Kenjo MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Kenjo's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Kenjo MCP server?
Skip a Kenjo MCP server if your integration is purely software-to-software — direct Kenjo API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call Kenjo actions at runtime.
What AI frameworks and AI clients does the StackOne Kenjo MCP server support?
The StackOne Kenjo MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.