Run OSINTNova investigations from your AI assistant

Claude web, Desktop and Cowork use a connector added in Claude’s settings. A chat prompt can guide you through this required step. Access depends on your plan and workspace permissions.

1. In Claude web, Desktop or Cowork, open Settings (or Customize) › Connectors.
2. On an individual plan, select Add custom connector, name it OSINTNova and paste the server address. On Team or Enterprise, an owner first adds it in Organization settings › Connectors; members then select that OSINTNova connector.
3. Select Connect, then sign in and approve Claude in the window that opens. Enable the connector in your chat; start a new session if its tools are not available.

Help me connect Claude web, Desktop or Cowork to OSINTNova at https://app.osintnova.com/mcp using its remote custom connector. For an individual plan, guide me to Settings or Customize > Connectors > Add custom connector, enter OSINTNova and this server URL, then Connect. On Team or Enterprise, an owner must first add it in Organization settings > Connectors; members then connect to that existing connector. If my plan or workspace permissions block setup, explain the specific limitation. This account connector requires Claude's settings flow; do not claim a chat prompt installs it. Do not edit claude_desktop_config.json or install Claude Code or a bridge inside a Cowork sandbox. After I approve the browser sign-in, help me enable the connector and start a new session if needed.

Use the client's own OAuth flow. If it gives you an authorization URL, open that exact URL in my default browser or a new tab in my existing browser using available browser controls. Keep any login process and callback listener running until I finish. Let me sign in and approve access myself. Never invent an authorization URL or use the connection-management page as a substitute.

Preserve my other servers, settings and approval controls. Do not ask me to paste passwords, API keys, access tokens or refresh tokens into chat. If this chat cannot access the persistent client configuration or complete its browser callback, explain the limitation and give me only the required manual step; do not configure an unrelated sandbox.

After authorization, discover the OSINTNova tools and call get_usage and get_command_guide without running an investigation or spending credits. Only say the connection is ready after a real authenticated tool response. If a reload or new chat is needed to load tools, tell me to do that and repeat this verification there; configuration or login success alone is not proof.

Official Claude setup guide

ChatGPT on the web requires adding the server as a custom plugin. Availability depends on your account and workspace permissions.

1. Open ChatGPT Plugins, select +, then Add custom MCP server.
2. Name it OSINTNova, paste the server address and choose OAuth. Review the warning and select Create as a plugin.
3. Install the plugin, complete browser sign-in when prompted, then select OSINTNova with @ in a chat. If your workspace restricts custom plugins, ask its administrator to enable access.

Help me connect ChatGPT on the web to OSINTNova at https://app.osintnova.com/mcp. The supported setup is ChatGPT Plugins at https://chatgpt.com/plugins > + > Add custom MCP server. Help me enter the name OSINTNova, this server URL and OAuth authentication, review the warning, create the plugin, install it and complete browser sign-in. I must complete the plugin setup in ChatGPT; do not claim that writing a local Codex configuration or posting a URL installs a hosted ChatGPT plugin. If workspace permissions prevent setup, explain the exact restriction. Once installed, help me select OSINTNova with @ in a chat.

Use the client's own OAuth flow. If it gives you an authorization URL, open that exact URL in my default browser or a new tab in my existing browser using available browser controls. Keep any login process and callback listener running until I finish. Let me sign in and approve access myself. Never invent an authorization URL or use the connection-management page as a substitute.

Preserve my other servers, settings and approval controls. Do not ask me to paste passwords, API keys, access tokens or refresh tokens into chat. If this chat cannot access the persistent client configuration or complete its browser callback, explain the limitation and give me only the required manual step; do not configure an unrelated sandbox.

After authorization, discover the OSINTNova tools and call get_usage and get_command_guide without running an investigation or spending credits. Only say the connection is ready after a real authenticated tool response. If a reload or new chat is needed to load tools, tell me to do that and repeat this verification there; configuration or login success alone is not proof.

Official ChatGPT setup guide

The agent can add the server and launch browser sign-in with the local Claude Code CLI. Older versions may require Authenticate from /mcp.

