Almanex MCP server

Model Context Protocol

MCP is an open protocol for exposing tools and resources to LLM-based agents. The Almanex MCP server adapts our HTTP API into MCP tools, so any MCP-aware client (Claude Desktop, Claude Code, Cursor, etc.) can search the corpus and pull source-grounded reports without you writing glue code.

Run the server

The MCP server is published as the npm package almanex-mcp. npx downloads and runs it on demand:

npx -y almanex-mcp

The server reads your API key from the ALMANEX_API_KEY environment variable.

Claude Desktop

Open Settings → Developer → Edit Config. Add the almanex entry to claude_desktop_config.json:

{
  "mcpServers": {
    "almanex": {
      "command": "npx",
      "args": ["-y", "almanex-mcp"],
      "env": { "ALMANEX_API_KEY": "alm_live_YOUR_KEY" }
    }
  }
}

Replace alm_live_YOUR_KEY with a real key from /account. Restart Claude Desktop after saving.

Claude Code

Project-level: drop a .mcp.json at the repo root. Same shape:

{
  "mcpServers": {
    "almanex": {
      "command": "npx",
      "args": ["-y", "almanex-mcp"],
      "env": { "ALMANEX_API_KEY": "alm_live_YOUR_KEY" }
    }
  }
}

Cursor

Cursor reads MCP servers from ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project). Same JSON works:

{
  "mcpServers": {
    "almanex": {
      "command": "npx",
      "args": ["-y", "almanex-mcp"],
      "env": { "ALMANEX_API_KEY": "alm_live_YOUR_KEY" }
    }
  }
}

Tools the server exposes

• list_reports
  List reports with filters (ticker, sector, query) and pagination.
• get_ticker_reports
  All reports for a ticker, newest first.
• get_report
  Full report body + sources + tags by ticker and slug.
• search_reports
  Full-text search across the corpus, returns matched titles + snippets.
• whoami
  Echo the calling key's user, plan, and remaining monthly quota.