Moltline TaxLots

Official8 tools

by GarphenGate · Python

Crypto cost-basis lots (FIFO/LIFO/HIFO/specific-ID), Form 8949 rows, 1099-DA diff. 5 of 8 free.

com.moltlinestudio/taxlots MCP Server

The com.moltlinestudio/taxlots server provides crypto cost-basis lots supporting FIFO, LIFO, HIFO, and specific-ID strategies. It produces Form 8949 rows and includes 1099-DA diff information (diff 5 of 8). The server is described as part of a dependency-free stdio bridge to Moltline Studio’s hosted MCP servers.

🛠️ Key Features

Crypto cost-basis lots with FIFO, LIFO, HIFO, and specific-ID
Form 8949 row generation
1099-DA diff (diff 5 of 8)
8 tools available

🚀 Use Cases

Preparing Form 8949 reporting rows from crypto lot data
Computing a specific 1099-DA difference set (diff 5 of 8)

⚡ Developer Benefits

Exposes 8 tools from the hosted MCP server
Part of an MCP fleet reachable via Streamable HTTP (when supported)

⚠️ Limitations

1099-DA coverage is limited to diff 5 of 8 (as described)
The stdio bridge is intended for clients that only support stdio transport

Topics

agent-skillsai-agentsclaudemcpmcp-servermodel-context-protocol

Captured live from the server via tools/list.

parse_transactions

Normalise an exchange CSV export into the canonical ledger rows. FREE. Supports the Coinbase transaction-history export (Transaction Type / Asset / Quantity Transacted columns), the Kraken ledgers export (txid / refid / type / asset / amount / fee) and a generic CSV with the canonical columns ts, type, asset, qty, fiat_value, fee_qty, fee_asset, fee_fiat, counter_asset, counter_qty, account, id. Typical input {"csv_text": "...", "source_hint": "coinbase"} returns {"rows": [...], "detected": "coinbase", "unrecognised": [...], "warnings": [...]}. Rows it cannot read are returned under unrecognised with the reason, never dropped silently. In every row qty is the whole amount that entered or left the account; when a fee was paid in the same asset, fee_qty is the part of qty that was the fee. Use before ledger_lint and build_lots. Not for other exchanges: convert those to the generic columns first. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "csv_text must be the CSV file contents"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Parameters3

csv_text	string	required	the CSV file contents (up to 2 MB).
source_hint	string	optional	coinbase, kraken or generic; empty to detect from the header.
account	string	optional	account label to stamp on every row (defaults to the source name).

Raw schema

{
  "type": "object",
  "properties": {
    "csv_text": {
      "type": "string",
      "description": "the CSV file contents (up to 2 MB)."
    },
    "source_hint": {
      "default": "",
      "type": "string",
      "description": "coinbase, kraken or generic; empty to detect from the header."
    },
    "account": {
      "default": "",
      "type": "string",
      "description": "account label to stamp on every row (defaults to the source name)."
    }
  },
  "required": [
    "csv_text"
  ],
  "additionalProperties": false
}

ledger_lint

Find the problems that break a lot build: missing values, duplicates, negative balances. FREE. Typical input {"ledger": <rows from parse_transactions>} returns {"issues": [{"severity": "error", "row": "cb12", "issue": "sell of 0.5 BTC exceeds balance 0.2 in account coinbase"}], "balances": {"coinbase": {"BTC": "0.2"}}, "counts": {...}}. Balances are running quantities per account and asset in time order, ignoring transfers' fiat values. Use after parse_transactions and before build_lots. Not a tax check: it checks the ledger's arithmetic consistency only. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Parameters1

ledger

array

required

canonical rows (ts, type, asset, qty, fiat_value, fees, account...).

Raw schema

{
  "type": "object",
  "properties": {
    "ledger": {
      "items": {
        "additionalProperties": true,
        "type": "object"
      },
      "type": "array",
      "description": "canonical rows (ts, type, asset, qty, fiat_value, fees, account...)."
    }
  },
  "required": [
    "ledger"
  ],
  "additionalProperties": false
}

match_transfers

