teadata-mcp AGENTS.md

A repository guide for teadata-mcp, a Python server with a web interface and tools that other programs can connect to. It explains the project layout, commands, coding rules, and tests.

In plain words
What is it for?
Use it when developing, testing, linting, or running teadata-mcp. It covers the React and TypeScript frontend, Python backend, local development scripts, deployment setup, and test suite.
Why use it?
It gives an agent the project-specific information needed to make changes consistently and run the right checks. It reduces guesswork about how the frontend and backend fit together.

Instructions file for CodexOpenCode

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/adpena/teadata-mcp/agents-md
Clone the repo
git clone --depth 1 https://github.com/adpena/teadata-mcp

Made for: Codex, OpenCode.

Per session 598 This file is loaded in full into every session.
When invoked 598 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.00598 $0.00598
Opus 5 $0.00299 $0.00299
Sonnet 5 $0.00120 $0.00120
Haiku 4.5 $0.00060 $0.00060

Measured yesterday against content hash 356869c136de, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

teadata-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 yesterday.

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 · 35 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

  • src/teadata_mcp/: Python MCP server code (routing, business logic, SSE entry point).
  • frontend/: Vite + React + TypeScript UI; builds into static_dist/ for the backend to serve.
  • tests/: Pytest suite (test_*.py).
  • run_dev.sh, run_mcp.sh: local/dev helper scripts; Dockerfile for deployment.

Build, Test, and Development Commands

  • ./run_dev.sh: build frontend, sync Python deps via uv, run uvicorn (default port 8000, auto-selects next free port; override with --port).
  • Backend only: uv sync, then uv run uvicorn teadata_mcp.sse_server:app --reload --port 8000.
  • Frontend dev server: cd frontend && npm install --legacy-peer-deps && npm run dev.
  • Frontend build: cd frontend && npm run build (writes to static_dist/).
  • Frontend lint: cd frontend && npm run lint.
  • Cloudflare tunnel helper: ./run_mcp.sh (use -s to skip frontend build; default port 8000, auto-selects next free port; override with --port; requires cloudflared).
  • Performance/log bundle: ./share_perf_report.sh (writes logs/share_perf_report_*.txt and copies to clipboard).

Coding Style & Naming Conventions

  • Python: 4-space indent, type hints where practical, snake_case for modules/functions; keep server code under src/teadata_mcp/.
  • Frontend: 2-space indent in TS/TSX; components in PascalCase (e.g., CampusView.tsx), utilities/types in camelCase or types.ts.
  • Styling: Tailwind utility classes in className; keep new styles colocated with components.

Testing Guidelines

  • Framework: pytest in tests/; run with uv run pytest.
  • Naming: test_*.py and test_* functions.
  • Coverage: no explicit threshold; add tests for new tool routes or data engine behavior.

Commit & Pull Request Guidelines

  • Commit messages follow short, imperative summaries (e.g., "Add ...", "Document ...", "Fix ..."); keep scope in the body if needed.
  • PRs should include: a clear description, linked issue if applicable, test command(s) run, and screenshots/GIFs for UI changes.

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

  1. yesterday First seen · 35 lines · 598 tokens per session scan A 356869c136de

Subscribe to this mod's changes

teadata-mcp AGENTS.md is an instructions file published in the GitHub repository adpena/teadata-mcp (1 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 598 tokens to every session, about $0.0030 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-31.