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