Azure/gpt-rag-mcp is a Python server that exposes GPT-RAG capabilities through the Model Context Protocol. It is deployed with Azure resources and consumed by GPT-RAG through its MCP strategy, while the catalogue provides instructions, skills, and agents for operating it.
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.
npx agentmods add instructions/azure/gpt-rag-mcp/releasegit clone --depth 1 https://github.com/Azure/gpt-rag-mcpWrote 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.
[](https://agentmods.dev/instructions/azure/gpt-rag-mcp/release)<a href="https://agentmods.dev/instructions/azure/gpt-rag-mcp/release"><img src="https://agentmods.dev/badge/instructions/azure/gpt-rag-mcp/release.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00222 | $0.00222 |
| Opus 5 | $0.00111 | $0.00111 |
| Sonnet 5 | $0.00044 | $0.00044 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
gpt-rag-mcp release.instructions.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 5d 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.
What it actually says
Component release surfaces
- Follow
.github/copilot-instructions.mdand loadcomponent-release. - Use
release/x.y.zfor the branch andvX.Y.Zfor the changelog heading, Git tag, and GitHub Release title. - Keep
VERSIONandproject.versioninpyproject.tomlequal toX.Y.Z. - Regenerate
uv.lockfrom the exact committedpyproject.toml; do not hand-edit dependency resolution. - Keep Keep a Changelog categories and semantic-version impact aligned with observable behavior.
- Validate the exact release commit and identify the corresponding
Azure/GPT-RAGcomponent pin when coordinated platform work is required. - Never infer versions from stale prose or a previous release.
- Never publish private Azure validation names, credentials, tokens, or personal data.
- A tag, GitHub Release, package, image, or deployment requires explicit human approval.
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.
- 5d ago First seen · 22 lines · 222 tokens per session scan A 1f36efa4d478
gpt-rag-mcp release.instructions.md is an instructions file published in the GitHub repository Azure/gpt-rag-mcp (22 stars, last pushed 3d ago), licensed MIT. It adds 222 tokens to every session, about $0.0011 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.
Other instructions, from other repositories
planning-with-files AGENTS.md
AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
OpenMicro AGENTS.md
Instructions for stephenleo/OpenMicro, covering openmicro — project conventions and releases.
ai-usagebar CLAUDE.md
Claude Code instructions for akitaonrails/ai-usagebar, covering claude.md, release checklist — must do all of these, hard invariants — never break these, secret-discipline rules (learned the hard way) and live api smoke discipline.
living-manual CLAUDE.md
Instructions for dougstanford/living-manual, covering living-manual, start of every session, how work lands — non-negotiable, user's manual (living-manual) and releasing.
yandex360-mcp CLAUDE.md
Claude Code instructions for pa1ch/yandex360-mcp, covering claude.md — гайд для ассистента, как устроен релиз (всё автоматически по тегу), процедура релиза (шаги ассистента), гарды and архитектура (кратко).