Skip to content
mcp/harbor

Windsurf Tiingo resolve_entity

How to: Windsurf Tiingo resolve_entity

client:Windsurf transport:streamable-http tool:resolve_entity

Add Tiingo to Windsurf

  1. 01

    Open ~/.codeium/windsurf/mcp_config.json and merge this in. Keep any servers already there. 

{
  "mcpServers": {
    "tiingo": {
      "serverUrl": "https://gateway.pipeworx.io/tiingo/mcp"
    }
  }
}
  1. 02

    Save the file and restart Windsurf.

  2. 03

    Ask for something resolve_entity does. Windsurf lists the server's tools on connect and calls resolve_entity itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Tiingo's identifier in your config matches the one above exactly.

Global only — Windsurf has no per-project MCP config. Refresh Cascade after saving. Windsurf docs

Set these first

Tiingo will not start until these are set, so resolve_entity never becomes available.

  • PIPEWORX_API_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.

Tiingo MCP server