SmartHR MCP Server

Created By
TomoyaGotoa year ago
Overview

What is SmartHR MCP Server?

SmartHR MCP Server is a server that implements the Model Context Protocol (MCP) for the SmartHR API, allowing users to manage employee, department, position, employment type, and grade information.

How to use SmartHR MCP Server?

  1. Clone or download the repository.
  2. Set up the environment variables in a .env file.
  3. Configure claud_desktop_config.json to include the contents of smarthr_mcp_server.json.
  4. Restart Claude for Desktop.

Key features of SmartHR MCP Server?

  • Integration with SmartHR API for managing HR data.
  • Supports various functions for creating, deleting, and updating employee and department information.
  • Provides a structured way to interact with HR data through MCP.

Use cases of SmartHR MCP Server?

  1. Managing employee records in SmartHR.
  2. Automating HR processes through API calls.
  3. Integrating HR data with other applications using MCP.

FAQ from SmartHR MCP Server?

  • What is the purpose of the SmartHR MCP Server?

It serves as a bridge between the SmartHR API and MCP tools, facilitating HR data management.

  • Is there a license for using SmartHR MCP Server?

Yes, it is licensed under the MIT license.

  • What programming language is used for SmartHR MCP Server?

The server is implemented in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
TomoyaGoto
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

37 minutes ago