# quantconnect-mcp-jwt
## 基本信息
- Slug: `i-dream-of-ai-quantconnect-mcp-jwt`
- Source: modelscope
- Publisher: @i-dream-of-ai/quantconnect-mcp-jwt
- Categories: 金融 / cloud-platforms / agent-orchestration
- Hosted: No
- License: Apache License 2.0
- Source URL: https://www.modelscope.cn/mcp/servers/@i-dream-of-ai/quantconnect-mcp-jwt
## 简介
暂无描述。
## 安装提示

```bash
To get your user Id and API token, see [Request API Token](https://www.quantconnect.com/docs/v2/cloud-platform/community/profile#09-Request-API-Token). Our MCP server is multi-platform capable. The options are `linux/amd64` for Intel/AMD chips and `linux/arm64` for ARM chips (for example, Apple's M-series chips). If you simultaneously run multiple agents, set a unique value for the `AGENT_NAME` environment variable for each agent to keep record of the request source. 5. Restart Claude Desktop. Claude Desktop automatically pulls our MCP server from Docker Hub and connects to it. To view all the MCP clients and the features they support, see the [Feature Support Matrix](https://modelcontextprotocol.io/clients#feature-support-matrix) in the MCP documentation. To keep the Docker image up-to-date, pull the latest MCP server from Docker Hub in the terminal.
```

## MCP Server 详情

<img width="1575" height="280" alt="github-header" src="https://github.com/user-attachments/assets/6cec1ef7-0340-416e-ab81-c73fbc8ff847" />


# QuantConnect MCP Server
The QuantConnect MCP Server is a bridge for AIs (such as Claude and OpenAI o3 Pro) to interact with our cloud platform. When equipped with our MCP, the AI can perform tasks on your behalf through our API such as updating projects, writing strategies, backtesting, and deploying strategies to production live-trading.

Our implementation is tested and dockerized for easy cross-platform deployment.

## Getting Started
To connect local MCP clients (like Claude Desktop) to the QC MCP Server, follow these steps:

1. Install and open [Docker Desktop](https://docs.docker.com/desktop/).
2. Install and open [Claude Desktop](https://claude.ai/download).
3. In Claude Desktop, click **File > Settings > Developer > Edit Config**.
4. Edit the `claude_desktop_config.json` file to include the following `quantconnect` configuration:

```json
{
  "mcpServers": {
    "quantconnect": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e", "QUANTCONNECT_USER_ID",
        "-e", "QUANTCONNECT_API_TOKEN",
        "-e", "AGENT_NAME",
        "--platform", "<your_platform>",
        "--name",
        "quantconnect-mcp-server",
        "quantconnect/mcp-server"
      ],
      "env": {
        "QUANTCONNECT_USER_ID": "<your_user_id>",
        "QUANTCONNECT_API_TOKEN": "<your_api_token>",
        "AGENT_NAME": "MCP Server"
      }
    }
  }
}
```

  To get your user Id and API token, see [Request API Token](https://www.quantconnect.com/docs/v2/cloud-platform/community/profile#09-Request-API-Token).

  Our MCP server is multi-platform capable. The options are `linux/amd64` for Intel/AMD chips and `linux/arm64` for ARM chips (for example, Apple's M-series chips).

  If you simultaneously run multiple agents, set a unique value for the `AGENT_NAME` environment variable for each agent to keep record of the request source. 

5. Restart Claude Desktop.

   Claude Desktop automatically pulls our MCP server from Docker Hub and connects to it.

To view all the MCP clients and the features they support, see the [Feature Support Matrix](https://modelcontextprotocol.io/clients#feature-support-matrix) in the MCP documentation.

To keep the Docker image up-to-date, pull the latest MCP server from Docker Hub in the terminal.
```
docker pull quantconnect/mcp-server
```
If you have an ARM chip, add the `--platform linux/arm64` option.

## Available Tools (60)
| Tools provided by this Server | Short Description |
| -------- | ------- |
| `read_account` | Read the organization account status. |
| `create_project` | Create a new project in your default organization. |
| `read_project` | List the details of a project. |
| `list_projects` | List the details of all projects. |
| `update_project` | Update a project's name or description. |
| `delete_project` | Delete a project. |
| `create_project_collaborator` | Add a collaborator to a project. |
| `read_project_collaborators` | List all collaborators on a project. |
| `update_project_collaborator` | Update collaborator information in a project. |
| `delete_project_collaborator` | Remove a collaborator from a project. |
| `read_project_nodes` | Read the available and selected nodes of a project. |
| `update_project_nodes` | Update the active state of the given nodes to true. |
| `create_compile` | Asynchronously create a compile job request for a project. |
| `read_compile` | Read a compile packet job result. |
| `create_file` | Add a file to a given project. |
| `read_file` | Read a file from a project, or all files in the project if no file name is provided. |
| `update_file_name` | Update the name of a file. |
| `update_file_contents` | Update the contents of a file. |
| `delete_file` | Delete a file in a project. |
| `create_backtest` | Create a new backtest request and get the backtest Id. |
| `read_backtest` | Read the results of a backtest. |
| `list_backtests` | List all the backtests for the project. |
| `read_backtest_chart` | Read a chart from a backtest. |
| `read_backtest_orders` | Read out the orders of a backtest. |
| `read_backtest_insights` | Read out the insights of a backtest. |
| `update_backtest` | Update the name or note of a backtest. |
| `delete_backtest` | Delete a backtest from a project. |
| `estimate_optimization_time` | Estimate the execution time of an optimization with the specified parameters. |
| `create_optimization` | Create an optimization with the specified parameters. |
| `read_optimization` | Read an optimization. |
| `list_optimizations` | List all the optimizations for a project. |
| `update_optimization` | Update the name of an optimization. |
| `abort_optimization` | Abort an optimization. |
| `delete_optimization` | Delete an optimization. |
| `authorize_connection` | Authorize an external connection with a live brokerage or data provider. |
| `create_live_algorithm` | Create a live algorithm. |
| `read_live_algorithm` | Read details of a live algorithm. |
| `list_live_algorithms` | List all your past and current live trading deployments. |
| `read_live_chart` | Read a chart from a live algorithm. |
| `read_live_logs` | Get the logs of a live algorithm. |
| `read_live_portfolio` | Read out the portfolio state of a live algorithm. |
| `read_live_orders` | Read out the orders of a live algorithm. |
| `read_live_insights` | Read out the insights of a live algorithm. |
| `stop_live_algorithm` | Stop a live algorithm. |
| `liquidate_live_algorithm` | Liquidate and stop a live algorithm. |
| `create_live_command` | Send a command to a live trading algorithm. |
| `broadcast_live_command` | Broadcast a live command to all live algorithms in an organization. |
| `upload_object` | Upload files to the Object Store. |
| `read_object_properties` | Get Object Store properties of a specific organization and key. |
| `read_object_store_file_job_id` |…