Pair withdrawals with the deposits that received them between your own accounts. FREE. Typical input {"ledger": <rows>, "window_minutes": 1440} returns {"pairs": [{"out": "kr91", "in": "cb14", "asset": "BTC", "from": "kraken", "to": "coinbase", "network_fee": "0.0001", "minutes": 42.0}], "unmatched": {"transfer_out": [...], "transfer_in": [...]}}. A pair needs the same asset, a different account, the deposit inside the window after the withdrawal, and a quantity within tolerance_pct of the amount sent net of the fee. Use before build_lots so basis and holding period move with the coins instead of being treated as a sale. Not for transfers to third parties: those stay unmatched and should be typed gift_out or sell. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Parameters3

ledger	array	required	canonical rows.
window_minutes	integer	optional	how long after the withdrawal the deposit may land (default one day).
tolerance_pct	number	optional	allowed quantity difference in percent after the fee (default 1).

Raw schema

{
  "type": "object",
  "properties": {
    "ledger": {
      "items": {
        "additionalProperties": true,
        "type": "object"
      },
      "type": "array",
      "description": "canonical rows."
    },
    "window_minutes": {
      "default": 1440,
      "maximum": 20160,
      "minimum": 1,
      "type": "integer",
      "description": "how long after the withdrawal the deposit may land (default one day)."
    },
    "tolerance_pct": {
      "default": 1,
      "maximum": 25,
      "minimum": 0,
      "type": "number",
      "description": "allowed quantity difference in percent after the fee (default 1)."
    }
  },
  "required": [
    "ledger"
  ],
  "additionalProperties": false
}

build_lots

Build the lot inventory per account and every disposal with basis, gain and holding period. PREMIUM (license). Methods: fifo (the default rule when no specific identification is made, Treas. Reg. 1.1012-1(j)), lifo, hifo, or specific_id via a row's specific_lots {lot_id: qty}. Typical input {"ledger": <rows>, "method": "hifo", "transfers": <pairs from match_transfers>} returns {"disposals": [{"row": "cb9", "asset": "BTC", "qty": "0.5", "proceeds": "31000.00", "basis": "20000.00", "gain": "11000.00", "term": "long", ...}], "open_lots": [...], "summary": {"short_term": {...}, "long_term": {...}}}. Fees: a cash purchase's fee joins basis; a sale's or exchange's fee reduces the amount realized (1.1001-7); a network fee paid in the transferred asset is a disposal of those units (transfer_fee_policy dispose) unless you choose ignore. Transfers between your own accounts move lots with their basis and acquisition date. Use once ledger_lint reports no errors. Not tax advice: it applies the stated rules to your rows and shows its work. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "method must be fifo, lifo, hifo or specific_id"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Parameters6

ledger	array	required	canonical rows.
method	string	optional	fifo, lifo, hifo or specific_id (rows without specific_lots fall back to fifo).
transfers	array	optional	pairs from match_transfers ({"out": id, "in": id, ...}); empty to auto-match with the defaults.
on_missing_lots	string	optional	error (default), or zero_basis for lenient mode - disposals beyond the lots held get zero basis and unmatched transfer_out rows simply leave the inventory, each flagged.
transfer_fee_policy	string	optional	dispose (default) or ignore for network fees paid in the transferred asset.
tax_year	integer	optional	when set, only disposals in that calendar year are returned (the inventory still runs from the start).

Raw schema

{
  "type": "object",
  "properties": {
    "ledger": {
      "items": {
        "additionalProperties": true,
        "type": "object"
      },
      "type": "array",
      "description": "canonical rows."
    },
    "method": {
      "default": "fifo",
      "type": "string",
      "description": "fifo, lifo, hifo or specific_id (rows without specific_lots fall back to fifo)."
    },
    "transfers": {
      "default": [],
      "items": {
        "additionalProperties": true,
        "type": "object"
      },
      "type": "array",
      "description": "pairs from match_transfers ({\"out\": id, \"in\": id, ...}); empty to auto-match with the defaults."
    },
    "on_missing_lots": {
      "default": "error",
      "type": "string",
      "description": "error (default), or zero_basis for lenient mode - disposals beyond the lots held get zero basis and unmatched transfer_out rows simply leave the inventory, each flagged."
    },
    "transfer_fee_policy": {
      "default": "dispose",
      "type": "string",
      "description": "dispose (default) or ignore for network fees paid in the transferred asset."
    },
    "tax_year": {
      "default": 0,
      "maximum": 2100,
      "minimum": 2009,
      "type": "integer",
      "description": "when set, only disposals in that calendar year are returned (the inventory still runs from the start)."
    }
  },
  "required": [
    "ledger"
  ],
  "additionalProperties": false
}

