QuantConnect
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_NAME | No | Name of the agent to keep record of the request source. Set a unique value for each agent if running multiple agents simultaneously. | MCP Server |
| QUANTCONNECT_USER_ID | Yes | Your QuantConnect user ID | |
| QUANTCONNECT_API_TOKEN | Yes | Your QuantConnect API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_accountA | Read the organization account status. |
| create_projectB | Create a new project in your default organization. |
| read_projectB | List the details of a project or a set of recent projects. |
| list_projectsA | List the details of all projects. |
| update_projectA | Update a project's name or description. |
| delete_projectC | Delete a project. |
| create_project_collaboratorB | Add a collaborator to a project. |
| read_project_collaboratorsA | List all collaborators on a project. |
| update_project_collaboratorB | Update collaborator information in a project. |
| delete_project_collaboratorC | Remove a collaborator from a project. |
| lock_project_with_collaboratorsA | Lock a project so you can edit it. This is necessary when the project has collaborators or when an LLM is editing files on your behalf via our MCP Server. |
| read_project_nodesA | Read the available and selected nodes of a project. |
| update_project_nodesC | Update the active state of the given nodes to true. |
| create_compileB | Asynchronously create a compile job request for a project. |
| read_compileB | Read a compile packet job result. |
| create_fileA | Add a file to a given project. |
| read_fileA | Read a file from a project, or all files in the project if no file name is provided. |
| update_file_nameB | Update the name of a file. |
| update_file_contentsC | Update the contents of a file. |
| patch_fileA | Apply a patch (unified diff) to a file in a project. |
| delete_fileB | Delete a file in a project. |
| create_backtestC | Create a new backtest request and get the backtest Id. |
| read_backtestB | Read the results of a backtest. |
| list_backtestsA | List all the backtests for the project. |
| read_backtest_chartC | Read a chart from a backtest. |
| read_backtest_ordersB | Read out the orders of a backtest. |
| read_backtest_insightsC | Read out the insights of a backtest. |
| update_backtestA | Update the name or note of a backtest. |
| delete_backtestA | Delete a backtest from a project. |
| estimate_optimization_timeC | Estimate the execution time of an optimization with the specified parameters. |
| create_optimizationC | Create an optimization with the specified parameters. |
| read_optimizationC | Read an optimization. |
| list_optimizationsA | List all the optimizations for a project. |
| update_optimizationB | Update the name of an optimization. |
| abort_optimizationC | Abort an optimization. |
| delete_optimizationB | Delete an optimization. |
| authorize_connectionA | Authorize an external connection with a live brokerage or data provider. This tool automatically opens your browser for you to complete the authentication flow. For the flow to work, you must be logged into your QuantConnect account on the browser that opens. |
| create_live_algorithmD | Create a live algorithm. |
| read_live_algorithmC | Read details of a live algorithm. |
| list_live_algorithmsC | List all your past and current live trading deployments. |
| read_live_chartC | Read a chart from a live algorithm. |
| read_live_logsA | Get the logs of a live algorithm. The snapshot updates about every 5 minutes. |
| read_live_portfolioB | Read out the portfolio state of a live algorithm. The snapshot updates about every 10 minutes. |
| read_live_ordersA | Read out the orders of a live algorithm. The snapshot updates about every 10 minutes. |
| read_live_insightsB | Read out the insights of a live algorithm. The snapshot updates about every 10 minutes. |
| stop_live_algorithmB | Stop a live algorithm. |
| liquidate_live_algorithmC | Liquidate and stop a live algorithm. |
| create_live_commandC | Send a command to a live trading algorithm. |
| broadcast_live_commandC | Broadcast a live command to all live algorithms in an organization. |
| upload_objectC | Upload files to the Object Store. |
| read_object_propertiesA | Get Object Store properties of a specific organization and key. It doesn't work if the key is a directory in the Object Store. |
| read_object_store_file_job_idC | Create a job to download files from the Object Store and then read the job Id. |
| read_object_store_file_download_urlB | Get the URL for downloading files from the Object Store. |
| list_object_store_filesB | List the Object Store files under a specific directory in an organization. |
| delete_objectB | Delete the Object Store file of a specific organization and key. |
| read_lean_versionsA | Returns a list of LEAN versions with basic information for each version. |
| check_initialization_errorsB | Run a backtest for a few seconds to initialize the algorithm and get inialization errors if any. |
| complete_codeC | Show the code completion for a specific text input. |
| enhance_error_messageB | Show additional context and suggestions for error messages. |
| update_code_to_pep8C | Update Python code to follow PEP8 style. |
| check_syntaxC | Check the syntax of a code. |
| search_quantconnectB | Search for content in QuantConnect. |
| read_mcp_server_versionA | Returns the version of the QC MCP Server that's running. |
| read_latest_mcp_server_versionB | Returns the latest version of the QC MCP Server released. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 64 tools
Tools are mostly distinct, with clear read/create/update/delete boundaries per resource domain. Minor overlap exists between list_projects and read_project (both can list projects), and stop_live_algorithm vs liquidate_live_algorithm could be misselected by an agent not reading carefully.
Most tools follow a consistent verb_noun snake_case pattern (create_backtest, read_backtest, list_backtests, delete_file). Deviations include object vs object_store prefixes, read_object_store_file_job_id which actually creates a job, and read_lean_versions used for listing.
This server exposes 64 tools, well above the 25+ threshold the rubric flags as too many for typical agent use. Even though the broad platform has genuine sub-domains, the sheer number makes the set heavy to navigate and increases the chance of misselection.
The tool set covers most core lifecycle workflows: projects, files, compiles, backtests, live algorithms, optimizations, object store, and collaboration. A few minor gaps exist, such as no ability to update optimization parameters after creation, no backtest abort, and no live algorithm update, but these are workable.