Returns a verified project brief so an agent can orient itself before reading more code.
DESCRIPTION
Start here on every unfamiliar repo. The output is compact on purpose: it gives you the stack, deployment shape, auth model, integrations, entry points, and high-value files without dumping the whole repository into context.
GOOD FIT
AVOID IT WHEN
| Name | Type | Required | Description |
|---|---|---|---|
| path | string | No | Absolute project path. If omitted, the active working directory is used. |
PATH PARAMETER
Use the absolute path to the project root on the machine where the code is available. In Cursor, VS Code, or Windsurf that usually means the workspace root you already have open. On a remote dev box, pass the absolute path on that remote machine. If the path does not exist or the service cannot access it, the tool returns an explicit error instead of guessing. Results are best when the folder is a real project root with .git or package.json. Private GitHub repos are not fetched automatically.
FAILURE BEHAVIOR
If the path does not exist or is not accessible, the tool returns a concrete retry instruction instead of a vague summary. If the folder is not a real project root, the context quality drops sharply because key markers like package.json, config files, and git metadata are missing.
{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "get_project_context", "arguments": { "path": "/Users/name/projects/zephex" } }}Stack: Next.js 16, React 19, TypeScript, Bun, ExpressAuth: Bearer API keys (hashed) plus dashboard session authHosting: Vercel for the public app, Render for the proxy, Supabase for dataKey files: dashboard/src/app/api/mcp/route.ts, src/lib/auth.ts, src/services/analyze-routes.tsIntegrations: Stripe, Upstash Redis, Supabase, SentryEnvironment variables: SUPABASE_URL, SUPABASE_ANON_KEY, STRIPE_SECRET_KEY, UPSTASH_REDIS_URLTOKEN EFFICIENCY
This tool usually returns about 400 to 700 tokens. Manually reading package.json, README, env examples, route entry points, auth helpers, and deployment config often costs 15,000 to 40,000 tokens, so this gives orientation at roughly 1 to 5 percent of the token cost.