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