# Bigdata MCP MCP Server > **Bigdata MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to Bigdata MCP. > > MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows, > token refresh, and production-grade auto-scaling — so your AI agents can connect to > third-party services and run freely without you managing any MCP server yourself. > > Server page: https://mewcp.com/mcp/bigdata-mcp > MewCP docs: https://docs.mewcp.com > Full catalog: https://mewcp.com/llms.txt --- ## About BigData.com provides AI-powered financial research across global markets, enabling users to discover market-moving news, analyze company fundamentals, monitor earnings and economic events, track insider transactions, and identify investment opportunities using financial data and real-time news intelligence. --- ## Details - Server ID: `bigdata-mcp` - Version: 4.1.0 - Tools: 25 - Authentication: API key, held by MewCP - Transport: http --- ## Access The gateway URL below serves your **entire MewCP toolset**, not this server on its own. Pasting a config snippet is not enough — Bigdata MCP has to be in the toolset first. In order: 1. Add Bigdata MCP to your toolset at https://mewcp.com/mcp/bigdata-mcp 2. Connect your Bigdata MCP account (API key); MewCP stores the credential and attaches it to each call 3. Copy your MewCP API key from the dashboard (Developer) 4. Configure your client with the snippet for it below Once connected, an agent does **not** see this server's tools as top-level tools. It sees four meta-tools and reaches everything through them: - `search(query)` — find tools by keyword across the toolset - `get_schema(tools)` — full description and arguments for the tools you picked - `list_accounts(provider)` — only when one app has several connected accounts - `call_tool(server_maskedId, tool_name, args)` — execute So the list below is what `search` can return for this server, not a set of callable tool names on their own. --- ## Tools (25) Descriptions are truncated to 160 characters; call `get_schema` for the full text and the argument schema. Where a tool is annotated, its type is shown — treat `destructive` as irreversible. - `bigdata_mcp_instructions` _(read)_ — [SYSTEM CONTEXT - DO NOT CALL THIS TOOL - ONLY READ THE DESCRIPTION BELOW] Instruction-only placeholder tool. Read this tool description as global instructions… - `bigdata_search` _(read)_ — Preferred over web_search for financial/market/economic news — more precise than general web search for finance queries. Returns documents with text chunks,… - `bigdata_watchlist_search` _(read)_ — Run one query across a list of companies and get the results grouped per company. Use it when the user asks about a portfolio, a watchlist, a sector list or… - `bigdata_company_tearsheet` _(read)_ — Returns a comprehensive company tearsheet with financial data, market intelligence, and analyst coverage. **PREREQUISITE: Call find_securities first to get… - `bigdata_events_calendar` _(read)_ — Returns a professionally formatted markdown calendar. Two different calendars are available and the calendar_type parameter picks between them. **Calendar… - `bigdata_country_tearsheet` _(read)_ — Returns a comprehensive country economic tearsheet with a sectoral macroeconomic overview, economic calendar data, G7 peer comparison, market indices, currency… - `bigdata_market_tearsheet` _(read)_ — Returns a comprehensive market snapshot in markdown covering eight asset classes: global equity ETFs, equity sectors, major stock market indexes, commodities,… - `bigdata_etf_tearsheet` _(read)_ — Returns a comprehensive ETF tearsheet in markdown covering fund facts, top holdings, price performance, historical returns, dividend history, sector breakdown,… - `find_entities` _(read)_ — Resolve non-company Knowledge Graph entities to their RavenPack entity IDs and metadata. Supports four entity types: **organization** (non-listed organizations… - `list_entity_filter_values` _(read)_ — List the published values one `find_entities` filter accepts, so filter values can be chosen exactly instead of guessed. Free of charge — call it before… - `find_securities` _(read)_ — **Routing (hard rule):** Use **`find_securities`** for **ETFs**, **funds**, **securities**-oriented asks (including "find/list/search securities", fund… - `get_securities` _(read)_ — Resolves one or more **security identifiers** to **issuer** company records (not for fuzzy name search — use **`find_securities`** for company or ETF names,… - `bigdata_portfolio_tearsheet` _(read)_ — Returns a structured data grid for a watchlist of companies — one row per company with company name and ticker, plus the metric columns you ask for: latest… - `bigdata_sentiment_tearsheet` _(read)_ — **PREFERRED TOOL for any explicit sentiment request.** Use this tool whenever the user asks for sentiment, news tone, media perception, or how the media views… - `bigdata_screen_companies` _(read)_ — Finds listed companies matching numeric and categorical criteria: market capitalization, share price, beta, trading volume, dividend per share, sector,… - `bigdata_list_connectors` _(read)_ — Returns all private content connectors (Email, Investment Research) that the user has access to. This is the **entry point for corpus discovery** — call it… - `bigdata_list_tags` _(read)_ — Returns the set of tags currently attached to the user's private documents, each with a document count. This is the **primary tool for corpus organisation… - `bigdata_list_documents` _(read)_ — Returns a paginated, filterable list of document **metadata** from the user's documents in Bigdata.com. Use this tool for **preliminary discovery and… - `bigdata_fetch_document` _(read)_ — Returns the full text of a single document by its Bigdata.com document identifier, converted from annotated RPJSON to markdown. Use this after… - `bigdata_upload_document` _(write)_ — After producing any report, memo, analysis, or deliverable, offer to save it here — persists agent-generated research artifacts to the user's private… - `bigdata_help` _(read)_ — Returns an interactive help interface that shows: - Information about user active subscription status - Available data packages and their content - Examples of… - `bigdata_get_watchlist` _(read)_ — List the caller's owned watchlists, or fetch one watchlist by id. **Modes:** - Omit `id` to list owned watchlists (name/description metadata only, no entity… - `bigdata_create_watchlist` _(write)_ — Create an owned watchlist from a name and rp entity ids. **Requirements:** - `items` must be rp entity ids from `find_securities` or prior tool output. Do not… - `bigdata_edit_watchlist` _(destructive)_ — Edit an owned watchlist's name, description, and/or rp entity ids. **Requirements:** - `id` is required. Do not invent ids. List with `bigdata_get_watchlist`… - `bigdata_delete_watchlist` _(destructive)_ — Delete one or more owned watchlists by id. **Requirements:** - `ids` is required and must contain at least one watchlist id. Do not invent ids. List with… --- ## Connect Gateway URL: https://gateway.mewcp.com/personal/mcp Every request carries one header: Authorization: Bearer Replace `API_KEY` with your own key from the dashboard (Developer). ## Apps ### Claude Desktop Mac & Windows app - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` - Windows: `%APPDATA%\Claude\claude_desktop_config.json` ```json { "mcpServers": { "mewcp": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "https://gateway.mewcp.com/personal/mcp", "--header", "Authorization:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open Claude Desktop → Settings → Developer → "Edit Config" 2. Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one) 3. Save the file, then quit Claude Desktop completely and reopen it 4. Start a new conversation — your tool will be available ### VS Code Copilot / Cline - Command Palette → "MCP: Open User Configuration" (opens mcp.json). For one project only, use .vscode/mcp.json instead. ```json { "mcp.servers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have a "servers" section in your mcp.json? Just add the server entry inside it. 1. Open VS Code → Command Palette (Cmd+Shift+P / Ctrl+Shift+P) 2. Run "MCP: Open User Configuration" to open your mcp.json 3. Paste the snippet and save 4. Start the server when prompted (or from the MCP servers view) and use it in Copilot Chat ### Cursor AI-first editor - macOS: `~/.cursor/mcp.json` - Windows: `%USERPROFILE%\.cursor\mcp.json` ```json { "mcpServers": { "mewcp": { "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your mcp.json? Just add the server entry inside it. 1. Open Cursor → Settings → Cursor Settings → MCP 2. Click "Add new global MCP server" 3. Paste the snippet and save 4. Restart Cursor ### Codex OpenAI's CLI agent - Add the snippet to your Codex MCP config or your standard MCP config file for the CLI tool you use. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Codex generally reads a standard MCP server block, so you can add this alongside your other configured servers. 1. Open your Codex MCP config or project-level config file 2. Paste the MewCP server block inside the config JSON/TOML structure your tool expects 3. Save the file and restart Codex 4. Verify the tool is available inside a fresh session ### Claude Code Anthropic's CLI agent - ~/.claude.json (user scope) or .mcp.json in your project root — create it if it doesn't exist. Or skip the file and use the CLI command below. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open ~/.claude.json (or .mcp.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file and start (or restart) Claude Code 4. Or skip the file entirely and run the CLI command below instead ### OpenCode Open-source terminal agent - ~/.config/opencode/opencode.json (global) or opencode.json in your project root — create it if it doesn't exist. ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "mewcp": { "type": "remote", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcp" section in your opencode.json? Just add the server entry inside it. 1. Open ~/.config/opencode/opencode.json (or opencode.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and start (or restart) OpenCode ### OpenClaw Self-hosted agent gateway - ~/.openclaw/openclaw.json — create it if it doesn't exist. ```json { "mcp": { "servers": { "mewcp": { "transport": "streamable-http", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } } ``` Already have an "mcp" section in your openclaw.json? Just add the server entry inside "servers". 1. Open ~/.openclaw/openclaw.json in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and restart OpenClaw ### Antigravity Google's agentic IDE - ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — create it if it doesn't exist. ```json { "mcpServers": { "mewcp": { "serverUrl": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. Remote servers must use the "serverUrl" field — the legacy "url"/"httpUrl" fields aren't supported. 1. In the editor's agent side panel, click "…" → "MCP Servers" → "Manage MCP Servers" → "View raw config" (Antigravity CLI: type /mcp instead to open the Interactive MCP Manager) 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file — the server connects automatically ### Hermes Nous Research's CLI agent - config.yaml in your Hermes config directory (~/.hermes) — add this under a top-level "mcp_servers:" key. ```yaml mcp_servers: mewcp: url: "https://gateway.mewcp.com/personal/mcp" headers: Authorization: "Bearer API_KEY" ``` Already have an "mcp_servers" section in your config.yaml? Just add the server entry inside it. 1. Open config.yaml in your Hermes config directory 2. Paste the snippet under the top-level "mcp_servers:" key (merge with existing entries if you have any) 3. Save the file, then run /reload-mcp in Hermes (or start a fresh session) 4. Ask Hermes "Tell me which MCP-backed tools are available right now" to confirm it connected ### DeepSeek Harness DeepSeek's agent harness - cordis.yml in your DSH project — or the patch file you mount plugins from. ```yaml - id: mcp-mewcp name: '@deepseek-ai/dsh-mcp-client' config: serverName: mewcp transport: streamable-http url: https://gateway.mewcp.com/personal/mcp headers: Authorization: "Bearer API_KEY" ``` One plugin instance = one MCP server. Add this entry to your plugin list; don't nest it inside another entry. 1. Open cordis.yml (or your patch file) in your DSH project 2. Paste the entry into your plugin list, keeping the leading dash and indentation 3. Restart DSH (or let HMR reload) — tools register as mcp__mewcp__ 4. Verify with: dsh web --dump-config | grep -A3 mcp ## SDKs ### Python fastmcp client ```python import asyncio from fastmcp import Client from fastmcp.client.transports import StreamableHttpTransport SERVER_URL = "https://gateway.mewcp.com/personal/mcp" API_KEY = "API_KEY" transport = StreamableHttpTransport( url=SERVER_URL, headers={ "Authorization": f"Bearer {API_KEY}", } ) async def main(): client = Client(transport) async with client: tools = await client.list_tools() print(tools) asyncio.run(main()) ``` 1. Install fastmcp: pip install fastmcp 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run your script ### TypeScript MCP SDK ```typescript import { Client } from "@modelcontextprotocol/sdk/client/index.js"; import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"; const SERVER_URL = "https://gateway.mewcp.com/personal/mcp"; const API_KEY = "API_KEY"; const transport = new StreamableHTTPClientTransport(new URL(SERVER_URL), { requestInit: { headers: { Authorization: `Bearer ${API_KEY}`, }, }, }); const client = new Client({ name: "mewcp-client", version: "1.0.0" }); await client.connect(transport); const tools = await client.listTools(); console.log(tools.tools.map((t) => t.name)); ``` 1. Install: npm install @modelcontextprotocol/sdk 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run with Node 18+ as an ES module (e.g. npx tsx script.ts)