Connect
Optimize
Secure
Live 24 Actions
absence.io MCP Server
for AI Agents
Connect your AI agent to StackOne's absence.io MCP server and give it 24 MCP tools out of the box. Auth, tool execution, and security all managed.
absence.io MCP Server
Built by 
StackOne
StackOne 
Coverage
24 Agent Actions
Create, read, update, and delete across absence.io — and extend your agent's capabilities with custom actions.
Authentication
Agent Tool Authentication
Per-user OAuth in one call. Your absence.io MCP server gets session-scoped tokens with zero credentials stored on your infra.
Agent Auth →
Security
Agent Protection
Every absence.io 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 absence.io call.
Tools Discovery →What is the absence.io MCP Server?
A absence.io MCP server lets AI agents read and write absence.io data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's absence.io MCP server ships with 24 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 absence.io MCP Tools
Every action from absence.io's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.
Absences
- Create Absence
Create a new absence assigned to a user with a specific reason and approver.
- List Absences
List absences with optional MongoDB-style filtering, sorting, and relation resolution.
- Get Absence
Retrieve a single absence by its MongoDB ObjectId.
- Update Absence
Update an existing absence — only the fields supplied are changed.
Allowance Types
- List Allowance Types
List allowance types with optional MongoDB-style filtering, sorting, and pagination.
- Get Allowance Type
Retrieve a single allowance type by its MongoDB ObjectId.
Departments
- List Departments
List departments with optional MongoDB-style filtering, sorting, and pagination.
- Get Department
Retrieve a single department by its MongoDB ObjectId.
Holidays
- List Holidays
Retrieve holidays for a user or location within a date range, with optional filtering by company, day type, and mandatory-leave status.
Locations
- List Locations
List locations with optional MongoDB-style filtering, sorting, and pagination.
- Get Location
Retrieve a single location by its MongoDB ObjectId.
Reasons
- List Reasons
List absence reasons with optional MongoDB-style filtering, sorting, and pagination.
- Get Reason
Retrieve a single absence reason by its MongoDB ObjectId.
Teams
- List Teams
List teams with optional MongoDB-style filtering, sorting, and pagination.
- Get Team
Retrieve a single team by its MongoDB ObjectId.
Timespans
- Create Timespan
Create a new timespan (work or break entry) for a user.
- List Timespans
List timetracking entries with optional MongoDB-style filtering, sorting, and pagination.
- Get Timespan
Retrieve a single timespan by its MongoDB ObjectId.
- Update Timespan
Update an existing timespan — only the fields supplied are changed.
- Delete Timespan
Delete a timespan by its MongoDB ObjectId.
Users
- List Users
List users with optional MongoDB-style filtering, sorting, and pagination.
- Get User
Retrieve a single user by their MongoDB ObjectId.
- Update User
Update an existing user — only the fields supplied are changed.
Invite Users
- Invite User
Register a new user for the company; optionally send an invitation email.
absence.io AI Agent Use Cases
Connect your AI agent to absence.io 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 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 Employee Offboarding
Use StackOne to connect your AI agent to your HRIS, identity management, and ITSM to automate employee offboarding and deprovisioning.
ViewSet Up Your absence.io MCP Server in Minutes
One endpoint. Any framework. Your agent is talking to absence.io in under 10 lines of code.
Agent Frameworks
JSON{
"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 hr-workforce MCP Servers
Platform Resources
MCP Code Mode: Keeping Tool Responses Out of Agent Context
Anthropic's code_execution processes data already in context. Custom MCP code mode keeps raw tool responses in a sandbox. 14K tokens vs 500.
11 min
Comparing BM25, TF-IDF, and Hybrid Search for MCP Tool Discovery
Benchmarking BM25, TF-IDF, and hybrid search for MCP tool discovery across 916 tools. The 80/20 TF-IDF/BM25 hybrid hits 21% Top-1 accuracy in under 1ms.
10 min
Indirect Prompt Injection Defense for MCP Tools: A Technical Guide
MCP tools that read emails, CRM records, and tickets are indirect prompt injection vectors. Here's how we built a two-tier defense that scans tool results in ~11ms.
12 min
absence.io MCP Server FAQ
Does StackOne have a absence.io MCP server?
Yes. StackOne offers a hosted absence.io MCP server with 24 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.
absence.io MCP server vs direct API integration — what's the difference?
A absence.io MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling absence.io. A absence.io 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 absence.io at runtime. StackOne provides both.
How does absence.io authentication work for AI agents?
absence.io 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 absence.io account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via
origin_owner_id.Are absence.io MCP tools vulnerable to prompt injection?
Yes — absence.io 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 absence.io agent and how do I avoid it?
Context bloat happens when absence.io tool schemas and API responses eat your absence.io agent's memory, preventing it from reasoning effectively. A single absence.io 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 absence.io agent can access?
Yes — you can limit which actions your absence.io 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 absence.io MCP server?
Yes — you can create custom agent actions for your absence.io MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research absence.io's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a absence.io MCP server?
Skip a absence.io MCP server if your integration is purely software-to-software — direct absence.io 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 absence.io actions at runtime.
What AI frameworks and AI clients does the StackOne absence.io MCP server support?
The StackOne absence.io 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.