form_8949_rows

Lay the disposals out as Form 8949 rows with box categories and totals. PREMIUM (license). Typical input {"disposals": <from build_lots>, "tax_year": 2026, "default_reporting": "proceeds_only"} returns {"part_i": {"B": [rows]}, "part_ii": {"E": [rows]}, "totals": {...}}. Columns follow the form: description (a), date acquired (b), date sold (c), proceeds (d), cost or other basis (e), code (f), adjustment (g), gain or loss (h). Box: A/D when the broker reported proceeds and basis, B/E when proceeds only, C/F when no broker form - set per row in reporting {row_id: value} or for all rows with default_reporting. Use to draft the schedule from computed disposals. Not a filing: check the current form instructions. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "disposals must be a non-empty list from build_lots"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Parameters5

disposals	array	required	rows from build_lots.
tax_year	integer	required	the calendar year of the disposals to include.
reporting	object	optional	per-row override: proceeds_and_basis, proceeds_only or none.
default_reporting	string	optional	proceeds_and_basis, proceeds_only or none (default).
whole_dollars	boolean	optional	round each row to whole dollars as the form permits.

Raw schema

{
  "type": "object",
  "properties": {
    "disposals": {
      "items": {
        "additionalProperties": true,
        "type": "object"
      },
      "type": "array",
      "description": "rows from build_lots."
    },
    "tax_year": {
      "maximum": 2100,
      "minimum": 2009,
      "type": "integer",
      "description": "the calendar year of the disposals to include."
    },
    "reporting": {
      "additionalProperties": true,
      "default": {},
      "type": "object",
      "description": "per-row override: proceeds_and_basis, proceeds_only or none."
    },
    "default_reporting": {
      "default": "none",
      "type": "string",
      "description": "proceeds_and_basis, proceeds_only or none (default)."
    },
    "whole_dollars": {
      "default": false,
      "type": "boolean",
      "description": "round each row to whole dollars as the form permits."
    }
  },
  "required": [
    "disposals",
    "tax_year"
  ],
  "additionalProperties": false
}

reconcile_1099da

Diff the broker's 1099-DA lines against the computed disposals. PREMIUM (license). Typical input {"disposals": <from build_lots>, "form_rows": [{"asset": "BTC", "date_sold": "2026-03-04", "qty": "0.5", "proceeds": "31000", "basis": "", "account": "coinbase"}]} returns {"matched": [...], "broker_missing_basis": [...], "basis_mismatch": [...], "proceeds_mismatch": [...], "unmatched_form_rows": [...], "unmatched_disposals": [...]}. A line matches a disposal on the same account (when given), asset and sale date with quantity and proceeds inside the tolerances; several lots sold in one order are summed first. Use when the form arrives and the basis column is blank for coins that came from your own wallet. Not a substitute for the broker's statement. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "disposals must be a non-empty list from build_lots"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Parameters4

disposals	array	required	rows from build_lots.
form_rows	array	required	1099-DA lines: asset, date_sold, qty, proceeds, basis (may be blank), account (optional), id (optional).
qty_tolerance_pct	number	optional	allowed quantity difference in percent (default 0.5).
money_tolerance	number	optional	allowed proceeds/basis difference in fiat units (default 1.00).

Raw schema

