S&P 500 MCP Server
Provides tools for querying S&P 500 company data (fundamentals, financials, prices, news, officers, SEC filings) stored in a Supabase database.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@S&P 500 MCP ServerWhat are the latest financials for Apple?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
S&P 500 MCP Server
An MCP (Model Context Protocol) server and Next.js web app for querying S&P 500 company data from Supabase. It exposes MCP tools for company fundamentals, annual financial metrics, historical price data, news sentiment, officers, and SEC filings, plus a web UI and embedded MCP App resources for browsing and testing those tools.
Tools
Tool | Description |
| Company basics, financials, leadership, address, and business summary |
| Annual financial metrics with chart-ready trends and matrix output |
| Historical daily OHLCV price rows with date filters |
| Recent company news with sentiment filtering |
| Executive officers and compensation |
| SEC filings history, with filing type and date filters |
search_companies is an internal symbol resolver, not an exposed MCP tool. User queries are resolved through getCompanySymbol.
Tech Stack
Workspace: pnpm 10.33.3 + Turborepo
Runtime: Node 22 (
.nvmrc)Web app: Next.js 16 App Router, React 19, TypeScript strict mode (
apps/web)MCP Apps: Vite single-file React pages built from
apps/web-appand served as tool UI resourcesMCP:
mcp-handleratapps/web/app/[transport]/route.ts;/sseis the public SSE endpointDatabase: Supabase client at
apps/web/app/[transport]/utils/supabase.tsUI: shared shadcn/Tailwind primitives in
packages/ui
Getting Started
Prerequisites
Node.js 22
pnpm 10
Supabase project with the S&P 500 data tables used by the tools
Local Development
Install dependencies:
pnpm installCreate a local env file with Supabase credentials:
SUPABASE_URL=your_supabase_url
SUPABASE_ANON_KEY=your_supabase_anon_key
MCP_MAX_DURATION=60
REDIS_URL=your_redis_url
LOGO_DEV_TOKEN=your_logo_dev_publishable_keySUPABASE_URL and SUPABASE_ANON_KEY are required. REDIS_URL is only needed for production SSE. LOGO_DEV_TOKEN is required for the /api/logo/* proxy.
Build the embedded MCP App HTML resources:
pnpm --filter @apps/web-app buildStart the apps:
pnpm devThe Next.js web app runs on http://localhost:3000; the MCP endpoint is http://localhost:3000/sse. The apps/web-app dev server proxies /sse to port 3000 when run separately.
Commands
pnpm dev # Start apps/* dev tasks via Turbo
pnpm build # Build apps/web and apps/web-app via Turbo
pnpm start # Start production server for apps/web
pnpm type-check # Type-check apps/web and apps/web-app
pnpm lint # ESLint + Prettier rule checksFocused commands:
pnpm --filter @apps/web dev
pnpm --filter @apps/web-app dev
pnpm --filter @apps/web-app build
pnpm exec tsc -p apps/web/tsconfig.json --noEmit
pnpm exec tsc -p apps/web-app/tsconfig.json --noEmit
pnpm exec tsc -p packages/ui/tsconfig.json --noEmitTesting
Tests are integration tests that connect a real MCP client to http://localhost:3000/sse, so start the dev server first:
pnpm --filter @apps/web-app build
pnpm dev
pnpm testRun a single tool test:
pnpm vitest run apps/web/tests/tools/get-company-info-tool.test.tsGenerate coverage:
pnpm coverageProject Layout
apps/web/
app/[transport]/route.ts MCP GET/POST/DELETE handler
app/[transport]/tools/ MCP tool registrations
app/[transport]/utils/ Supabase, symbol resolution, summaries
app/api/tools/call/route.ts HTTP proxy for the web tool tester
app/tools/ Tool catalog page
components/ App-specific UI
tests/tools/ MCP integration tests
apps/web-app/
src/pages/ Embedded MCP App pages, one per tool
src/components/ MCP App UI components
scripts/build-pages.js Builds each page into dist/*.html
dist/ Generated single-file HTML resources
packages/ui/
src/components/ Shared shadcn UI primitives
src/styles/globals.css Shared Tailwind CSSapps/web/app/[transport]/tools/app-resource.ts reads generated HTML from apps/web-app/dist, so rebuild apps/web-app after changing embedded MCP App pages.
Vercel Deployment
Requires Fluid compute
MCP_MAX_DURATIONdefaults to60; set a higher duration for long-running production calls when your Vercel plan supports itSSE is enabled (
disableSse: false); production SSE requires Redis viaREDIS_URL
Docs
Full guides and examples: https://sp500-mcp.vercel.app/
Contributing
Feel free to dive in! Open an issue or submit PRs.
Standard Readme follows the Contributor Covenant Code of Conduct.
Contributors
This project exists thanks to all the people who contribute.
License
GNU Affero General Public License v3.0 © MichaelSun
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zhensherlock/sp500-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server