HR FLARE

com.hrflarePublished by hrflare.comOfficial publisherv1.0.0Updated Nov 5, 2026

HR for small teams: leave, attendance, expenses, payslips and team data. Acts as you, in your role.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote HR MCP server for small teams that lets an assistant work with leave, attendance, expenses, payslips and team data on your behalf.

What you can do
  • Work with leave, attendance, expenses, payslips and team data for a small team.
  • The server acts as you, in your own role, so the assistant sees and does what your HR account is allowed to.
  • No individual tools are documented, so the exact actions available are not described in the listing.
When to use it
Useful when you run HR for a small team and want an assistant to handle everyday leave, attendance, expense and payslip questions or updates without switching to the HR web app.
Requirements
A remote endpoint at hrflare.com reached over streamable HTTP. OAuth sign-in is required; no environment variables or headers are declared. An HR FLARE account with the appropriate role is needed.
Before you install
The server acts as you in your role, so anything the assistant does carries your permissions and may change leave, attendance, expense or payslip records. It handles personal and payroll data about team members, which is sent to the service. Review what it can write before connecting.

Installation

In SourceWeft

  1. Open HR FLARE in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.hrflare%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "hr-flare": {
      "type": "http",
      "url": "https://hrflare.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 5, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.