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/teradata/teradata-mcp-server/claude-mdgit clone --depth 1 https://github.com/Teradata/teradata-mcp-serverWrote 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/teradata/teradata-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/teradata/teradata-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/teradata/teradata-mcp-server/claude-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.01596 | $0.01596 |
| Opus 5 | $0.00798 | $0.00798 |
| Sonnet 5 | $0.00319 | $0.00319 |
| Haiku 4.5 | $0.00160 | $0.00160 |
Grade A, and why
teradata-mcp-server CLAUDE.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.
Copies of this mod
1 near-identical copy found in the catalogue:
- teradata-mcp-server-stc CLAUDE.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
Teradata MCP Server — a Model Context Protocol server for interacting with Teradata databases. Built on FastMCP, distributed on PyPI as teradata-mcp-server. Python 3.11+.
Build & Development Commands
# Install dependencies
uv sync
# Install with optional modules
uv sync --extra fs # Feature Store (teradataml)
uv sync --extra tdvs # Vector Store (teradatagenai)
uv sync --extra bar # Backup & Restore
uv sync --extra dev # Dev tools (ruff, mypy)
# Run the server locally (stdio mode)
uv run teradata-mcp-server --database_uri "teradata://user:pass@host:1025/db"
# Run with specific profile and transport
uv run teradata-mcp-server --profile dba --mcp_transport streamable-http --mcp_port 8001
# Lint
uv run ruff check src/
uv run ruff format --check src/
# Type check
uv run mypy src/
# Run tests (requires a live Teradata connection)
export DATABASE_URI="teradata://user:pass@host:1025/database"
uv run python tests/integration/run_mcp_tests.py "uv run teradata-mcp-server"
# Docker
docker compose up teradata-mcp-server
Architecture
Request Flow
server.py— CLI argument parsing, callscreate_mcp_app()app.py— FastMCP app factory. Creates the MCP instance, registers tools/prompts/resources based on profile, configures middleware. Ateradata_lifespanasync context manager (passed toFastMCP(lifespan=...)) owns theTDConnpool lifecycle: creates the pool at server startup and callsengine.dispose()in itsfinallyblock on shutdown.middleware.py—RequestContextMiddlewareextracts per-request headers, auth, and session info. Sets Teradata QueryBand for tracing- Tool handlers — Plain sync functions (
handle_*) intools/subdirectories. Wrapped to async viaasyncio.to_thread
Profile-Based Module Loading
Tools are organized into domain modules under src/teradata_mcp_server/tools/:
- base/ — Core queries (readQuery, tableList, columnDescription, etc.)
- dba/ — Administration & monitoring
- sec/ — Security & permissions
- rag/ — Retrieval-augmented generation workflows
- fs/ — Feature Store (optional, requires teradataml)
- tdvs/ — Vector Store operations
- bar/ — Backup & restore (optional)
- chat/ — Chat completion
- qlty/ — Data quality / EDA
- plot/ — Visualization (charts)
- sql_opt/ — SQL optimization
- tmpl/ — Template tools
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 · 115 lines · 1,596 tokens per session scan A d32e48c12cbd
teradata-mcp-server CLAUDE.md is an instructions file published in the GitHub repository Teradata/teradata-mcp-server (55 stars, last pushed today), licensed MIT. It adds 1,596 tokens to every session, about $0.0080 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.