Massive.com MCP Server

The server includes built-in functions that can be applied to API results or query outputs using the apply parameter in call_api or query_data. You can discover all available functions by calling search_endpoints with scope="functions".

Available Categories:

• Greeks (Black-Scholes): bs_price, bs_delta, bs_gamma, bs_theta, bs_vega, bs_rho
• Returns: simple_return, log_return, cumulative_return, sharpe_ratio, sortino_ratio
• Technical Indicators: sma (simple moving average), ema (exponential moving average)

To integrate the Massive.com MCP server with Claude Desktop:

1. Install the server using uv:

uv tool install "mcp_massive @ git+https://github.com/massive-com/mcp_massive@v0.10.0"

2. Find the absolute path to the installed binary:

• Mac/Linux: which mcp_massive
• Windows: where mcp_massive

3. Add the server to your claude_desktop_config.json file. Replace <path_to_mcp_massive> with your binary path and <your_api_key_here> with your actual Massive.com API key.

{
    "mcpServers": {
        "massive": {
            "command": "<path_to_mcp_massive>",
            "env": {
                "MASSIVE_API_KEY": "<your_api_key_here>",
                "HOME": "<your_home_directory>"
            }
        }
    }
}

To use the Massive.com MCP server with Claude Code, follow these steps. Ensure you have Astral UV (v0.4.0+) and Python 3.12+ installed.

1. Install Claude Code via npm:

npm install -g @anthropic-ai/claude-code

2. Install the MCP server using uv tool install (this ensures fast startup by downloading dependencies ahead of time):

uv tool install "mcp_massive @ git+https://github.com/massive-com/mcp_massive@v0.10.0"

3. Register the server with Claude Code:

claude mcp add massive -e MASSIVE_API_KEY=your_api_key_here -- mcp_massive

To upgrade the server in the future, use:

uv tool upgrade mcp_massive

The API documentation supports consistent filter-operator suffixes for query parameters. When using the more detail level in Endpoint.format(), these are collapsed into a single annotation for the base parameter.

Supported Filter Operators:

• gt (greater than)
• gte (greater than or equal to)
• lt (less than)
• lte (less than or equal to)
• any_of (matches any in a list)
• all_of (matches all in a list)

Example parameter name in docs: market_cap.gt

When providing inputs to functions, the ParamKind determines how your input value is interpreted:

By default, the server uses stdio transport. You can change this using the MCP_TRANSPORT environment variable or the --transport CLI argument (the CLI argument takes precedence).

Using CLI argument:

MASSIVE_API_KEY=<your_api_key_here> uv run mcp_massive --transport streamable-http

Using Environment variable:

MCP_TRANSPORT=streamable-http MASSIVE_API_KEY=<your_api_key_here> uv run mcp_massive

Use the build_index function to asynchronously fetch and index the llms-full.txt documentation file.

By default, it looks for the MASSIVE_LLMS_TXT_URL environment variable. If not set, it uses a default URL.

Note: This process involves downloading the documentation, parsing endpoints, and initializing an in-memory SQLite FTS5 database.

import os
from mcp_massive.index import build_index

# Optional: Set the URL via environment variable
os.environ["MASSIVE_LLMS_TXT_URL"] = "https://example.com/llms-full.txt"

index = await build_index()

To debug or test the server, use the MCP Inspector. This provides a browser interface to interact with tools and view I/O.

Run the following command:

npx @modelcontextprotocol/inspector uv --directory /path/to/mcp_massive run mcp_massive

In the browser UI, select STDIO as the transport type and use uv with run mcp_massive as the arguments.

The mcp_massive service can be run using Docker Compose. It requires a MASSIVE_API_KEY environment variable to authenticate with the Massive API. When using Docker Compose, ensure the MASSIVE_API_KEY is set in your host environment or a .env file so it can be interpolated into the container.

services:
  mcp_massive:
    build: .
    volumes:
      - .:/app
    container_name: mcp_massive_server
    environment:
      - MASSIVE_API_KEY=${MASSIVE_API_KEY}
    stdin_open: true
    tty: true