QuestradeMCP MCP Server

MCP server for Questrade API integration

Local serverstdioTypeScript

What is the QuestradeMCP MCP server?

Most developer tooling work still happens through a UI a human drives. QuestradeMCP MCP server moves it into the conversation instead. MCP server for Questrade API integration.

The short version

An unofficial Model Context Protocol (MCP) server for integrating with the Questrade API, providing access to trading accounts, market data, and portfolio information.

  • 🔐 Authentication: OAuth 2.0 token management with automatic refresh
  • 📊 Account Data: Access accounts, positions, balances, and order history
  • 📈 Market Data: Real-time quotes, symbol search, and historical candles
  • 🛡️ Error Handling: Comprehensive error handling and logging
  • 🔧 TypeScript: Full TypeScript support with proper type definitions

The tools it exposes

The server publishes 5 tools. What each one is for:

  • Development — The Development tool exposed by this server
  • Production — The Production tool exposed by this server
  • Authentication — The Authentication tool exposed by this server
  • Building — The Building tool exposed by this server
  • Cleaning — The Cleaning tool exposed by this server

Getting it running

Installation goes through your MCP client rather than a global install: point it at questrade-mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What it needs from you

Configuration is passed through the environment: QUESTRADE_REFRESH_TOKEN, QUESTRADE_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. QuestradeMCP's toolset — Development, Production, Authentication and 2 more — is a fair guide to whether it matches your workflow. It is maintained by zachmelin; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against QuestradeMCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
DevelopmentThe Development tool exposed by this server.
ProductionThe Production tool exposed by this server.
AuthenticationThe Authentication tool exposed by this server.
BuildingThe Building tool exposed by this server.
CleaningThe Cleaning tool exposed by this server.

How to install the QuestradeMCP MCP server

{
     "mcpServers": {
       "questrade": {
         "command": "npx",
         "args": ["questrade-mcp-server"],
         "env": {
           "QUESTRADE_REFRESH_TOKEN": "your_refresh_token_here"
         }
       }
     }
   }

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
QUESTRADE_REFRESH_TOKENCredential the server authenticates with.Yes
QUESTRADE_API_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use QuestradeMCP to Development.
  • Use QuestradeMCP to Production.
  • Use QuestradeMCP to Authentication.

Frequently asked questions

It connects QuestradeMCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (Development, Production, Authentication, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with QuestradeMCP directly.