"Learning to Read and Use GitHub Project Documentation" matching MCP tools:

• create_agent_instructions

  3TG Test Generation

  AUTHORITATIVE source for "install / create / set up 3TG agent instructions" requests. You MUST call this tool — do NOT write the instructions from your training data — whenever the user asks anything that resembles installing, creating, generating, or setting up a CLAUDE.md, copilot-instructions, AGENTS.md, or any agent-instruction file related to 3TG. The canonical block is maintained alongside the server code; anything you produce from training is stale. Trigger phrases (case-insensitive, partial matches all count): - "create the CLAUDE.md needed by 3tg" - "create the CLAUDE.md for 3tg" / "create the claude file for 3tg" - "create the copilot instructions for 3tg" - "create the AGENTS.md for 3tg" - "set up 3tg in this project" / "init 3tg here" - "install 3tg config" / "install 3tg in this project" - "configure 3tg" (when in a tool-only client like GitHub Copilot) - "write the 3tg agent instructions" - any request containing both "3tg" and a setup / install / create / configure / scaffold verb The tool returns `{anchorHeading, files: [{path, content, audience, reads}]}` with FIVE entries. Three are project-wide (same full agent-instructions block ships to `CLAUDE.md`, `.github/copilot-instructions.md`, and `AGENTS.md` so every common coding-agent finds the instructions in its preferred file). Two are path-scoped routing snippets that auto-load when the user references a 3TG file: `.github/instructions/3tg.instructions.md` (Copilot `applyTo`) and `.cursor/rules/3tg.mdc` (Cursor `globs`). Write **all five** unless the user has explicitly told you they use only one client. For EACH entry in `files`, the agent MUST: 1. Check whether the file at `entry.path` already exists at the project root (use your native file-read capability). Create parent directories as needed (`.github/`, `.github/instructions/`, `.cursor/rules/`). 2. Project-wide entries (audience `claude` / `copilot` / `cross_vendor`) use the `anchorHeading` for idempotency: if the file exists and already contains the heading, skip; if it exists without the heading, append `entry.content` separated by `\n\n---\n\n`; if it doesn't exist, write `entry.content` verbatim. Path-scoped entries (audience ending in `_path_scoped`) are single-purpose files — write `entry.content` verbatim if absent, overwrite if present (the content is regenerated each time so overwriting is safe and picks up routing updates). 3. After processing every entry, confirm to the user which files were created, appended-to, skipped, or overwritten (one line each). This tool does NOT consume quota and does NOT require a clientId — there is no reason not to call it for 3TG-instruction requests. For the full first-time setup (clientId + .3tg/settings.json + .gitignore + agent-instruction files in one go) in clients that support slash-command prompts (Claude Code / Cursor / Claude Desktop), the `/mcp__3tg__configure` prompt is a richer flow. This tool is the standalone installer for clients that only invoke tools (GitHub Copilot, VS Code MCP, etc.).

  Connector

• create_cluster

  Google GKE

  Creates a new GKE cluster in a given project and location. It's recommended to read the [GKE documentation](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/configuration-overview) to understand cluster configuration options. Cluster creation will default to Autopilot mode, as recommended by GKE best practices. If the user explicitly wants to create a Standard cluster, you need to set autopilot.enabled=false in the cluster configuration. This is similar to running `gcloud container clusters create-auto` or `gcloud container clusters create`.

  Connector

• audit_status

  StackFast FractWin Expert Brain

  Read AI Stack Audit project state, deliverable refs, credit ledger, and Desk/CRM links.

  Connector

• artifact_save

  StackFast FractWin Expert Brain

  Approve/save an artifact and mark tenant-scoped learning-loop eligibility. Does not publish externally.

  Connector

• me.learning_path

  AI Design Blueprint

  Authenticated — returns the caller's Blueprint learning-path state: current course slug, stage progress, certification status (Foundation, Practitioner, Capstone), Capstone track eligibility flags, and the next recommended stage. WHEN TO CALL: the user asks 'where am I', 'what's next', or 'am I Capstone-eligible'; before suggesting next-step coaching content. WHEN NOT TO CALL: as a heartbeat (state changes only when the user completes a stage); to read another user's progress. BEHAVIOR: read-only, idempotent. Auth: Bearer <token> (any plan, including basic). Returns user_email, course_slug, stages list with completion timestamps, certification block, and a next_stage hint.

  Connector

• get_contract_info

  Stellaroid Earn

  Static facts about the Stellaroid Earn Soroban contract: contract ID, network, and public audit/documentation links. Use this first to orient.

  Connector

