Market Sizing MCP Server

- Stock symbols: AAPL, MSFT, GOOGL
- Industry codes: NAICS 54 (Professional Services)
- Market sizes: $10B base with 15% growth
- Time periods: 2020-2024

- NodeCache-based with configurable TTLs
- Automatic cleanup and statistics
- Per-source cache invalidation

const dataService = new EnhancedDataService({ cache: { type: 'redis' }, apiKeys: { / your keys / } });

TAM-MCP-Server/ ├── config/ # Configuration files │ ├── jest.config.json # Jest test configuration │ ├── vitest.config.ts # Vitest test configuration │ └── redis.conf # Redis configuration ├── doc/ # Documentation │ ├── README.md # Documentation hub │ ├── consumer/ # Consumer documentation │ │ ├── getting-started.md # Getting started guide │ │ ├── default-values-guide.md # Default values guide │ │ ├── mcp-prompts-guide.md # MCP prompts guide │ │ ├── tools-guide.md # Tools reference │ │ └── api-reference.md # API documentation │ ├── contributor/ # Contributor documentation │ │ ├── contributing.md # Development guidelines │ │ └── security.md # Security policy │ ├── reference/ # Reference documentation │ │ ├── RELEASE-NOTES.md # Version history │ │ ├── CHANGELOG.md # Technical changes │ │ └── requirements.md # Technical specifications │ ├── reports/ # Technical reports and validation │ │ ├── SEMANTIC-VALIDATION-COMPLETE.md # Validation results │ │ └── DEFAULT-VALUES-SUMMARY.md # Default values analysis │ └── archive/ # Historical documents ├── examples/ # Examples and demos │ ├── README.md # Examples documentation │ ├── demo-default-values.mjs # Default values demonstration │ ├── demo-integration.mjs # Integration examples │ └── TAM-MCP-Server-Postman-Collection.json # API testing ├── scripts/ # Build and development scripts │ ├── build.sh # Production build script │ ├── dev-setup.sh # Development environment setup │ └── dev.sh # Development helper script ├── src/ # Source code │ ├── index.ts # Main entry point │ ├── server.ts # Core MCP server │ ├── http.ts # HTTP transport │ ├── sse-new.ts # SSE transport │ ├── stdio-simple.ts # STDIO transport │ ├── config/ # Configuration modules │ ├── services/ # Data source services │ ├── tools/ # MCP tool implementations │ ├── prompts/ # Business prompt templates │ ├── notifications/ # Notification system │ ├── types/ # TypeScript definitions │ └── utils/ # Utility functions ├── tests/ # Test suite │ ├── unit/ # Unit tests │ ├── integration/ # Integration tests │ ├── e2e/ # End-to-end tests │ ├── scripts/ # Test and validation scripts │ │ ├── test-comprehensive.mjs # Comprehensive testing │ │ ├── test-semantic-validation.mjs # Semantic validation │ │ └── *.mjs # Additional test utilities │ ├── fixtures/ # Test data and mock objects │ ├── utils/ # Test utilities and helpers │ └── setup.ts # Test configuration ├── logs/ # Application logs ├── dist/ # Compiled JavaScript (built) ├── .env.example # Environment template ├── package.json # Node.js dependencies ├── tsconfig.json # TypeScript configuration └── README.md # Main documentation

15 Professional Business Analysis Promptsdesigned for real-world business scenarios:

- startup_funding_pitch- Series A-C funding presentations with TAM/SAM analysis
- private_equity_research- Investment committee packages for PE deals
- corporate_strategy_entry- Fortune 500 market entry strategy analysis
- venture_capital_thesis- VC investment thesis development
- asset_management_research- Institutional asset management research

- crisis_management_analysis- Emergency market analysis for crisis response
- regulatory_impact_assessment- Regulatory change impact analysis
- international_expansion- Global market entry strategy analysis
- technology_disruption_analysis- Technology disruption impact assessment
- esg_sustainability_analysis- ESG and sustainability market analysis

- market_opportunity_scan- Rapid market opportunity identification
- competitive_intelligence- Competitive landscape analysis
- investment_screening- Investment opportunity screening
- tool_guidance- Interactive guide to TAM MCP Server tools
- best_practices_guide- Best practices for market analysis

Designed for AI applications serving business analysts, developers, and market researchers with deep market intelligence and data access tools.

The project uses a comprehensive test structure with Vitest as the primary testing framework:

