Leave Management MCP Server
Exposes leave management APIs through MCP, enabling users to manage employee leave requests, approvals, and balances via natural language. It bridges Claude Desktop to a Flask backend with PostgreSQL persistence.
README
Leave Management — Flask + PostgreSQL
Backend for the leave-management application. Flask exposes REST APIs, SQLAlchemy handles persistence, and PostgreSQL stores employees and leave requests.
Architecture
Claude Desktop
|
| MCP / stdio
v
MCP Server
|
| HTTP
v
Flask API
|
| SQLAlchemy
v
PostgreSQL :5433
Prerequisites
- Windows
- Python 3.12+
- PostgreSQL 17+
- PowerShell
1. Create Project and Virtual Environment
mkdir C:\ai_workspace\leave_management
cd C:\ai_workspace\leave_management
python -m venv .venv
.\.venv\Scripts\Activate.ps1
If PowerShell blocks activation:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
.\.venv\Scripts\Activate.ps1
2. Install Dependencies
python -m pip install Flask Flask-SQLAlchemy Flask-Migrate psycopg2-binary python-dotenv
python -m pip freeze > requirements.txt
For an existing checkout:
.\.venv\Scripts\Activate.ps1
python -m pip install -r requirements.txt
3. PostgreSQL Setup
Check PostgreSQL:
psql --version
Get-Service *postgres*
This project uses PostgreSQL on port 5433.
Connect:
psql -h localhost -p 5433 -U postgres
Create the database:
CREATE DATABASE leave_management;
4. Configure .env
Create .env in the project root:
FLASK_APP=run.py
FLASK_ENV=development
DB_HOST=localhost
DB_PORT=5433
DB_NAME=leave_management
DB_USER=postgres
DB_PASSWORD=YOUR_POSTGRES_PASSWORD
Do not commit .env.
Recommended .gitignore:
.venv/
.env
__pycache__/
*.pyc
5. Test Database Connection
db_test.py:
from sqlalchemy import create_engine, text
from dotenv import load_dotenv
import os
load_dotenv()
url = (
f"postgresql+psycopg2://"
f"{os.getenv('DB_USER')}:"
f"{os.getenv('DB_PASSWORD')}@"
f"{os.getenv('DB_HOST')}:"
f"{os.getenv('DB_PORT')}/"
f"{os.getenv('DB_NAME')}"
)
engine = create_engine(url)
with engine.connect() as connection:
result = connection.execute(text("SELECT version()"))
print("Database connection successful!")
print(result.scalar())
Run:
python db_test.py
6. Flask-Migrate
Initialize once:
flask --app run.py db init
Create/apply migrations:
flask --app run.py db migrate -m "Create employees table"
flask --app run.py db upgrade
After adding the leave-request model:
flask --app run.py db migrate -m "Create leave requests table"
flask --app run.py db upgrade
7. Sample Employees
Connect:
psql -h localhost -p 5433 -U postgres -d leave_management
Insert:
INSERT INTO employees
(employee_id, name, email, department, designation, leave_balance, created_at, updated_at)
VALUES
('EMP001', 'Rohit Shinde', 'rohit@example.com', 'Engineering', 'Team Lead', 20, NOW(), NOW()),
('EMP002', 'Amit Sharma', 'amit@example.com', 'HR', 'HR Manager', 15, NOW(), NOW()),
('EMP003', 'Priya Patel', 'priya@example.com', 'Marketing', 'Marketing Executive', 10, NOW(), NOW());
Verify:
SELECT employee_id, name, department, leave_balance
FROM employees;
8. Run Flask
cd C:\ai_workspace\leave_management
.\.venv\Scripts\Activate.ps1
python run.py
Expected:
Running on http://127.0.0.1:5000
9. Test Employee API
Invoke-RestMethod `
-Uri "http://127.0.0.1:5000/employees/EMP003" `
-Method GET
Expected data includes:
employee_id : EMP003
name : Priya Patel
department : Marketing
leave_balance : 10
10. Test Leave API
Apply two days:
$body = @{
employee_id = "EMP003"
start_date = "2026-08-10"
end_date = "2026-08-11"
days = 2
reason = "Personal leave"
leave_type = "Personal"
} | ConvertTo-Json
Invoke-RestMethod `
-Uri "http://127.0.0.1:5000/leave/apply" `
-Method POST `
-ContentType "application/json" `
-Body $body
The request should initially have:
status : Pending
Check pending requests:
Invoke-RestMethod `
-Uri "http://127.0.0.1:5000/leave/pending" `
-Method GET
Approve using the returned request_id:
$body = @{
approved_by = "EMP001"
} | ConvertTo-Json
Invoke-RestMethod `
-Uri "http://127.0.0.1:5000/leave/request/YOUR_REQUEST_ID/approve" `
-Method POST `
-ContentType "application/json" `
-Body $body
Verify:
Invoke-RestMethod `
-Uri "http://127.0.0.1:5000/employees/EMP003" `
-Method GET
After approving 2 days:
leave_balance : 8
API Summary
| Method | Endpoint | Purpose |
|---|---|---|
| GET | /employees |
List employees |
| GET | /employees/<employee_id> |
Employee details |
| POST | /employees |
Create employee |
| PUT | /employees/<employee_id> |
Update employee |
| DELETE | /employees/<employee_id> |
Delete employee |
| POST | /leave/apply |
Apply for leave |
| GET | /leave/<employee_id> |
Employee leave history |
| GET | /leave/pending |
Pending leave requests |
| GET | /leave/request/<request_id> |
Leave request details |
| POST | /leave/request/<request_id>/approve |
Approve leave |
| POST | /leave/request/<request_id>/reject |
Reject leave |
Database Verification
SELECT employee_id, name, leave_balance
FROM employees
WHERE employee_id = 'EMP003';
SELECT request_id, employee_id, days, status
FROM leave_requests
WHERE employee_id = 'EMP003';
Design Principle
The Flask application owns business logic and database access. The MCP server calls Flask APIs instead of directly manipulating PostgreSQL:
MCP → Flask Services → SQLAlchemy → PostgreSQL
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。