DEPTH4 MCP for agents

Authentication

Keys use the depth4_mcp_ prefix. For the stdio server, set DEPTH4_MCP_API_KEY. For HTTP integrations, send Authorization: Bearer depth4_mcp_… or header x-depth4-mcp-key.

Cursor

{
  "mcpServers": {
    "depth4": {
      "command": "node",
      "args": ["/path/to/signal/apps/mcp/dist/index.js"],
      "env": { "DEPTH4_MCP_API_KEY": "depth4_mcp_…" }
    }
  }
}

Claude SDK

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";

const transport = new StdioClientTransport({
  command: "node",
  args: ["signal/apps/mcp/dist/index.js"],
  env: { ...process.env, DEPTH4_MCP_API_KEY: process.env.DEPTH4_MCP_API_KEY },
});
const client = new Client({ name: "my-agent", version: "1.0.0" });
await client.connect(transport);
const result = await client.callTool({ name: "depth4_list_signals", arguments: { limit: 10 } });

LangChain

// Wrap MCP tools as LangChain tools via your MCP client bridge.
// Example shape:
const depth4ListSignals = tool(
  async ({ limit }) => mcpClient.callTool("depth4_list_signals", { limit }),
  { name: "depth4_list_signals", description: "List DEPTH4 asset signals" },
);

Tool reference