TAM MCP Server

Market research and business intelligence with TAM/SAM calculations and integration across 8 economic data sources: Alpha Vantage, BLS, Census

Local serverstdioTypeScript

What is the TAM MCP server?

Market research and business intelligence with TAM/SAM calculations and integration across 8 economic data sources: Alpha Vantage, BLS, Census Bureau, FRED, IMF, Nasdaq Data Link, OECD, and World Bank. That is what the tam mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

A Model Context Protocol server providing market research and business analysis capabilities through 28 tools, 15 business prompts, and integration with 8 economic data sources.

This MCP server provides comprehensive market research capabilities including:

  • Total Addressable Market (TAM) and Serviceable Addressable Market (SAM) calculations
  • Market size estimation and forecasting
  • Industry analysis and competitive intelligence
  • Market segmentation and opportunity identification
  • Data validation and cross-source verification
  • Startup funding pitch preparation

The tools it exposes

The server publishes 14 tools. What each one is for:

  • serverUrlhttp://localhost:3000
  • sessionId — (automatically set after initialization)
  • Source — Tools
  • BLS — bls_getSeriesData
  • Census — census_fetchIndustryData, census_fetchMarketSize
  • FRED — fred_getSeriesObservations
  • IMF — imf_getDataset, imf_getLatestObservation
  • Nasdaq — nasdaq_getDatasetTimeSeries, nasdaq_getLatestDatasetValue
  • OECD — oecd_getDataset, oecd_getLatestObservation
  • industry_search — Basic industry data search from sources
  • tam_calculator — Basic Total Addressable Market calculations
  • market_size_calculator — Market size estimation and calculations

What it needs from you

Configuration is passed through the environment: ALPHA_VANTAGE_API_KEY, FRED_API_KEY, CENSUS_API_KEY, NASDAQ_DATA_LINK_API_KEY, BLS_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js 20.x or later - npm or yarn - API keys for data sources (optional, see Configuration)

Getting it running

The server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. TAM's toolset — serverUrl, sessionId, Source and 11 more — is a fair guide to whether it matches your workflow. It is maintained by gvaibhav; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against TAM's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch TAM.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
serverUrlhttp://localhost:3000
sessionId(automatically set after initialization)
SourceTools
BLSbls_getSeriesData
Censuscensus_fetchIndustryData, census_fetchMarketSize
FREDfred_getSeriesObservations
IMFimf_getDataset, imf_getLatestObservation
Nasdaqnasdaq_getDatasetTimeSeries, nasdaq_getLatestDatasetValue
OECDoecd_getDataset, oecd_getLatestObservation
industry_searchBasic industry data search from sources
tam_calculatorBasic Total Addressable Market calculations
market_size_calculatorMarket size estimation and calculations
company_financials_retrieverEnhanced company financial data retrieval
industry_analysisEnhanced multi-source industry analysis

How to install the TAM MCP server

**STDIO Transport (Alternative)**
```json
{
  "mcpServers": {
    "tam": {
      "command": "npm",
      "args": ["run", "start:stdio"],
      "cwd": "/path/to/TAM-MCP-Server"
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js 20.x or later - npm or yarn - API keys for data sources (optional, see Configuration)
VariableDescriptionRequired
ALPHA_VANTAGE_API_KEYCredential the server authenticates with.Yes
FRED_API_KEYCredential the server authenticates with.Yes
CENSUS_API_KEYCredential the server authenticates with.Yes
NASDAQ_DATA_LINK_API_KEYCredential the server authenticates with.Yes
BLS_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use TAM to serverUrl.
  • Use TAM to sessionId.
  • Use TAM to Source.

Frequently asked questions

It connects TAM to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (serverUrl, sessionId, Source, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with TAM directly.