Skip to content
Back to search

chronulus-mcp

MCP Server for Chronulus AI Forecasting and Prediction Agents

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/chronulusai--chronulus-mcp/badge.svg)](/listings/chronulusai--chronulus-mcp)

HTML

<a href="/listings/chronulusai--chronulus-mcp"><img src="/api/listings/chronulusai--chronulus-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Install

Claude for Desktop is currently available on macOS and Windows.

Install Claude for Desktop [here](https://claude.ai/download)

Configuration

Follow the general instructions [here](https://modelcontextprotocol.io/quickstart/user) to configure the Claude desktop client.

You can find your Claude config at one of the following locations:

- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` - Windows: `%APPDATA%\Claude\claude_desktop_config.json`

Then choose one of the following methods that best suits your needs and add it to your `claude_desktop_config.json`

<details> <summary>Using pip</summary>

(Option 1) Install release from PyPI

pip install chronulus-mcp

(Option 2) Install from Github

git clone https://github.com/ChronulusAI/chronulus-mcp.git
cd chronulus-mcp
pip install .
{
  "mcpServers": {
    "chronulus-agents": {
      "command": "python",
      "args": ["-m", "chronulus_mcp"],
      "env": {
        "CHRONULUS_API_KEY": "<YOUR_CHRONULUS_API_KEY>"
      }
    }
  }
}

Note, if you get an error like "MCP chronulus-agents: spawn python ENOENT", then you most likely need to provide the absolute path to `python`. For example `/Library/Frameworks/Python.framework/Versions/3.11/bin/python3` instead of just `python`

</details>

<details> <summary>Using docker</summary>

Here we will build a docker image called 'chronulus-mcp' that we can reuse in our Claude config.

git clone https://github.com/ChronulusAI/chronulus-mcp.git
cd chronulus-mcp
 docker build . -t 'chronulus-mcp'

In your Claude config, be sure that the final argument matches the name you give to the docker image in the build command.

{
  "mcpServers": {
    "chronulus-agents": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "CHRONULUS_API_KEY", "chronulus-mcp"],
      "env": {
        "CHRONULUS_API_KEY": "<YOUR_CHRONULUS_API_KEY>"
      }
    }
  }
}

</details>

<details> <summary>Using uvx</summary>

`uvx` will pull the latest version of `chronulus-mcp` from the PyPI registry, install it, and then run it.

{
  "mcpServers": {
    "chronulus-agents": {
      "command": "uvx",
      "args": ["chronulus-mcp"],
      "env": {
        "CHRONULUS_API_KEY": "<YOUR_CHRONULUS_API_KEY>"
      }
    }
  }
}

Note, if you get an error like "MCP chronulus-agents: spawn uvx ENOENT", then you most likely need to either: 1. [install uv](https://docs.astral.sh/uv/getting-started/installation/) or 2. Provide the absolute path to `uvx`. For example `/Users/username/.local/bin/uvx` instead of just `uvx`

</details>

Additional Servers (Filesystem, Fetch, etc)

In our demo, we use third-party servers like [fetch](https://github.com/modelcontextprotocol/servers/tree/main/src/fetch) and [filesystem](https://github.com/modelcontextprotocol/servers/tree/main/src/filesystem).

For details on installing and configure third-party server, please reference the documentation provided by the server maintainer.

Below is an example of how to configure filesystem and fetch alongside Chronulus in your `claude_desktop_config.json`:

{
  "mcpServers": {
    "chronulus-agents": {
      "command": "uvx",
      "args": ["chronulus-mcp"],
      "env": {
        "CHRONULUS_API_KEY": "<YOUR_CHRONULUS_API_KEY>"
      }
    },
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/path/to/AIWorkspace"
      ]
    },
    "fetch": {
      "command": "uvx",
      "args": ["mcp-server-fetch"]
    }
  }
} 

Claude Preferences

To streamline your experience using Claude across multiple sets of tools, it is best to add your preferences to under Claude Settings.

You can upgrade your Claude preferences in a couple ways:

* From Claude Desktop: `Settings -> General -> Claude Settings -> Profile (tab)`

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 186 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <div align="center">
  2. <img width="150px" src="https://www.chronulus.com/brand-assets/chronulus-logo-blue-on-alpha-square.png" alt="Chronulus AI">
  3. <h1 align="center">MCP Server for Chronulus</h1>
  4. <h3 align="center">Chat with Chronulus AI Forecasting & Prediction Agents in Claude</h3>
  5. </div>
  6. ### Quickstart: Claude for Desktop
  7. #### Install
  8. Claude for Desktop is currently available on macOS and Windows.
  9. Install Claude for Desktop [here](https://claude.ai/download)
  10. #### Configuration
  11. Follow the general instructions [here](https://modelcontextprotocol.io/quickstart/user) to configure the Claude desktop client.
  12. You can find your Claude config at one of the following locations:
  13. - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
  14. - Windows: `%APPDATA%\Claude\claude_desktop_config.json`
  15. Then choose one of the following methods that best suits your needs and add it to your `claude_desktop_config.json`
  16. <details>
  17. <summary>Using pip</summary>
  18. (Option 1) Install release from PyPI
  19. ```bash
  20. pip install chronulus-mcp
  21. ```
  22. (Option 2) Install from Github
  23. ```bash
  24. git clone https://github.com/ChronulusAI/chronulus-mcp.git
  25. cd chronulus-mcp
  26. pip install .
  27. ```
  28. ```json
  29. {
  30. "mcpServers": {
  31. "chronulus-agents": {
  32. "command": "python",
  33. "args": ["-m", "chronulus_mcp"],
  34. "env": {
  35. "CHRONULUS_API_KEY": "<YOUR_CHRONULUS_API_KEY>"
  36. }
  37. }
  38. }
  39. }
  40. ```
  41. Note, if you get an error like "MCP chronulus-agents: spawn python ENOENT",
  42. then you most likely need to provide the absolute path to `python`.
  43. For example `/Library/Frameworks/Python.framework/Versions/3.11/bin/python3` instead of just `python`
  44. </details>
  45. <details>
  46. <summary>Using docker</summary>
  47. Here we will build a docker image called 'chronulus-mcp' that we can reuse in our Claude config.
  48. ```bash
  49. git clone https://github.com/ChronulusAI/chronulus-mcp.git
  50. cd chronulus-mcp
  51. docker build . -t 'chronulus-mcp'
  52. ```
  53. In your Claude config, be sure that the final argument matches the name you give to the docker image in the build command.
  54. ```json
  55. {
  56. "mcpServers": {
  57. "chronulus-agents": {
  58. "command": "docker",
  59. "args": ["run", "-i", "--rm", "-e", "CHRONULUS_API_KEY", "chronulus-mcp"],
  60. "env": {
  61. "CHRONULUS_API_KEY": "<YOUR_CHRONULUS_API_KEY>"
  62. }
  63. }
  64. }
  65. }
  66. ```
  67. </details>
  68. <details>
  69. <summary>Using uvx</summary>
  70. `uvx` will pull the latest version of `chronulus-mcp` from the PyPI registry, install it, and then run it.
  71. ```json
  72. {
  73. "mcpServers": {
  74. "chronulus-agents": {
  75. "command": "uvx",
  76. "args": ["chronulus-mcp"],
  77. "env": {
  78. "CHRONULUS_API_KEY": "<YOUR_CHRONULUS_API_KEY>"
  79. }
  80. }
  81. }
  82. }
  83. ```
  84. Note, if you get an error like "MCP chronulus-agents: spawn uvx ENOENT", then you most likely need to either:
  85. 1. [install uv](https://docs.astral.sh/uv/getting-started/installation/) or
  86. 2. Provide the absolute path to `uvx`. For example `/Users/username/.local/bin/uvx` instead of just `uvx`
  87. </details>
  88. #### Additional Servers (Filesystem, Fetch, etc)
  89. In our demo, we use third-party servers like [fetch](https://github.com/modelcontextprotocol/servers/tree/main/src/fetch) and [filesystem](https://github.com/modelcontextprotocol/servers/tree/main/src/filesystem).
  90. For details on installing and configure third-party server, please reference the documentation provided by the server maintainer.
  91. Below is an example of how to configure filesystem and fetch alongside Chronulus in your `claude_desktop_config.json`:
  92. ```json
  93. {
  94. "mcpServers": {
  95. "chronulus-agents": {
  96. "command": "uvx",
  97. "args": ["chronulus-mcp"],
  98. "env": {
  99. "CHRONULUS_API_KEY": "<YOUR_CHRONULUS_API_KEY>"
  100. }
  101. },
  102. "filesystem": {
  103. "command": "npx",
  104. "args": [
  105. "-y",
  106. "@modelcontextprotocol/server-filesystem",
  107. "/path/to/AIWorkspace"
  108. ]
  109. },
  110. "fetch": {
  111. "command": "uvx",
  112. "args": ["mcp-server-fetch"]
  113. }
  114. }
  115. }
  116. ```
  117. #### Claude Preferences
  118. To streamline your experience using Claude across multiple sets of tools, it is best to add your preferences to under Claude Settings.
  119. You can upgrade your Claude preferences in a couple ways:
  120. * From Claude Desktop: `Settings -> General -> Claude Settings -> Profile (tab)`
  121. * From [claude.ai/settings](https://claude.ai/settings): `Profile (tab)`
  122. Preferences are shared across both Claude for Desktop and Claude.ai (the web interface). So your instruction need to work across both experiences.
  123. Below are the preferences we used to achieve the results shown in our demos:
  124. ```
  125. ## Tools-Dependent Protocols
  126. The following instructions apply only when tools/MCP Servers are accessible.
  127. ### Filesystem - Tool Instructions
  128. - Do not use 'read_file' or 'read_multiple_files' on binary files (e.g., images, pdfs, docx) .
  129. - When working with binary files (e.g., images, pdfs, docx) use 'get_info' instead of 'read_*' tools to inspect a file.
  130. ### Chronulus Agents - Tool Instructions
  131. - When using Chronulus, prefer to use input field types like TextFromFile, PdfFromFile, and ImageFromFile over scanning the files directly.
  132. - When plotting forecasts from Chronulus, always include the Chronulus-provided forecast explanation below the plot and label it as Chronulus Explanation.
  133. ```

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.