{
  "type": "object",
  "properties": {
    "disposals": {
      "items": {
        "additionalProperties": true,
        "type": "object"
      },
      "type": "array",
      "description": "rows from build_lots."
    },
    "form_rows": {
      "items": {
        "additionalProperties": true,
        "type": "object"
      },
      "type": "array",
      "description": "1099-DA lines: asset, date_sold, qty, proceeds, basis (may be blank), account (optional), id (optional)."
    },
    "qty_tolerance_pct": {
      "default": 0.5,
      "maximum": 10,
      "minimum": 0,
      "type": "number",
      "description": "allowed quantity difference in percent (default 0.5)."
    },
    "money_tolerance": {
      "default": 1,
      "maximum": 1000,
      "minimum": 0,
      "type": "number",
      "description": "allowed proceeds/basis difference in fiat units (default 1.00)."
    }
  },
  "required": [
    "disposals",
    "form_rows"
  ],
  "additionalProperties": false
}

wash_window_check

Flag loss disposals with a repurchase of the same asset inside the window. FREE. Typical input {"disposals": <from build_lots>, "acquisitions": [{"asset": "ETH", "ts": "2026-02-10T10:00:00Z", "qty": "2"}]} returns {"flags": [{"row": "cb7", "asset": "ETH", "loss": "-410.00", "repurchases": [...]}], "rule_status": "..."}. The 30-day window before and after the sale is the one IRC 1091 uses for stock or securities; as checked on the verification date that statute had not been extended to digital assets that are not securities, so the output is a heads-up for planning, not an adjustment. Use when reviewing loss harvesting. Not a determination that any rule applies. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "disposals and acquisitions must be lists"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Parameters3

disposals	array	required	rows from build_lots (uses asset, disposed_at, gain, row).
acquisitions	array	required	purchases/income rows with asset, ts, qty (ledger rows work as-is).
window_days	integer	optional	days before and after the loss disposal to scan (default 30).

Raw schema

{
  "type": "object",
  "properties": {
    "disposals": {
      "items": {
        "additionalProperties": true,
        "type": "object"
      },
      "type": "array",
      "description": "rows from build_lots (uses asset, disposed_at, gain, row)."
    },
    "acquisitions": {
      "items": {
        "additionalProperties": true,
        "type": "object"
      },
      "type": "array",
      "description": "purchases/income rows with asset, ts, qty (ledger rows work as-is)."
    },
    "window_days": {
      "default": 30,
      "maximum": 90,
      "minimum": 1,
      "type": "integer",
      "description": "days before and after the loss disposal to scan (default 30)."
    }
  },
  "required": [
    "disposals",
    "acquisitions"
  ],
  "additionalProperties": false
}

lp_position_math

Impermanent loss, hold-vs-pool value and basis split for a two-asset constant-product pool. FREE. Typical input {"deposit": {"asset_a": "ETH", "qty_a": "1", "price_a": "2000", "asset_b": "USDC", "qty_b": "2000", "price_b": "1"}, "current_prices": {"ETH": "3000", "USDC": "1"}} returns {"il_pct": "-2.02", "hold_value": "5000.00", "pool_value": "4898.98", "deposit_value": "4000.00", "basis_split": {...}}. The pool value assumes x*y=k with no fees; add fees_earned_fiat to see the net. The basis split is the deposit's fiat value at deposit, allocated by each side's share, which is the arithmetic a lot engine needs if the LP position is treated as one asset. Use for DeFi position reviews. Not a determination of whether the deposit is a taxable exchange. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "deposit and current_prices must be objects"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Parameters3

deposit	object	required	asset_a, qty_a, price_a, asset_b, qty_b, price_b at the time of deposit.
current_prices	object	required	{asset: price} for both assets now.
fees_earned_fiat	number	optional	fees accrued to the position, in fiat.

Raw schema

{
  "type": "object",
  "properties": {
    "deposit": {
      "additionalProperties": true,
      "type": "object",
      "description": "asset_a, qty_a, price_a, asset_b, qty_b, price_b at the time of deposit."
    },
    "current_prices": {
      "additionalProperties": true,
      "type": "object",
      "description": "{asset: price} for both assets now."
    },
    "fees_earned_fiat": {
      "default": 0,
      "minimum": 0,
      "type": "number",
      "description": "fees accrued to the position, in fiat."
    }
  },
  "required": [
    "deposit",
    "current_prices"
  ],
  "additionalProperties": false
}

