What is mcp-mayo CLAUDE.md?

Project-specific instructions for mcp-mayo, an MCP server that exposes the MAYO Apollo HR system's foundation, attendance, and payroll functions to AI tools.

Use it when setting up the server, checking its API connection, testing its tools, or changing its tool and connector modules.

It explains how to configure, run, test, and navigate the server without needing to know its architecture first.

How asgard-ai-platform/mcp-mayo configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to asgard-ai-platform/mcp-mayo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/asgard-ai-platform/mcp-mayo/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/asgard-ai-platform/mcp-mayo

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/asgard-ai-platform/mcp-mayo/claude-md/github.svg)](https://agentmods.dev/instructions/asgard-ai-platform/mcp-mayo/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/asgard-ai-platform/mcp-mayo/claude-md"><img src="https://agentmods.dev/badge/instructions/asgard-ai-platform/mcp-mayo/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/asgard-ai-platform/mcp-mayo/claude-md"><img src="https://agentmods.dev/badge/instructions/asgard-ai-platform/mcp-mayo/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 685 This file is loaded in full into every session.

When invoked 685 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00685	$0.00685
Opus 5	$0.00342	$0.00342
Sonnet 5	$0.00137	$0.00137
Haiku 4.5	$0.00068	$0.00068

Measured 9d ago against content hash 5c95dfbef69a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

mcp-mayo CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

mcp-mayo

Overview

MCP Server that wraps the MAYO Apollo HRM platform (Foundation, Attendance, Payroll) as AI-callable tools over stdio JSON-RPC 2.0. Part of the Asgard open-source ecosystem.

Setup

uv sync
cp .env.example .env   # then set MAYO_API_KEY

Run

uv run --env-file .env python mcp_server.py

Test

uv run --env-file .env python scripts/auth/test_connection.py   # probes FD / PT / PY
uv run --env-file .env python tests/test_all_tools.py           # every registered tool

Architecture

stdio (JSON-RPC 2.0)
  → mcp_server.py                     entry point; imports tool modules
    → app.py                          FastMCP("mcp-mayo") singleton
      → tools/
          foundation_tools.py           15 FD wrappers (pre-linkup-be)
          attendance_tools.py           8 PT wrappers (pre-pt-be)
          payroll_tools.py              5 PY wrappers (pre-py-be)
          semantic_tools.py             5 higher-level compositions
        → connectors/rest_client.py     retry + MayoAPIError
          → auth/api_key.py             hrmlicense header from MAYO_API_KEY
            → config/settings.py        BASE_URLS + ENDPOINTS (keyed by domain)

Key patterns

Single auth credential — MAYO_API_KEY is sent on the hrmlicense header for all three domains
Endpoint keys carry their domain — ENDPOINTS[key] = (domain, path) so get_url resolves to the right base URL without tool code needing to know
Date conversion in the tool layer — callers pass ISO, tools/_util.py converts to MAYO's format before the connector fires
Two-layer tool surface — thin raw wrappers for completeness + semantic composites for AI ergonomics
Known-broken upstream endpoints stay exposed — wrappers are marked KNOWN ISSUE: in docstrings so they work as soon as MAYO fixes the server

Adding a new tool

Register the endpoint in config/settings.py under ENDPOINTS with its domain
Add the tool function to the matching tools/*_tools.py, decorated with @mcp.tool() and typed via Pydantic Field()
Use _val() from tools/_util.py for every optional parameter to avoid the FieldInfo pitfall
Route through api_get / api_post from connectors/rest_client.py — never call requests directly
If you created a brand new tool module, add its import to mcp_server.py
Add an E2E case to tests/test_all_tools.py

Read the full file on GitHub · 67 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 67 lines · 685 tokens per session scan A 5c95dfbef69a

Subscribe to this mod's changes

mcp-mayo CLAUDE.md is an instructions file published in the GitHub repository asgard-ai-platform/mcp-mayo (0 stars, last pushed 24d ago), licensed MIT. It adds 685 tokens to every session, about $0.0034 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

ai-tools apollo attendance hr hrm human-resources

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

mcp-mayo: Instructions file for Claude Code