Alphasmo MCP Server

CLI + MCP server for SEC 13F institutional holdings, insider trading, and smart money convergence.

Local serverstdioPython

What is the Alphasmo MCP server?

CLI + MCP server for SEC 13F institutional holdings, insider trading, and smart money convergence. Exposed over MCP by the alphasmo mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Wire the MCP server into Claude Desktop, Claude Code, Cursor, or any MCP client (see below) and ask these in plain English — no code required.

  • 📊 13F institutional holdings — every hedge fund and asset manager's quarterly SEC filings: AUM, positions, and behavioral "personality scores" (concentration, turnover, sector conviction)
  • 🕵️ Insider trading (Form 4) — officer/director/10%-owner buys and sells, with a confidence score per ticker
  • 🚀 Smart money convergence — the flagship signal: tickers where 13F institutions and company insiders are both buying right now
  • 🤖 Built for AI agents — an MCP server out of the box, so Claude, ChatGPT, Cursor, or any MCP client can pull real financial data mid-conversation
  • 🆓 Free anonymous tier — no signup required to try it; get a free API key any time to raise your rate limit

Its toolset

Everything the assistant can do here goes through one of these:

  • Commands — Global flags on every command: --api-key (env ALPHASMO_API_KEY), --base-url (env ALPHASMO_BASE_URL), -f/--format json|compact|table|csv

Adding it to your client

alphasmo on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

You will need 2 environment variables: ALPHASMO_API_KEY, ALPHASMO_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Alphasmo's toolset — Commands — is a fair guide to whether it matches your workflow. It is maintained by alphasmo; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the alphasmo mcp server does with a few real requests.

Available tools

ToolWhat it does
CommandsGlobal flags on every command: --api-key <key> (env ALPHASMO_API_KEY), --base-url <url> (env ALPHASMO_BASE_URL), -f/--format json|compact|table|csv, --json (shorthand for --format json), --csv (shorthand for --format csv

How to install the Alphasmo MCP server

{
  "mcpServers": {
    "alphasmo-tools": {
      "command": "npx",
      "args": ["-y", "alphasmo"],
      "env": {
        "ALPHASMO_API_KEY": "your-value",
        "ALPHASMO_BASE_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
ALPHASMO_API_KEYCredential the server authenticates with.Yes
ALPHASMO_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Alphasmo to Commands.

Frequently asked questions

It connects Alphasmo to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Commands) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Alphasmo directly.