开源MCP工具：MaverickMCP

Prerequisites

• Python 3.12+: Core runtime environment
• uv: Modern Python package manager (recommended)
• Redis (optional, for enhanced caching)
• PostgreSQL or SQLite (optional, for data persistence; SQLite is the default)

Installing uv (Recommended)

```bash

Install dependencies and create virtual environment in one command

uv sync --extra dev

Skip the setup — hosted version

Self-hosting MaverickMCP means Python, uv, and MCP client config (Redis and a research LLM key are optional). If you just want the analysis, Capital Companion is the hosted product built on the same engine: AI technical analysis, trade-plan review sheets with outcome tracking, and price alerts. 25 free analyses, no credit card.

Self-hosting instructions continue below.

Installation

Note: The package is not on PyPI yet. The name maverick-mcp-server is held by a dormant, unrelated project, and a PEP 541 name-transfer request is pending with PyPI. Until this note is gone, do not pip install maverick-mcp-server or uvx --from maverick-mcp-server: that name is not ours, and whatever its current owner publishes is what you would get. Use Option 1 (uvx from the release tag), Option 2 (the GHCR image), or Option 3 (from source).

Option 1: Run without installing (uvx from the release tag)

```bash

Docker (Optional)

For containerized deployment:

```bash

Using uv in Docker (recommended for faster builds)

docker build -t maverick-mcp-server . docker run -p 8003:8000 --env-file .env maverick-mcp-server

Or start with docker-compose

docker-compose up -d ```

Note: The Dockerfile uses uv for fast dependency installation. The image ships the [backtesting] and [research] extras by default; drop --extra backtesting --extra research from the uv sync line in the Dockerfile for a smaller, core-only image. There is no HTTP /health endpoint or HEALTHCHECK -- this is an MCP server, not a REST API.

Quick Start

Usage Examples

Once connected to Claude Desktop, use natural language:

--env-file is optional (core tools need no keys)

docker run --rm -p 8003:8000 --env-file .env ghcr.io/wshobson/maverick-mcp:1.1.0

Drop `[backtesting,research]` for a smaller, core-only install (37 tools,
no backtesting/research tools registered).

#### Option 3: From source with uv (for development)

Copy environment template

cp .env.example .env

Configure DATABASE_URL / LLM_PROVIDER / EXA_API_KEY as needed (all optional)

```

Configuration

Configure MaverickMCP via .env file or environment variables. See .env.example for the complete, code-verified list.

Essential Settings:

- DATABASE_URL - PostgreSQL connection or sqlite:///maverick.db for SQLite (default). - REDIS_HOST - enables Redis caching when set; caching falls back to in-memory/SQLite otherwise. - LOG_LEVEL - Logging verbosity (default: INFO).

No API key is required to run the core server; stock data comes from yfinance.

Optional (research extra, bring your own key):

• LLM_PROVIDER - anthropic, openai, openrouter, or openai_compatible.
• LLM_API_KEY - API key for the configured LLM_PROVIDER.
• LLM_MODEL - Model name for the configured LLM_PROVIDER.
• LLM_BASE_URL - Base URL override, required when LLM_PROVIDER=openai_compatible.
• LLM_TEMPERATURE - Sampling temperature (default: 0.0).
• EXA_API_KEY - Web search for the research tools (get at exa.ai).
• RESEARCH_SEARCH_BACKEND - exa (default) or searxng.
• SEARXNG_BASE_URL - Base URL of a self-hosted SearXNG instance with the JSON format enabled; used when the backend is searxng.

Migrating an older .env (legacy OPENROUTER_API_KEY-style auto-detection, TIINGO_API_KEY, etc.)? See docs/runbooks/migrating-to-v1.md.

Copy and configure environment

cp .env.example .env

Alternative: via pip

pip install uv ```

Troubleshooting