README.md9 KBView on GitHub

moltline-mcp

A thin, dependency-free stdio bridge to Moltline Studio's fleet of 22 hosted MCP servers.

Most modern MCP clients can connect to the fleet directly over Streamable HTTP — no install needed (see Direct connection below). This bridge exists for clients that only speak the stdio transport: it proxies newline-delimited JSON-RPC between your client and the hosted server, verbatim, with no telemetry and no dependencies beyond the Python 3.9+ standard library.

160 tools across 22 servers; 110 are free.
Free tier: no registration, no account, no credentials — connect and call tools immediately.
Premium tools are unlocked with a Moltline license. Set MOLTLINE_LICENSE in your MCP client's environment; the bridge sends it as the X-Moltline-License header and never writes it to argv, URLs or logs. See auth.md.
Independently checked by MCPize on the direct endpoints (scans of 5–6 September 2026: 6 A+, 15 A, 1 B+; scores 89–98). All 22 servers score 100 on clarity, 100 on reliability and 100 on trust, 95 on protocol and 87 on safety; the one finding raised on every server is that the free tier accepts anonymous access — which is the point of it — and the spread between servers sits in MCPize's "Market" dimension (a crowded category). Each server's MCPize listing links its own public result.

Find it on: Smithery · MCPize · Glama · Clawmart · MCP Registry

The fleet

Server	Tools	What it does
`catalog`	10	Search 138 agent skills and personas by plain-language job; preview any product.
`codereview`	7	Risk-scan a diff, flag AI-generated-code tells, find secrets, report complexity.
`govern`	8	Audit an MCP config or SKILL.md for over-broad scope and prompt-injection risk.
`timeops`	5	Business days, meeting overlap, recurrence expansion, deadline and SLA math.
`data`	7	Paste-your-data analytics: CSV profiling, A/B tests, correlation, growth, cohorts.
`humanizer`	5	Find AI-isms with evidence, fingerprint a writing voice, measure burstiness.
`business`	8	30 finance, bookkeeping, legal-ops and SMB operations persona-skill products.
`creator`	8	20 blogging, brand-voice, copywriting, video and social persona-skill products.
`educator`	7	8 curriculum, classroom, accommodations and exam-prep persona-skill products.
`outbound`	8	7 outreach, sequencing, deliverability, call-coaching and CRM-hygiene products.
`personal`	9	20 inbox, calendar, travel, meals and family-logistics persona-skill products.
`research`	8	7 research navigation, thesis, note-taking and citation persona-skill products.
`skillmd-lint`	6	Lint a SKILL.md for frontmatter, structure, secrets and size. All tools free.
`merchant`	6	Commerce arithmetic: processor fees, charge-to-net, invoice totals, proration.
`shipping`	6	Dimensional weight, parcel fit, landed cost, freight class, rate cards.
`shopify`	6	Check a product CSV, URL handles, variant matrices and metafield keys.
`dropship`	6	Dropshipping unit economics: margin, lead time, SKU mapping, price ladders.
`recall`	6	A portable knowledge-graph memory you pass in and get back. No database.
`vision`	6	Image header probing, bbox conversion, resize plans, color and detection math.
`regclock`	9	Incident-reporting deadlines from the legal text (EU CRA, NIS2, DORA, GDPR, UK GDPR, HIPAA, SEC 8-K), cited.
`taxlots`	8	Crypto cost basis: parse exchange CSVs, lint, match transfers, FIFO/LIFO/HIFO lots, Form 8949 rows, 1099-DA diff.
`optimize`	11	OR-Tools routing, 3-D packing, 1-D/2-D cutting, knapsack and shift rostering with stated limits.

Machine-readable discovery: api-catalog · per-server card at https://mcp.moltlinestudio.com/<server>/.well-known/mcp/server-card.json · fleet health.

Direct connection (preferred)

If your MCP client supports Streamable HTTP (Claude Desktop, Claude Code, Cursor, and most current clients do), point it straight at the hosted endpoint — nothing to install:

json