Connect this local Claude Code host to OSINTNova at https://app.osintnova.com/mcp using its native HTTP MCP transport and OAuth. Inspect claude mcp get osintnova and reuse a matching entry. If absent, run claude mcp add --transport http --scope user osintnova https://app.osintnova.com/mcp yourself. Preserve other servers; ask before replacing a conflicting entry. Check the installed CLI's help and, if supported, run claude mcp login osintnova in an interactive terminal to launch browser sign-in. If this version lacks that command, give me the short fallback: enter /mcp in Claude Code, select osintnova, then Authenticate. Do not run slash commands in a shell. A headless claude -p or Agent SDK run cannot complete this interactive login.

Use the client's own OAuth flow. If it gives you an authorization URL, open that exact URL in my default browser or a new tab in my existing browser using available browser controls. Keep any login process and callback listener running until I finish. Let me sign in and approve access myself. Never invent an authorization URL or use the connection-management page as a substitute.

Preserve my other servers, settings and approval controls. Do not ask me to paste passwords, API keys, access tokens or refresh tokens into chat. If this chat cannot access the persistent client configuration or complete its browser callback, explain the limitation and give me only the required manual step; do not configure an unrelated sandbox.

After authorization, discover the OSINTNova tools and call get_usage and get_command_guide without running an investigation or spending credits. Only say the connection is ready after a real authenticated tool response. If a reload or new chat is needed to load tools, tell me to do that and repeat this verification there; configuration or login success alone is not proof.

Official Claude Code setup guide

Cursor’s agent can add the configuration and use Cursor CLI for browser sign-in when installed. Otherwise, select Connect in Cursor.

Connect this local Cursor installation to OSINTNova at https://app.osintnova.com/mcp using native remote HTTP MCP and OAuth. Inspect ~/.cursor/mcp.json and the current project's .cursor/mcp.json for an existing osintnova entry. Reuse a matching entry; ask before changing a conflicting one. If absent, merge "osintnova": {"url": "https://app.osintnova.com/mcp"} into mcpServers in ~/.cursor/mcp.json, preserving every other entry and taking a backup before editing. If Cursor CLI is already installed on this host and its help supports it, run agent mcp login osintnova to launch browser sign-in. Confirm this is Cursor's CLI before running it. Otherwise, give me the short fallback: Cursor Settings > Tools & MCP > osintnova > Connect. Restart Cursor if it has not loaded the edited configuration. Do not install a bridge or authenticate an unrelated CLI.

Use the client's own OAuth flow. If it gives you an authorization URL, open that exact URL in my default browser or a new tab in my existing browser using available browser controls. Keep any login process and callback listener running until I finish. Let me sign in and approve access myself. Never invent an authorization URL or use the connection-management page as a substitute.

Preserve my other servers, settings and approval controls. Do not ask me to paste passwords, API keys, access tokens or refresh tokens into chat. If this chat cannot access the persistent client configuration or complete its browser callback, explain the limitation and give me only the required manual step; do not configure an unrelated sandbox.

After authorization, discover the OSINTNova tools and call get_usage and get_command_guide without running an investigation or spending credits. Only say the connection is ready after a real authenticated tool response. If a reload or new chat is needed to load tools, tell me to do that and repeat this verification there; configuration or login success alone is not proof.

{
  "mcpServers": {
    "osintnova": { "url": "https://app.osintnova.com/mcp" }
  }
}

Official Cursor setup guide

Copilot in agent mode can configure your workspace. VS Code may ask you to trust, start or authenticate the server.

Connect this VS Code workspace to OSINTNova at https://app.osintnova.com/mcp using Copilot agent mode and native HTTP MCP with OAuth. Inspect the workspace and active user profile's MCP configuration for an existing osintnova entry. Reuse a matching entry; ask before replacing a conflicting entry. If absent and the local VS Code CLI is available, run code --add-mcp with the JSON argument {"name":"osintnova","type":"http","url":"https://app.osintnova.com/mcp"}, quoted correctly for this shell. Otherwise merge "osintnova": {"type": "http", "url": "https://app.osintnova.com/mcp"} into servers in .vscode/mcp.json, preserving other servers, inputs and settings and taking a backup before editing. Use VS Code's MCP: List Servers controls to start osintnova and launch OAuth sign-in. Let me accept the server trust prompt. If those editor controls are unavailable to you, give me only the necessary Start or Authenticate step. Respect workspace and organization MCP policies and ensure OSINTNova tools are enabled in Copilot Chat.

Use the client's own OAuth flow. If it gives you an authorization URL, open that exact URL in my default browser or a new tab in my existing browser using available browser controls. Keep any login process and callback listener running until I finish. Let me sign in and approve access myself. Never invent an authorization URL or use the connection-management page as a substitute.

