# MCP And External Lookup Guidance

This file is generated by Shrey Junior.
Profile: `{{profileName}}`
Detected project type: `{{projectType}}`

Use it to decide when external lookup is justified and when repo inspection should win.

Recommended pack pointer:
- `core-pack`: repo inspection, git, local validation, issue/PR context.
- `research-pack`: docs lookup and careful external research.
- `web-qa-pack`: browser/UI verification when the repo actually has a web surface.
- `aws-pack`: AWS-specific repos only.
- `ios-pack`: iOS/macOS work when Xcode-capable tooling is actually available.
- `android-pack`: Android work should still rely primarily on repo-local build/test/tooling; do not imply Android MCP parity.

## Capability Categories

- Docs lookup: useful for version-sensitive framework or provider behavior.
- Web search and fetch: useful when repo-local docs are insufficient and the task depends on current external behavior.
- Browser automation: useful for UI validation, reproduction, or live workflow checks.
- DB inspection: useful for schema, migration, or data-boundary work when safe and policy-allowed.
- Memory and context tools: useful for continuity and synthesis, not as a substitute for repo-local files.

## Tool Reality

- Codex and Claude local workflows may be able to use MCP or tool integrations directly when the environment exposes them.
- Copilot should treat MCP notes as routing context, not as a promise that it can invoke those tools itself.
- Cloud-hosted runtimes may not see machine-global MCP config even when repo-local guidance mentions capability categories.
- GitHub MCP-style tooling is usually strongest for repo, PR, issue, and workflow context.
- Playwright-style tooling is strongest for browser/UI verification, not for deciding repo truth.
- AWS-specific tooling should not be suggested for non-AWS repos.

## Search Discipline

- Inspect repo code, repo-local contract files, and promoted canonical docs first.
- Use docs lookup when framework, cloud, browser, or library behavior may have changed.
- Use web search when the question is current, external, or not answered by the repo.
- Avoid external lookup for narrow local edits, repo-owned docs changes, or when the latest packet or checkpoint already answers the question.

## Policy Reminder

- MCP use is policy-driven, not ad hoc.
- Capability availability does not mean approval.
- Repo authority and the active role still decide whether external lookup is appropriate.
