X-HR MCP server using stdio transport
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"xhr-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# XHR MCP Server Python MCP server for X-HR tools. This package is intended to run as a stdio MCP server so external clients can launch it as a local subprocess and communicate through standard input/output. ## Transport This server uses MCP `stdio` transport. It is not intended to expose an HTTP MCP endpoint. MCP clients should start the package command directly and let the client manage the stdio session. ## Install From PyPI, once published: ```bash pip install xhr-mcp-server ``` Or run it without a persistent install: ```bash uvx xhr-mcp-server ``` For local development: ```bash uv sync ``` ## MCP Client Config Example stdio configuration: ```json { "mcpServers": { "xhr": { "command": "uvx", "args": ["xhr-mcp-server"] } } } ``` If the package is installed in the same environment as the MCP client: ```json { "mcpServers": { "xhr": { "command": "xhr-mcp-server", "args": [] } } } ``` ## Local Development Run from the repository root: ```bash uv run xhr-mcp-server ``` The installed package exposes the same command: ```bash xhr-mcp-server ``` ## Environment Common environment variables: ```bash LOG_LEVEL=DEBUG LOG_FORMAT=pretty API_BASE_URL=https://api.dev.x-hr.ai XHR_PAT= ``` `API_BASE_URL` defaults to `https://api.x-hr.co` when unset. For local testing, set it to the dev API URL shown above. `XHR_PAT` is optional. When present and the MCP request does not include an authorization header, script tools forward it as `authorization: Bearer <XHR_PAT>`. Script tools also use that authorization header to call `/v1/im/me` and fill `xhr-employee-id` and `xhr-company-id` when they are missing. ## Notes Database migrations, Alembic, SQLAlchemy, and Postgres are intentionally not part of this package.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.