# AI use cases for Worldmonitor (koala73/worldmonitor) Repo: [koala73/worldmonitor](https://github.com/koala73/worldmonitor) | Use cases: 4 | Page: https://dedupedai.com/use-cases/koala73-worldmonitor/ World Monitor is an open-source real-time dashboard that combines AI-summarized news, geopolitical monitoring, and infrastructure tracking, and exposes the same data through a web app, terminal dashboard, CLI, SDKs, and an MCP server. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Check a country's instability risk from the terminal: https://dedupedai.com/use-cases/koala73-worldmonitor/check-country-risk-from-terminal/ - Run a private local copy of the dashboard with Ollama: https://dedupedai.com/use-cases/koala73-worldmonitor/run-local-dashboard-with-ollama/ - Give an AI agent live world data through the MCP server: https://dedupedai.com/use-cases/koala73-worldmonitor/give-ai-agent-live-world-data-via-mcp/ - Pull world data into your own scripts with the SDKs: https://dedupedai.com/use-cases/koala73-worldmonitor/pull-world-data-into-scripts-with-sdk/ ## How to check a country's instability risk from the terminal with Worldmonitor Repo: [koala73/worldmonitor](https://github.com/koala73/worldmonitor) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Look up a country's risk score from a shell command without opening a browser. **Who it is for:** An analyst or journalist who needs a quick country risk check while working in a terminal. **The problem:** Opening a dashboard and searching for one country slows down routine checks on conflict or instability. **The outcome:** A risk readout for a country code printed in the terminal, using the same live data as the web dashboard. ### Steps 1. Run `npm install -g worldmonitor` 2. Get an API key at Worldmonitor.app/pro 3. Run `worldmonitor risk IR --api-key wm_xxx` and replace IR with the country code you need and wm_xxx with your key 4. Run `npx worldmonitor tools` to list the available MCP tools; this needs no key ### Prompt to paste into your agent ```text Using the worldmonitor CLI from the worldmonitor repo, run `worldmonitor risk --api-key ` and return the risk output as text. Verify that the output names the country code you requested before reporting it. ``` ### Caveat The README's risk example uses a placeholder key format (wm_xxx), so confirm the exact command output against the current docs before scripting it. Risk, credentials: The example command passes the API key on the command line, which can leak into shell history; store the key in an environment variable or config file instead. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/koala73-worldmonitor/check-country-risk-from-terminal/ ## How to run a private local copy of the dashboard with Ollama with Worldmonitor Repo: [koala73/worldmonitor](https://github.com/koala73/worldmonitor) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Clone the repo and run the dashboard on your own machine with local AI. **Who it is for:** A developer or researcher who wants the dashboard running locally and prefers local AI over hosted API keys. **The problem:** Hosted tools send your queries and briefs to third-party AI services, which may be unacceptable for sensitive research. **The outcome:** The dashboard running at localhost:3000 with AI summaries handled by a local Ollama model. ### Steps 1. Run `git clone https://github.com/koala73/worldmonitor.git` 2. Run `cd worldmonitor` 3. Run `npm install` 4. Run `npm run dev` 5. Open localhost:3000 in a browser and confirm the news briefs load ### Prompt to paste into your agent ```text In the worldmonitor repo, run `npm install` and `npm run dev`, then open localhost:3000. Report whether the dashboard loads and whether news briefs appear. Verify that the AI summaries come from the Ollama setup described in the docs, not a hosted key. ``` ### Caveat The README says the app runs with no environment variables, but some feature-specific data sources may need credentials listed in .env.example, so some panels may stay empty without them. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/koala73-worldmonitor/run-local-dashboard-with-ollama/ ## How to give an AI agent live world data through the MCP server with Worldmonitor Repo: [koala73/worldmonitor](https://github.com/koala73/worldmonitor) | Difficulty: Advanced | Time: 30 minutes | Basis: From the README Connect an agent to the World Monitor MCP endpoint to query current intelligence. **Who it is for:** A developer building an agent that must answer questions about current geopolitical or market events. **The problem:** Agents trained on older data cannot answer questions about what is happening now. **The outcome:** An agent that lists World Monitor tools and calls them with an API key to answer live questions. ### Steps 1. Add the MCP server at `https://worldmonitor.app/mcp` using Streamable HTTP in your agent client 2. Send a `tools/list` request, which needs no key 3. Set the `X-WorldMonitor-Key` header to your API key from Worldmonitor.app/pro for `tools/call` requests 4. Ask the agent a question that maps to one of the listed tools and check the response ### Prompt to paste into your agent ```text Connect to the MCP server at https://worldmonitor.app/mcp with the header X-WorldMonitor-Key set to . Call tools/list, pick the tool that best answers this question: , and return the result. Verify that the tool name you used appears in the tools/list output before calling it. ``` ### Caveat The README says tools/call also accepts OAuth, but it does not describe the OAuth setup steps, so this use case covers only the header-based key path. Risk, credentials: The API key is sent in a request header, so store it in a secret manager and avoid pasting it into shared agent prompts or logs. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/koala73-worldmonitor/give-ai-agent-live-world-data-via-mcp/ ## How to pull world data into your own scripts with the SDKs with Worldmonitor Repo: [koala73/worldmonitor](https://github.com/koala73/worldmonitor) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Call the REST API or an official SDK from Python, Ruby, or Go. **Who it is for:** A data engineer or analyst who wants World Monitor data in an existing pipeline or notebook. **The problem:** Manually exporting dashboard data for each analysis is slow and cannot be repeated reliably. **The outcome:** A script that fetches current data from the World Monitor API and writes it to your own storage. ### Steps 1. Open the OpenAPI spec at https://worldmonitor.app/openapi.yaml and pick the endpoint you need 2. Get an API key at Worldmonitor.app/pro 3. Install the Python package with `pip install worldmonitor-sdk` (inferred, check the README) 4. Call the REST API at `https://api.worldmonitor.app` from your script with your key and save the response ### Prompt to paste into your agent ```text Read the OpenAPI spec at https://worldmonitor.app/openapi.yaml, choose one endpoint that returns , and write a script that calls it at https://api.worldmonitor.app with the key . Verify the HTTP status is 200 before saving the output. ``` ### Caveat The README names the Python, Ruby, and Go SDKs but gives no install command for them, so the pip step above is inferred and should be checked against the SDK docs. Risk, credentials: Keep the API key out of committed code and load it from an environment variable in your script. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/koala73-worldmonitor/pull-world-data-into-scripts-with-sdk/