mcpField
H
human-standards

human-standards

Local
github.com/aklodhi98Developer Tools5Updated 8w ago

About human-standards

human-standards is an open reference library for product teams and AI tools, covering human factors, accessibility, usability, and implementation guidance. Its local, read-only MCP server uses bundled material without reading project files or contacting external services.

Key features

  1. 01Guidance on human factors, cognition, and accessibility
  2. 02Design patterns, implementation notes, and code examples
  3. 03Usability research methods and evaluation guidance
  4. 04Cited sources and supporting evidence
  5. 05Read-only search and heuristic tools

Use cases

  1. 01Find human-factors rationale for interface design
  2. 02Retrieve implementation guidance for design decisions
  3. 03Consult usability testing and evaluation methods
  4. 04Query standards and heuristics through MCP

MCP support

The local MCP server provides five read-only tools to search and retrieve standards, heuristics, and spatial-rhythm guidance. It uses a snapshot bundled with the npm package, communicates over standard input and output, and does not read project files.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"aklodhi98-human-standards": {
"command": "npx",
"args": [
"-y",
"@humanstandards/mcp-server"
]
}
}
}
Run commandnpx -y @humanstandards/mcp-server

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@humanstandards/mcp-server0.3.1

Tools

5

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
idenumYesHeuristic ID: H1 (Visibility of system status), H2 (Match between system and real world), H3 (User control and freedom), H4 (Consistency and standards), H5 (Error prevention), H6 (Recognition rather than recall), H7 (Flexibility and efficiency), H8 (Aesthetic and minimalist design), H9 (Help users recover from errors), H10 (Help and documentation)H1 | H2 | H3 | H4 | H5 | H6 | H7 | H8 | H9 | H10

Details

From the project README

Human Standards

Human factors research translated into practical design standards, implementation guidance, and read-only context for AI agents.

Explore the live library · Connect the MCP server · Read Study 001

Built with Starlight

Is Human Standards useful to you? Star the project on GitHub to save it for later and help other practitioners discover it. You can also watch the repository for future releases or join the public Discussions.

Study 001 is published as an exploratory coordinator-reviewed pilot. Directed MCP access improved the automated results but did not reliably remove obvious usability and accessibility problems. The planned independent review was not completed, and the missing human outcome is reported explicitly. Read the case study and evidence.

Why Human Standards exists

Product teams have access to extensive research on cognition, ergonomics, accessibility, usability, and human-computer interaction. Turning that evidence into a concrete design decision is still difficult—and AI-assisted product work makes the gap more visible.

Human Standards is an open-source reference library designed to make that knowledge easier to inspect and apply. People can browse the guidance directly. Compatible AI tools can retrieve the same material through a local, read-only MCP server.

The project does not claim to replace user research, accessibility testing, professional judgment, or the standards and studies it cites.

What is included

  • Human factors guidance — Cognition, perception, emotion, decision-making, ergonomics, accessibility, and social context
  • Design and implementation guidance — Interaction patterns, playbooks, code examples, and design-token constraints
  • Research methods — Usability testing, cognitive walkthroughs, metrics, and evaluation guidance
  • Evidence and references — Links to the standards, publications, and source material behind the guidance
  • Machine-readable access — Five read-only MCP tools for search, retrieval, heuristics, and relationship-first spatial-rhythm guidance
  • Open evaluation — Study protocols and evidence intended for independent review and reproducible analysis

Current status

Human Standards is actively developed and should be treated as a working reference library, not a finished or universally validated standard.

  • The documentation library is available at humanstandards.org.
  • The MCP server runs locally from the published npm package, uses bundled guidance, and does not write to projects or external services.
  • Study 001 is published as an exploratory pilot. Its protocol deviation, automated evidence, coordinator observations, condition mapping and missing independent-review outcome are public.
  • Gaps, corrections, competing evidence, and well-scoped contributions are welcome.

Use the documentation library

Start with Getting Started or browse the library by topic. Every page is designed to connect principles with practical decisions, implementation guidance, and primary or established sources where available.

To run the site locally:

git clone https://github.com/aklodhi98/humanstandards.git
cd humanstandards
npm ci
npm run dev

Open http://localhost:4321 to view the local site.

Use the MCP server

The MCP server exposes the library to compatible AI tools through five read-only tools:

  • search_standards
  • get_standard
  • get_heuristic
  • get_all_heuristics
  • get_spatial_rhythm

The MCP client runs the npm package; it is not an application dependency and does not become part of the project being built:

npx --yes @humanstandards/mcp-server

Configure a compatible MCP client to run that command:

{
  "mcpServers": {
    "human-standards": {
      "command": "npx",
      "args": ["--yes", "@humanstandards/mcp-server"]
    }
  }
}

The server communicates over standard input/output, reads no project files, opens no network port, and uses the Human Standards snapshot bundled with its package release. See the MCP setup guide for Codex, Claude Desktop, Claude Code, source-build, and verification instructions.

Project commands

CommandAction
npm ciInstall the documentation-site dependencies from the lockfile
npm run devStart the local site at localhost:4321
npm run buildBuild the production site to ./dist/
npm run checkBuild the site and validate internal links
npm run previewPreview the production build locally
npm run build --prefix human-standards-mcpCompile the MCP server
npm test --prefix human-standards-mcpRun the MCP server tests after it has been built

Contributing

Useful contributions include:

  • correcting inaccurate, ambiguous, or outdated guidance;
  • adding stronger primary or established sources;
  • improving examples and implementation details;
  • identifying missing contexts, limitations, or accessibility considerations;
  • reporting defects in the website, standards index, or MCP server.

Read CONTRIBUTING.md for the contribution workflow, evidence expectations, content structure, and local checks. Questions and early ideas can start in GitHub Discussions; concrete defects belong in Issues.

Licensing and attribution

Human Standards builds on work across human factors, cognitive psychology, HCI, UX, and accessibility. Source citations are included throughout the library, with broader starting points in the academic research references and standards and guidelines.

Built with Astro and Starlight. Maintained by AK Lodhi.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.