mcp-server AGENTS.md

A set of project instructions for Harness.io's MCP server, a service that lets an AI agent work with many kinds of resources through defined commands. It explains the server's commands, structure, logging, development workflow, and testing.

In plain words
What is it for?
Use it when developing, building, testing, documenting, starting, or diagnosing this TypeScript MCP server.
Why use it?
It gives the agent the project-specific details needed to work with the server correctly instead of guessing how its commands and codebase fit together.

Instructions file for CodexOpenCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/harness/mcp-server/agents-md
Clone the repo
git clone --depth 1 https://github.com/harness/mcp-server

Made for: Codex, OpenCode.

Per session 1,942 This file is loaded in full into every session.
When invoked 1,942 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.01942 $0.01942
Opus 5 $0.00971 $0.00971
Sonnet 5 $0.00388 $0.00388
Haiku 4.5 $0.00194 $0.00194

Measured 2d ago against content hash f85d0feb36c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mcp-server AGENTS.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 2d 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.

AGENTS.md · 162 lines

How it starts

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

AGENTS.md — Harness.io MCP Server

Registry-based MCP server: 11 consolidated tools (harness_list, harness_get, harness_create, harness_update, harness_delete, harness_execute, harness_search, harness_describe, harness_diagnose, harness_status, harness_schema) dispatching across 219+ resource types. TypeScript (Node.js 20+), ESM, pnpm, Zod v4.


Commands

pnpm install           # install deps
pnpm build             # tsc → build/
pnpm dev               # tsc --watch
pnpm typecheck         # tsc --noEmit
pnpm test              # vitest run (118 test files, 2510 tests, ~9s)
pnpm standards:check   # run coding-standards and structural validation tests
pnpm start             # stdio transport (requires HARNESS_API_KEY)
pnpm start:http        # HTTP transport (node build/index.js http)
pnpm inspect           # MCP Inspector against stdio build
pnpm docs:generate     # generate docs from build/ — run pnpm build first
pnpm docs:check        # CI check (reads build/); stale build = wrong count and CI fail

Project Structure

src/
├── index.ts            # Entrypoint — stdio/HTTP transport setup
├── config.ts           # Env var validation (Zod); see .env.example for all vars
├── registry/
│   ├── index.ts        # Core dispatch (~50K) — ResourceDefinition, EndpointSpec
│   ├── types.ts        # Registry types: ResourceDefinition, EndpointSpec, OperationPolicy
│   ├── extractors.ts   # Response shape extractors for all resource types
│   ├── scope-utils.ts  # Scope resolution utilities
│   └── toolsets/       # 41 declarative toolset definition files (pure data — add new resources here)
├── tools/              # 11 consolidated tool handlers
├── prompts/            # ~33 prompt templates (one per workflow)
├── resources/          # MCP resources (pipeline YAML, execution summary)
├── client/
│   └── harness-client.ts  # HTTP client — auth, retry, pagination
├── data/               # Example data and JSON schemas for entity validation
├── search/             # Cross-resource keyword search
├── audit/              # Audit manager
└── utils/              # Errors, logger, elicitation, deep-links, body normalizer

Read the full file on GitHub · 162 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.

  1. 2d ago First seen · 162 lines · 1,942 tokens per session scan A f85d0feb36c6

Subscribe to this mod's changes

mcp-server AGENTS.md is an instructions file published in the GitHub repository harness/mcp-server (93 stars, last pushed 2d ago), licensed MIT. It adds 1,942 tokens to every session, about $0.0097 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-30.