Leave Management MCP Server
by rshinde02
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_HOST | Yes | Database host (e.g., localhost). | |
| DB_NAME | Yes | Database name (e.g., leave_management). | |
| DB_PORT | Yes | Database port (e.g., 5433). | |
| DB_USER | Yes | Database user (e.g., postgres). | |
| FLASK_APP | Yes | Flask application entry point (e.g., run.py). | |
| FLASK_ENV | Yes | Flask environment (e.g., development). | |
| DB_PASSWORD | Yes | Database password. |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rshinde02/leave_management'
If you have feedback or need assistance with the MCP directory API, please join our Discord server