Credentials. API tokens grant access to your workbench, so give each client the lowest scope and keep the gateway local only.
Who it is forA developer who wants Claude, Codex or another MCP client to query their local quant data.
The problemBuilding bots on top of a dashboard usually means scraping pages.
The outcomeAn AI client calling 12 MCP tools on your local workbench, limited by the token scope you choose.
What you need first
- Docker (one container, no external database)
- Optional: a TickFlow API key or another plugged in data source
- Optional: an OpenAI compatible LLM endpoint for strategy generation and the chat assistant
Steps
- Run the workbench and create an API token with the narrowest scope you need
- Set up the bundled mcp-server, which runs over stdio
- Add it to your MCP client config
- Ask the client a data question and check the tool calls it made
Prompt for your agent
Connect shy3130/tick-stock-panel's mcp-server to <MCP client> with a read only token, list the available tools, and answer <data question>. Show me which tools were called.
Caveat. By default the token gateway only accepts local or LAN traffic, so keep it that way unless you know why to open it. Not financial advice: paper trade first, and remember you can lose money.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for shy3130/tick-stock-panel and "Connect an AI client to your quant workbench over MCP"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer