Prismhr Mcp

Please install the `prismhr-mcp` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Clone the repository** — The README's install path runs the server from a local checkout directory.
- **Configure PrismHR credentials** — Set up PrismHR authentication using either 1Password CLI or direct environment variables before starting the server.

Optional prerequisites:
- Install uv — Install the uv Python package/project runner used to sync dependencies and launch the server. Run: `uv sync --extra dev`
- Optional: Install and sign in to 1Password CLI — Required only if you choose the recommended 1Password credential path. The item must contain fields labeled username and password, and may optionally include peoId. Run: `op signin`

Canonical MCP server config (stdio transport):
- command: `uv`
- args: ["run","--directory","<path-to-prismhr-mcp>","prismhr-mcp"]
- optional environment variables:
  - `PRISMHR_MCP_ENVIRONMENT`: PrismHR environment to target. UAT is the safe default; production requires an additional opt-in flag. (example: `uat`)
  - `PRISMHR_MCP_USERNAME`: PrismHR API username when using direct environment-variable authentication. (example: `<your-api-username>`)
  - `PRISMHR_MCP_PASSWORD`: PrismHR API password when using direct environment-variable authentication. (example: `<your-password>`)
  - `PRISMHR_MCP_PEO_ID`: PrismHR tenant/PEO ID. Tenant-specific and different between UAT and production. Optional in the README because it may come from the 1Password item. (example: `<your-peo-id>`)
  - `PRISMHR_MCP_ONEPASSWORD_VAULT`: 1Password vault name containing the PrismHR credential item. Use this with the 1Password authentication path. (example: `<your-1password-vault>`)
  - `PRISMHR_MCP_ONEPASSWORD_ITEM_PRISMHR`: 1Password item name for PrismHR credentials. The item should expose username and password fields, and may optionally include peoId. (example: `<your-1password-item-name>`)
  - `PRISMHR_MCP_ALLOW_PROD`: Required only when targeting production PrismHR. Must be set to true to allow prod connections. (example: `true`)

Note: Authentication requires choosing one credential path: either direct PrismHR credentials (username/password, optionally peo_id) or 1Password CLI-backed credentials (vault/item). The README only documents a local-repo uv run path; no PyPI/packaged stdio launch command is provided, so the canonical config uses the repository checkout.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.