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/qiskit/mcp-servers/agents-mdgit clone --depth 1 https://github.com/Qiskit/mcp-serversWrote 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/qiskit/mcp-servers/agents-md)<a href="https://agentmods.dev/instructions/qiskit/mcp-servers/agents-md"><img src="https://agentmods.dev/badge/instructions/qiskit/mcp-servers/agents-md.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.11715 | $0.11715 |
| Opus 5 | $0.05858 | $0.05858 |
| Sonnet 5 | $0.02343 | $0.02343 |
| Haiku 4.5 | $0.01171 | $0.01171 |
Grade A, and why
mcp-servers 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 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.
How it starts
The opening of the file, as written. The whole thing — 1,250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to AI development assistants when working with code in this repository.
Supported AI Assistants:
- IBM Bob
- Claude Code
- GitHub Copilot
- Cursor AI
- Windsurf
- Gemini CLI
- Any AI assistant with codebase context awareness
Project Overview
qiskit-mcp-servers is a collection of Model Context Protocol (MCP) servers that provide AI assistants, LLMs, and agents with seamless access to IBM Quantum services and Qiskit libraries for quantum computing development and research.
Core Purpose
- Enable AI systems to interact with quantum computing resources through Qiskit
- Provide production-ready MCP servers for quantum computing workflows
- Connect AI assistants to real quantum hardware automatically
- Simplify quantum circuit execution and job management
- Provide intelligent quantum code completion and assistance
- Enable AI-powered quantum circuit optimization and transpilation
Key Technologies
- Protocol: Model Context Protocol (MCP)
- Language: Python 3.10+ (3.11+ recommended)
- Framework: FastMCP (async-first MCP framework)
- Package Manager: uv (modern Python package manager with workspace support)
- Testing: pytest with async support, 65%+ coverage
- Code Quality: ruff (formatting + linting), mypy (type checking)
- Build System: hatchling with pyproject.toml
Architecture
Repository Structure
This is a monorepo using uv workspace containing five independent MCP servers:
qiskit-mcp-servers/
├── qiskit-mcp-server/ # Core Qiskit transpilation
├── qiskit-docs-mcp-server/ # Documentation retrieval
├── qiskit-ibm-runtime-mcp-server/ # IBM Quantum cloud services
├── qiskit-ibm-transpiler-mcp-server/ # AI-powered transpilation
├── qiskit-gym-mcp-server/ # RL-based circuit synthesis
├── .claude/skills/ # Claude Code skills
├── .github/ # GitHub templates and workflows
├── pyproject.toml # Workspace configuration & meta-package
├── mypy.ini # Shared mypy configuration
├── ruff.toml # Shared ruff configuration
├── README.md # Main repository documentation
├── PUBLISHING.md # PyPI publishing guide
├── CONTRIBUTING.md # Contribution guidelines
├── CODE_OF_CONDUCT.md # Community guidelines
└── LICENSE # Apache 2.0 license
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.
- 4d ago First seen · 1,250 lines · 11,715 tokens per session scan A 768bedb5c111
mcp-servers AGENTS.md is an instructions file published in the GitHub repository Qiskit/mcp-servers (39 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 11,715 tokens to every session, about $0.0586 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.