Aller au contenu

Check My Tools

Audit the current environment to verify all required MCPs and CLI tools are installed for a Bricks engineer.

Required tools

Name Type Why Docs Auth / Install
Datadog MCP Monitor logs, traces, incidents, dashboards from IDE https://docs.datadoghq.com/bits_ai/mcp_server/setup/ API Key + App Key
Postgres MCP Direct SQL queries on any PG instance (staging/dev), inspect schemas https://github.com/modelcontextprotocol/servers/tree/main/src/postgres Connection string (env var)
Neon Postgres MCP Neon-managed DB access, serverless branching https://neon.tech/docs/ai/mcp-server OAuth (Neon account)
Playwright MCP Browser automation, E2E testing, visual validation https://github.com/microsoft/playwright-mcp None (local)
Figma MCP Design-to-code, fetch design tokens, screenshots https://github.com/nichochar/figma-mcp OAuth (Figma account)
Linear MCP Issue tracking, sprint management, ticket updates https://linear.app/docs/mcp OAuth (Linear account)
Notion MCP Access internal docs, knowledge base, specs https://www.notion.com/help/mcp OAuth (Notion account)
Slack MCP Read threads, search messages, post updates https://api.slack.com/mcp OAuth (Slack workspace)
bricks-intel MCP Monorepo index — components, hooks, routes, stores Project-local (.mcp.json.example) None (local)
GitHub CLI (gh) CLI PR creation, issue management, repo operations https://cli.github.com/manual/ brew install gh

How to audit

Check the following sources and report a status for each tool:

MCP servers

Paths like .cursor/settings.json and .cursor/mcp.json are relative to the workspace root (where .cursor/ lives in this monorepo), not under a single app package (e.g. not projects/front-mobile-app).

  1. Cursor plugins — read .cursor/settings.json and check plugins object for each MCP
  2. Cursor MCP servers — read .cursor/mcp.json for manually configured servers
  3. Claude Code MCPs — check available deferred tools (prefixed mcp__) in the current session
  4. Project MCP — read .mcp.json or .mcp.json.example for project-level servers (bricks-intel)
  5. Cursor (optional) — if a plugin is enabled but tools do not appear, check MCP connection in Cursor settings or ~/.cursor/projects/<workspace-folder-hash>/mcps/ for loaded server folders

CLI tools

  1. Run which gh to check GitHub CLI is installed
  2. Run gh auth status to check authentication

Output format

Report a table with a single Cursor / Claude column reflecting the environment you are running in:

| Tool           | Type | Available | Status |
|----------------|------|-----------|--------|
| Datadog        | MCP  | ✅        | OK     |
| Postgres       | MCP  | ❌        | MISSING — see https://github.com/modelcontextprotocol/servers/tree/main/src/postgres |
| ...            |      |           |        |
| GitHub CLI     | CLI  | ✅        | OK     |

For any missing tool, include the docs link from the table above so the engineer can install it immediately.