tests/ ├── unit/ # Fast, isolated component tests ├── integration/ # Component interaction tests ├── e2e/ # End-to-end workflow tests ├── scripts/ # Integration test scripts │ ├── test-comprehensive.mjs # Comprehensive testing │ ├── test-http-streaming.mjs # HTTP streaming transport │ ├── test-simple-mcp.mjs # Basic MCP functionality │ └── test-mcp-tool-calls.mjs # Individual tool validation ├── fixtures/ # Test data and mock objects ├── utils/ # Test utilities and helpers └── setup.ts # Vitest global configuration

# Run all tests npm test # Run by category npm run test:unit # Fast unit tests npm run test:integration # Integration tests npm run test:e2e # End-to-end tests # Advanced options npm run test:coverage # With coverage report npm run test:watch # Watch mode for development npm run test:ui # Vitest UI mode npm run test:ci # CI-optimized test run # Run integration scripts npm run test:scripts # Comprehensive backend integration npm run test:scripts:http # HTTP streaming transport npm run test:scripts:simple # Basic MCP functionality npm run test:scripts:tools # Individual tool validation npm run test:scripts:inspector # MCP Inspector compatibility # Or run directly node tests/scripts/test-comprehensive.mjs node tests/scripts/test-http-streaming.mjs

Import the comprehensive Postman collection for testing both MCP endpoints and backend API integrations:
- Import Collection:examples/TAM-MCP-Server-Postman-Collection.json
- Set Environment Variables:

- Health check and server status
- MCP session initialization
- All 28 tools (11 market analysis + 17 data access)
- Resource access endpoints
- Session management and cleanup

Newman CLI TestingAutomate Postman tests from command line:

# Install Newman npm install -g newman # Run backend API tests newman run examples/TAM-MCP-Server-Postman-Collection.json \ -e tests/postman/environments/TAM-MCP-Server-Environment.postman_environment.json \ --reporters cli,json # Or use npm script npm run test:postman

- Unit Level: Individual tool functionality and business logic
- Integration Level: MCP protocol compliance and server behavior
- System Level: Complete workflows through real transports
- API Level: REST endpoints and session management
- Performance: Response time and resource usage monitoring

Code coverage reports are generated in thecoverage/directory.

src/ ├── index.ts # Main entry point ├── server.ts # MCP server implementation ├── http.ts # HTTP transport ├── sse-new.ts # SSE transport ├── stdio-simple.ts # STDIO transport ├── config/ # Configuration modules │ └── apiConfig.ts # API endpoint configurations ├── services/ # Data source services │ ├── dataService.ts # Main data orchestrator │ ├── cache/ # Caching services │ │ ├── cacheService.ts # In-memory caching │ │ └── persistenceService.ts # File persistence │ └── dataSources/ # Individual data source clients │ ├── alphaVantageService.ts │ ├── blsService.ts │ ├── censusService.ts │ ├── fredService.ts │ ├── imfService.ts │ ├── nasdaqDataService.ts │ ├── oecdService.ts │ └── worldBankService.ts ├── tools/ # MCP tool implementations │ └── market-tools.ts # MarketAnalysisTools class ├── prompts/ # Business prompt templates ├── notifications/ # Notification system ├── types/ # TypeScript definitions │ ├── index.ts # Core schemas and types │ ├── dataSources.ts # Data source interfaces │ └── cache.ts # Cache-related types └── utils/ # Utility functions ├── dataTransform.ts # Data transformation ├── envHelper.ts # Environment parsing ├── rateLimit.ts # Rate limiting └── logger.ts # Winston logging tests/ ├── unit/ # Unit tests ├── integration/ # Integration tests ├── e2e/ # End-to-end tests └── scripts/ # Test automation scripts

# Import collection examples/TAM-MCP-Server-Postman-Collection.json # Or run with Newman npm run test:postman

- Language: TypeScript 5.x
- Protocol: MCP 2025-03-26
- Framework: Express.js 4.x
- Validation: Zod schemas
- Testing: Vitest + Postman
- Cache: NodeCache (Redis optional)
- Logging: Winston

Services showing as disabled despite API keys

- Ensure.envfile is in project root
- Check API key variable names match exactly
- Restart server after adding keys
- Verify startup logs show service initialization

- Use:npx @modelcontextprotocol/inspector node dist/stdio-simple.js
- Ensure no console.log statements contaminate stdout
- Check Winston logger uses stderr for output

- Runnpm installto update dependencies
- Check Node.js version (20.x recommended)
- Clear build cache:rm -rf dist && npm run build

- Check service status in startup logs
- Verify API quotas not exceeded
- Test withgeneric_data_querytool
- Check network connectivity

All documentation is also accessible through the MCP protocol:

// Discover all available documentation { "method": "resources/list", "params": {} } // Read specific documentation { "method": "resources/read", "params": { "uri": "file:///README.md" } }