What is mcp AGENTS.md?

A set of project instructions for the Temporal Cortex MCP documentation repository. MCP is a standard way for AI tools to connect to external services and tools.

Use it when updating the repository, checking links, keeping version details consistent, or adding setup and integration examples.

It gives coding agents the project structure, build and test checks, coding conventions, and rules for adding examples. This reduces guesswork when changing the documentation.

How temporal-cortex/mcp configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to temporal-cortex/mcp. 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/temporal-cortex/mcp/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/temporal-cortex/mcp

Made for: Codex, OpenCode.

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/temporal-cortex/mcp/agents-md/github.svg)](https://agentmods.dev/instructions/temporal-cortex/mcp/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/temporal-cortex/mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/temporal-cortex/mcp/agents-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/temporal-cortex/mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/temporal-cortex/mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 538 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.00538	$0.00538
Opus 5.5	$0.00215	$0.00215
Sonnet 5.5	$0.00108	$0.00108
Haiku 4.5	$0.00054	$0.00054

Measured 2mo ago against content hash a25342ea9408, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mcp 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 2mo 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 · 48 lines

How it starts

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

Temporal Cortex MCP

Public documentation repo for the Temporal Cortex MCP server (@temporal-cortex/cortex-mcp). Source code is in a private repository — this repo contains user-facing docs, setup guides, integration examples, directory configs, and the Dockerfile.

Structure

README.md — Main user-facing docs (Q&A format: each section is a question)
CHANGELOG.md — Release history
docs/ — Setup guides (google-cloud-setup, outlook-setup, caldav-setup), tool reference, integration guides (CrewAI, OpenAI Agents SDK), architecture overview
examples/ — Integration examples: crewai/, langgraph/, openai-agents/, config snippets (claude-desktop.json, cursor.json, windsurf.json)
Dockerfile — Multi-stage build wrapping the npm binary
smithery.yaml — Smithery directory config
glama.json — Glama directory metadata (maintainers field only; Docker config is in Glama dashboard)
.mcp/server.json — MCP Registry metadata
assets/ — Icons and logos

Build & Test

No build system — this is a docs-only repo. To verify changes:

npx markdown-link-check README.md   # check links

Ensure version numbers match across README.md, Dockerfile, and smithery.yaml.

Conventions

Pin npm version (@temporal-cortex/[email protected]) in Dockerfile, smithery.yaml, and .mcp/server.json
Do NOT pin npm versions in user-facing docs — always use @temporal-cortex/cortex-mcp (latest)
Keep tool counts (18), layer numbers (0-4), and tool lists in sync with the source
README uses Q&A format: each ## section is a question starting with "How", "What", "Can"
No pricing or business strategy content (public repo)

Adding Examples

Follow the pattern in examples/crewai/:

README.md with prerequisites, quick start, file descriptions
.env.example with required environment variables
requirements.txt for Python dependencies
Both Local Mode (stdio) and Platform Mode (HTTP) variants where applicable

Boundaries

Always: verify version numbers match across README, Dockerfile, smithery.yaml after version bumps
Ask first: changing tool descriptions, parameter schemas, or layer assignments
Never: include API keys, secrets, or pricing information

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

2mo ago First seen · 48 lines · 538 tokens per session scan A a25342ea9408

Subscribe to this mod's changes

mcp AGENTS.md is an instructions file published in the GitHub repository temporal-cortex/mcp (13 stars, last pushed 2mo ago), licensed MIT. It adds 538 tokens to every session, about $0.0022 per session on Opus 5.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.

Building agents LLM Writing and docs ai booking calendar google-calendar mcp

mcp AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
mcp AGENTS.mdtemporal-cortex/mcp	Instructions file	13	2mo ago	MIT	A	538	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

mcp: Instructions file for Codex