MCP Installation
stock-sdk's MCP server talks to clients over stdio, and the launch command is always stock-sdk mcp. In each AI client you simply register it as a stdio-type MCP server.
The examples below launch via npx (no pre-install needed; -y skips the interactive prompt):
{
"command": "npx",
"args": ["-y", "stock-sdk", "mcp"]
}You can also
npm install -g stock-sdkfirst, then setcommandto"stock-sdk"andargsto["mcp"], saving thenpxresolution cost on each start.
Cursor
Create/edit .cursor/mcp.json in your project root (or the global config dir):
{
"mcpServers": {
"stock-sdk": {
"command": "npx",
"args": ["-y", "stock-sdk", "mcp"]
}
}
}After saving, enable stock-sdk in Cursor's MCP settings to call the market-data tools in chat.
Claude Desktop
Edit the Claude Desktop config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"stock-sdk": {
"command": "npx",
"args": ["-y", "stock-sdk", "mcp"]
}
}
}After saving, restart Claude Desktop; the stock-sdk tool icon should appear in the toolbar.
Codex
Add a server entry to Codex's MCP config (TOML):
[mcp_servers.stock-sdk]
command = "npx"
args = ["-y", "stock-sdk", "mcp"]Gemini
Add mcpServers to the Gemini CLI settings.json:
{
"mcpServers": {
"stock-sdk": {
"command": "npx",
"args": ["-y", "stock-sdk", "mcp"]
}
}
}Verify the connection
The server uses stdio and is normally spawned by the client — no need to run it by hand. To manually confirm it starts in a terminal:
npx -y stock-sdk mcpThe process waits for JSON-RPC messages (such as initialize) on stdin. Once a client is connected, ask the model to "list available tools" to confirm the handshake succeeded.
Config file paths and field names may vary across client versions — follow each client's official docs. This page only fixes the
stock-sdk mcplaunch entry.
Next steps
- MCP Tool Table: the tools available once connected.
- AI Skills: compose tools into higher-level skills like technical analysis and smart screening.