environmental_risk — Dpla MCP Prompt

environmental_risk is one of 12 prompts on the Dpla MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke environmental_risk from your client

• Claude Code Dpla Prompt/environmental_risk run in your project directory
• Claude Desktop Dpla Prompt/environmental_risk ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Dpla Prompt/environmental_risk ~/.cursor/mcp.json
• VS Code Dpla Prompt/environmental_risk .vscode/mcp.json
• Zed Dpla Prompt/environmental_risk ~/.config/zed/settings.json
• Windsurf Dpla Prompt/environmental_risk ~/.codeium/windsurf/mcp_config.json
• Cline Dpla Prompt/environmental_risk ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Dpla Prompt/environmental_risk ~/.gemini/settings.json
• Grok Dpla Prompt/environmental_risk .mcp.json (in your project root)
• ChatGPT Dpla Prompt/environmental_risk Settings → Connectors → Advanced → Developer mode
• Claude.ai Dpla Prompt/environmental_risk Settings → Connectors → Add custom connector
• LangChain Dpla Prompt/environmental_risk pip install langchain-mcp-adapters

Other prompts on this server

• research_public_company
• drug_safety_profile
• trade_exposure
• housing_market_brief
• regulatory_landscape
• tool_chain_for_question
• property_research
• patent_due_diligence
• lobbying_activity
• financial_health_check
• agricultural_commodity_brief

Read from the server itself, by connecting to it and calling prompts/list on 25 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.