{
  "mcpServers": {
    "moltline-timeops": {
      "type": "http",
      "url": "https://mcp.moltlinestudio.com/timeops"
    }
  }
}

Swap timeops for any slug in the table above.

The stdio bridge (for stdio-only clients)

Install

Run directly (recommended) — the bridge is a single stdlib-only file, so a clone is all you need:

bash

git clone https://github.com/GarphenGate/moltline-mcp.git
python3 moltline-mcp/moltline_mcp.py timeops   # any of the 22 slugs; default: catalog

Docker — see Docker below if you prefer a container.

A PyPI package is planned; until then, use the methods above.

Client configuration

Point your MCP client at the script with an absolute path:

json

{
  "mcpServers": {
    "moltline-timeops": {
      "command": "python3",
      "args": ["/absolute/path/to/moltline-mcp/moltline_mcp.py", "timeops"]
    }
  }
}

Or run it through Docker (after docker build -t moltline-mcp .):

json

{
  "mcpServers": {
    "moltline-timeops": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "moltline-mcp", "timeops"]
    }
  }
}

CLI

text

python3 moltline_mcp.py [server] [--timeout SECONDS] [--list] [--version]

server — one of the 22 slugs (default catalog); anything else fails fast with the valid list.
--timeout — per-request timeout in seconds (default 300, or env MOLTLINE_TIMEOUT).
--list — print the server slugs and exit.
Env MOLTLINE_BASE_URL — override the fleet base URL (for testing).
Env MOLTLINE_LICENSE — your Moltline license, sent as the X-Moltline-License header to unlock premium tools. Omit it and the bridge runs free-tier only.
Env MOLTLINE_DEBUG=1 — diagnostic logging on stderr (stdout stays protocol-clean). The license is never logged; debug output reports only whether one is configured.

Docker

The bridge also runs containerized (stdio in, network egress to the fleet required):

bash

docker build -t moltline-mcp .
docker run -i --rm moltline-mcp timeops   # any of the 22 slugs; default: catalog

See Client configuration for the matching mcpServers entry.

How it works

One process per server connection. Each JSON-RPC message read from stdin is POSTed to https://mcp.moltlinestudio.com/<server>; JSON and SSE-framed responses are relayed back to stdout as newline-delimited JSON. The bridge tracks the server-assigned Mcp-Session-Id and echoes the negotiated MCP-Protocol-Version, per the Streamable HTTP transport spec. It never inspects, stores, or reports your traffic.

Tests

The bridge ships with an offline test suite - no network, no dependencies:

bash

python -m unittest -v

Twenty-two tests cover the parts that actually break in a transport bridge: newline-delimited framing, SSE event splitting (multiple events, multi-line data: payloads, a trailing event with no blank line, comments and named events), session-id capture and reuse, protocol-version negotiation on initialize only, and error relay - a JSON-RPC error document is passed through verbatim, anything else becomes a well-formed -32603. CI runs them on Python 3.9, 3.12 and 3.13, plus a Docker build and container smoke test.

Access and licensing

Free tier — anonymous. No registration or credentials; all free tools work immediately.
Premium — unlocked with a Moltline license purchased (human-in-the-loop) at moltlinestudio.com. Set MOLTLINE_LICENSE in the environment and the bridge forwards it as the X-Moltline-License request header. It is deliberately not a command-line flag: argv is world-readable through ps. It is never placed in a URL and never logged. Details: auth.md.

License

Install

Tools (8)

parse_transactionsledger_lintmatch_transfersbuild_lotsform_8949_rowsreconcile_1099dawash_window_checklp_position_math

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp.moltlinestudio.com/taxlots

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "taxlots": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.moltlinestudio.com/taxlots"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

Moltline TaxLots

com.moltlinestudio/taxlots MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

parse_transactions

ledger_lint

match_transfers

build_lots

form_8949_rows

reconcile_1099da

wash_window_check

lp_position_math

moltline-mcp

The fleet

Direct connection (preferred)

The stdio bridge (for stdio-only clients)

Install

Client configuration

CLI

Docker

How it works

Tests

Access and licensing

Links

License

Install

Remote endpoint

Related servers