Preserve my other servers, settings and approval controls. Do not ask me to paste passwords, API keys, access tokens or refresh tokens into chat. If this chat cannot access the persistent client configuration or complete its browser callback, explain the limitation and give me only the required manual step; do not configure an unrelated sandbox.

After authorization, discover the OSINTNova tools and call get_usage and get_command_guide without running an investigation or spending credits. Only say the connection is ready after a real authenticated tool response. If a reload or new chat is needed to load tools, tell me to do that and repeat this verification there; configuration or login success alone is not proof.

{
  "servers": {
    "osintnova": { "type": "http", "url": "https://app.osintnova.com/mcp" }
  }
}

Official VS Code setup guide

This is for Gemini CLI on your computer. Its agent can add the server; browser sign-in uses the CLI’s /mcp auth command.

Connect this local Gemini CLI host to OSINTNova at https://app.osintnova.com/mcp using Streamable HTTP and OAuth. Inspect ~/.gemini/settings.json and the project's .gemini/settings.json for an existing osintnova entry. Reuse a matching entry; ask before replacing a conflicting one. If absent, run gemini mcp add --scope user --transport http osintnova https://app.osintnova.com/mcp using the installed CLI. If that command is unavailable, merge "osintnova": {"httpUrl": "https://app.osintnova.com/mcp"} into mcpServers in ~/.gemini/settings.json, preserving all other settings and taking a backup before editing. Enter /mcp reload in Gemini CLI to load the server, then /mcp auth osintnova to launch browser authorization. If you cannot operate interactive slash commands, tell me those required commands to enter. Do not run them in a shell or claim this configures the Gemini website. Browser OAuth needs access to the CLI host's localhost callback; a remote or headless container may require a local session.

Use the client's own OAuth flow. If it gives you an authorization URL, open that exact URL in my default browser or a new tab in my existing browser using available browser controls. Keep any login process and callback listener running until I finish. Let me sign in and approve access myself. Never invent an authorization URL or use the connection-management page as a substitute.

Preserve my other servers, settings and approval controls. Do not ask me to paste passwords, API keys, access tokens or refresh tokens into chat. If this chat cannot access the persistent client configuration or complete its browser callback, explain the limitation and give me only the required manual step; do not configure an unrelated sandbox.

After authorization, discover the OSINTNova tools and call get_usage and get_command_guide without running an investigation or spending credits. Only say the connection is ready after a real authenticated tool response. If a reload or new chat is needed to load tools, tell me to do that and repeat this verification there; configuration or login success alone is not proof.

{
  "mcpServers": {
    "osintnova": { "httpUrl": "https://app.osintnova.com/mcp" }
  }
}

Official Gemini CLI setup guide

Support depends on the client running your AI model. It needs remote Streamable HTTP and OAuth.

Connect the AI client running this chat to OSINTNova at https://app.osintnova.com/mcp. First identify this client's documented support for remote Streamable HTTP MCP and OAuth. If you can access its persistent host configuration, use the native setup mechanism and preserve existing settings. Otherwise guide me through the shortest supported connector-settings path. Do not assume the model's name proves client compatibility, and do not install another client's CLI or a bridge as a substitute. If this client lacks the required transport or OAuth support, say so clearly and recommend a supported client.

Use the client's own OAuth flow. If it gives you an authorization URL, open that exact URL in my default browser or a new tab in my existing browser using available browser controls. Keep any login process and callback listener running until I finish. Let me sign in and approve access myself. Never invent an authorization URL or use the connection-management page as a substitute.

Preserve my other servers, settings and approval controls. Do not ask me to paste passwords, API keys, access tokens or refresh tokens into chat. If this chat cannot access the persistent client configuration or complete its browser callback, explain the limitation and give me only the required manual step; do not configure an unrelated sandbox.

After authorization, discover the OSINTNova tools and call get_usage and get_command_guide without running an investigation or spending credits. Only say the connection is ready after a real authenticated tool response. If a reload or new chat is needed to load tools, tell me to do that and repeat this verification there; configuration or login success alone is not proof.

1. Use any MCP client that supports remote servers over Streamable HTTP with OAuth sign-in.
2. Add the server address below. The client discovers sign-in automatically; no API key is needed.