regulatory_landscape — Copernicus Dataspace MCP Prompt
regulatory_landscape
is one of 12 prompts on the
Copernicus Dataspace
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke regulatory_landscape from your client
- Claude Code Copernicus Dataspace Prompt/regulatory_landscape run in your project directory
- Claude Desktop Copernicus Dataspace Prompt/regulatory_landscape ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Copernicus Dataspace Prompt/regulatory_landscape ~/.cursor/mcp.json
- VS Code Copernicus Dataspace Prompt/regulatory_landscape .vscode/mcp.json
- Zed Copernicus Dataspace Prompt/regulatory_landscape ~/.config/zed/settings.json
- Windsurf Copernicus Dataspace Prompt/regulatory_landscape ~/.codeium/windsurf/mcp_config.json
- Cline Copernicus Dataspace Prompt/regulatory_landscape ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Copernicus Dataspace Prompt/regulatory_landscape ~/.gemini/settings.json
- Grok Copernicus Dataspace Prompt/regulatory_landscape .mcp.json (in your project root)
- ChatGPT Copernicus Dataspace Prompt/regulatory_landscape Settings → Connectors → Advanced → Developer mode
- Claude.ai Copernicus Dataspace Prompt/regulatory_landscape Settings → Connectors → Add custom connector
- LangChain Copernicus Dataspace Prompt/regulatory_landscape pip install langchain-mcp-adapters
Other prompts on this server
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.