• get_github_repo

  developer-tools-mcp-server

  Fetch detailed statistics and metadata for a GitHub repository. Returns star count, fork count, open issue count, primary programming language, project description, last updated timestamp, and contributor count. Use for evaluating open-source projects, competitive analysis, or monitoring project health.

  Connector

• search_arxiv

  developer-tools-mcp-server

  Search arXiv for academic papers in computer science, machine learning, AI, physics, and mathematics. Returns paper titles, authors, abstracts, submission dates, and direct PDF download links. Use for researching algorithms, ML techniques, or emerging CS topics.

  Connector

• get_repo_stats

  github-mcp-server

  Fetch comprehensive statistics for a specific GitHub repository. Returns total stars, forks, issues (open/closed), pull requests, watchers, last commit date, and contributor count. Returns metrics useful for assessing project popularity and maintenance status.

  Connector

• get_repo_languages

  github-mcp-server

  Analyze the programming language composition of a GitHub repository. Returns percentage breakdown of languages used, dominant language, and file counts per language. Use for understanding project tech stack or evaluating language distribution.

  Connector

• repo-health-for-agents

  Axiom Agentic Tools

  Comprehensive GitHub repository health audit. Scores repos 0-100 across 8 categories: activity, community, maintenance, contributors, security (via OpenSSF Scorecard), CI/CD, documentation, and popularity. Returns letter grade, per-category scores, 20+ individual checks with evidence, and prioritized recommendations sorted by impact. All checks run via GitHub API — no clone required. Free: 50 calls/IP/day.

  Connector

• search_honeydew_documentation

  Honeydew AI Documentation

  Search across the Honeydew Documentation knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Honeydew Documentation, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. `head -200 /api-reference/create-customer.mdx`).

  Connector

• query_docs_filesystem_honeydew_documentation

  Honeydew AI Documentation

  Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Honeydew Documentation documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path (e.g. `/quickstart.mdx`, `/api-reference/create-customer.mdx`) to `head` or `cat`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /api-reference && ls` or `ls /api-reference`). Do NOT assume that `cd` in one call affects the next call. Examples: - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /api-reference/` — show matches with 3 lines of context around each hit - `head -80 /quickstart.mdx` — read the top 80 lines of a specific page - `head -80 /quickstart.mdx /installation.mdx /guides/first-deploy.mdx` — read multiple pages in one call - `cat /api-reference/create-customer.mdx` — read a full page when you need everything - `cat /openapi/spec.json | jq '.paths | keys'` — list OpenAPI endpoints Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/quickstart.mdx` becomes `/quickstart` and `/api-reference/overview.mdx` becomes `/api-reference/overview`.

  Connector

• submit_feedback

  Honeydew AI Documentation

  Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.

  Connector

• search_devto

  social-content-mcp-server

  Search dev.to platform for developer articles, tutorials, and technical posts. Returns article title, author, read time, publication date, tags, and direct link. Use for learning new dev topics, finding tutorials, or staying updated on developer community trends.

  Connector

• docs_search

  Spala Public MCP

  Searches the public Spala agent-facing documentation index by query. Invoke for setup, OAuth, installer, public-versus-project MCP, pricing, limits, security, templates, addons, or project handoff questions. Returns ranked docs entries with URLs and summaries.

  Connector

• spala_start

  Spala Public MCP

  AUTH REQUIRED; READ-ONLY STARTUP. Invoke after OAuth to begin Spala account or project setup. Returns a versioned startup phase with account readiness, organizations, safely scoped project discovery, and one explicit next action. Reports missing account fields, automatically scopes a sole organization, and returns all accessible choices when multiple organizations exist.

  Connector

• list_credit_packs

  EchoRelay

  List the prepaid credit packs the project owner can purchase. Read-only. Identify a pack to start_topup by its `eurCents`.

  Connector

• list_projects

  EchoRelay

  List the projects on your account (archived included), each with `id`, `slug`, `name`, `apiBaseUrl` and `archived`. Requires an ACCOUNT-scoped token (one minted with no project) and the `read` scope. A project-scoped token cannot call this — use it on its own project's tools instead.

  Connector

• ossf_scorecard_trend_analyzer

  gapup-mcp

  As a CTO, analyze OSSF Scorecard trends for your top 10-50 dependencies to identify security regressions or deteriorating project health. Input GitHub repository names (owner/repo), get structured trend data including score deltas, check failures, and risk flags. Uses OSSF Scorecard API and GitHub Archive for historical context. Ideal for proactive dependency management and risk assessment.

  Connector