Cursor market pulse pulse_should_i_bid
How to: Cursor market pulse pulse_should_i_bid
Add market pulse to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"market-pulse": {
"url": "https://market-pulse.t3ratech.co.zw/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something pulse_should_i_bid does. Cursor lists the server's tools on connect and calls pulse_should_i_bid itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that market pulse's identifier in your config matches the one above exactly.
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs
Set these first
market pulse will not start until these are set, so pulse_should_i_bid never becomes available.
-
MARKET_PULSE_API_KEY -
MARKET_PULSE_TIMEOUT_MS
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 7 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.