gpt-rag-mcp deployment.instructions.md

gpt-rag-mcp deployment.instructions.md is an instructions file for GitHub Copilot from Azure/gpt-rag-mcp. It costs 242 tokens per session, scanned A, original, MIT.

Operational instructions for deploying and running the GPT-RAG MCP service on Azure, Microsoft's cloud platform. They cover configuration, containers, builds, images, and deployment behavior.

In plain words
What is it for?
Use them when changing deployment scripts, Azure settings, container behavior, dependency locks, image publishing, or operator troubleshooting steps.
Why use it?
They prevent unsafe or inconsistent deployments and make failures, missing settings, and prerequisite problems visible.

Instructions file for GitHub Copilot

About the project

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.

Azure/gpt-rag-mcp · 22 stars · on GitHub

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/azure/gpt-rag-mcp/deployment
Clone the repo
git clone --depth 1 https://github.com/Azure/gpt-rag-mcp

Made for: GitHub Copilot.

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.

agentmods badge for gpt-rag-mcp deployment.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/azure/gpt-rag-mcp/deployment.svg)](https://agentmods.dev/instructions/azure/gpt-rag-mcp/deployment)
Your own site
<a href="https://agentmods.dev/instructions/azure/gpt-rag-mcp/deployment"><img src="https://agentmods.dev/badge/instructions/azure/gpt-rag-mcp/deployment.svg" alt="Measured on agentmods" height="20"></a>
Per session 242 This file is loaded in full into every session.
When invoked 242 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.00242 $0.00242
Opus 5 $0.00121 $0.00121
Sonnet 5 $0.00048 $0.00048
Haiku 4.5 $0.00024 $0.00024

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

Security

Grade A, and why

gpt-rag-mcp deployment.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 4d 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.

.github/instructions/deployment.instructions.md · 24 lines

What it actually says

MCP deployment and operations

  • Infrastructure provisioning belongs to Azure/GPT-RAG; preserve the guard that blocks azd provision and azd up here.
  • Keep PowerShell and POSIX deployment behavior aligned, including required settings, image naming, tagging, build fallback, and failure behavior.
  • Treat APP_CONFIG_ENDPOINT, label gpt-rag, and required App Configuration keys as operational contracts.
  • Quote paths and external input safely. Never echo secrets or private Azure validation environment and resource-group names.
  • Do not hide missing prerequisites or continue after failed login, configuration retrieval, build, push, or Container App update.
  • Keep the container on Python 3.12, non-privileged port 8080, and the committed uv project contract unless an intentional migration is approved.
  • Use a reproducible dependency lock and keep production-only installation behavior explicit.
  • Load documentation-consistency when deployment or operator steps change.
  • Production deployment and image publication require explicit human approval.
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. 4d ago First seen · 24 lines · 242 tokens per session scan A 66a26d5fcb0d

Subscribe to this mod's changes

gpt-rag-mcp deployment.instructions.md is an instructions file published in the GitHub repository Azure/gpt-rag-mcp (22 stars, last pushed 2d ago), licensed MIT. It adds 242 tokens to every session, about $0.0012 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.