Skip to main content
Glama
Mintline MCP Server

Mintline MCP Server

by mintlineai

Mintline MCP Server

Connect AI assistants to your Mintline receipts and transactions via the Model Context Protocol.

MCP Registry mcp.so npm

Installation

npm install -g @mintline/mcp

Related MCP server: bank-mcp

Setup

1. Get your API key

Create an API key at mintline.ai/app/settings/api-keys

2. Configure Claude Desktop

Add to your ~/.claude/claude_desktop_config.json:

{
  "mcpServers": {
    "mintline": {
      "command": "mintline-mcp",
      "env": {
        "MINTLINE_API_KEY": "ml_live_your_api_key_here"
      }
    }
  }
}

3. Restart Claude Desktop

The Mintline tools will now be available.

Available Tools

Tools are loaded dynamically from the Mintline API and stay automatically in sync.

View all available tools:

Example Prompts

Receipts & Transactions

  • "Show me my unmatched receipts"

  • "Find receipts from Amazon"

  • "List transactions from my Chase statement"

  • "Show details for receipt rcpt_01abc123"

Matching

  • "What matches need my review?"

  • "Confirm the top match"

  • "Reject match mtch_01xyz789 - wrong vendor"

Analytics

  • "How much did I spend this month?"

  • "What are my top vendors by spending?"

  • "Show me spending trends for the last 6 months"

  • "Break down my spending by week"

  • "How much did I spend at AWS last quarter?"

  • "What needs my attention?" (shows unmatched items)

  • "Do I have any large transactions without receipts?"

Environment Variables

Variable

Required

Description

MINTLINE_API_KEY

Yes

Your Mintline API key

MINTLINE_API_URL

No

API URL (default: https://api.mintline.ai)

Development

git clone https://github.com/mintlineai/mintline-mcp.git
cd mintline-mcp
npm install

# Run locally
MINTLINE_API_KEY=ml_live_... node src/index.js

License

MIT

Available Tools

36 tools
confirm_matchB

Confirm match. Confirm a proposed match between a receipt and transaction. This action is billable and counts toward your plan usage.

Inputs: id (required).

confirm_matchesA

Confirm multiple matches. Confirm multiple proposed matches at once. Useful for batch-confirming all proposed matches for a statement.

Inputs: ids (required).

create_exportA

Create export. Create a new export job. The export will be processed asynchronously. Poll the job status or use webhooks to know when it's ready.

Inputs: statementId (required), includeUnmatched (required).

create_tagD

Create tag. Create a new tag.

Inputs: name (required), color.

delete_receiptA

Delete receipt. Permanently delete a receipt. This cannot be undone.

Inputs: id (required).

delete_tagA

Delete tag. Delete a tag and remove it from all tagged items.

Inputs: id (required).

get_exportB

Get export. Retrieve export job status and download URL. The download URL is a signed S3 URL that expires in 1 hour.

Inputs: id (required).

get_receiptA

Get receipt. Retrieve a single receipt by ID with full details including line items and matched transaction.

Inputs: id (required).

get_statementB

Get statement. Retrieve a single statement with summary information.

Inputs: id (required).

get_statement_match_statsB

Get statement match stats. Get matching statistics for a statement — how many transactions are matched, unmatched, etc.

Inputs: id (required).

get_statement_transactionsB

Get statement transactions. Retrieve all transactions for a specific statement.

Inputs: id (required).

get_transactionB

Get transaction. Retrieve a single transaction by ID with full details.

Inputs: id (required).

get_transaction_matchesB

Get matches for transaction. Get all match candidates (proposed + confirmed) for a specific transaction with receipt details and confidence scores.

Inputs: transactionId (required).

hide_receiptA

Hide receipt. Hide a receipt from matching and default views. Hidden receipts can be restored.

Inputs: id (required).

hide_statementA

Hide statement. Hide a bank statement from the default view. Hidden statements can be unhidden later.

Inputs: id (required).

hide_transactionB

Hide transaction. Hide a transaction from matching and default views.

Inputs: id (required).

list_exportsB

List exports. Retrieve a list of export jobs.

Inputs: limit (required), offset (required).

list_matchesA

List matches. Retrieve match candidates between receipts and transactions. Use this to review proposed matches or see confirmed/rejected history.

Inputs: limit (required), offset (required), status, minConfidence.

list_receiptsB

List receipts. Retrieve a paginated list of receipts with optional filtering and sorting.

Inputs: limit (required), offset (required), order (required), search, +2 more.

list_skip_reasonsA

List skip reasons. Get available skip reasons (bank fee, salary, tax, etc.).

Inputs: no named parameters.

list_statementsB

List statements. Retrieve a list of uploaded bank statements.

Inputs: limit (required), offset (required).

list_tagsA

List tags. Retrieve all tags for the authenticated user.

Inputs: no named parameters.

list_transactionsC

List transactions. Retrieve a paginated list of bank transactions.

Inputs: limit (required), offset (required), search, statementId, +1 more.

manual_matchA

Manual match. Manually create and confirm a match between a transaction and receipt when there is no proposed match.

Inputs: transactionId (required), receiptId (required).

reject_matchB

Reject match. Reject a proposed match. The receipt and transaction won't be suggested as a match again.

Inputs: id (required), reason.

search_receiptsA

Search receipts by amount and date. Search for receipts matching an amount range and/or date range. Useful for finding potential matches for unmatched transactions.

Inputs: minAmount, maxAmount, dateFrom, dateTo, +3 more.

skip_transactionA

Skip transaction. Mark a transaction as 'no receipt needed' (e.g. bank fees, salary, tax, internal transfers). Rejects any proposed matches.

Inputs: id (required), reason.

spending_summaryC

Get spending summary. Get spending summary with flexible grouping by vendor, month, week, or day. Returns totals, averages, and breakdowns for the specified period.

Inputs: groupBy (required), limit (required), dateFrom, dateTo, +1 more.

top_vendorsA

Get top vendors. Get a ranked list of vendors by total spending amount.

Inputs: limit (required).

unhide_receiptB

Unhide receipt. Restore a hidden receipt to active status.

Inputs: id (required).

unhide_statementB

Unhide statement. Unhide a previously hidden bank statement.

Inputs: id (required).

unhide_transactionB

Unhide transaction. Restore a hidden transaction to active status.

Inputs: id (required).

unmatched_summaryA

Get unmatched summary. Get a summary of unmatched receipts and transactions, including action items that need attention.

Inputs: no named parameters.

unmatch_transactionA

Unmatch transaction. Undo a confirmed match on a transaction. If within the grace period, usage is reversed.

Inputs: transactionId (required).

unskip_transactionA

Unskip transaction. Undo a skip — mark a transaction as needing a receipt again.

Inputs: id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 36 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear pairs like hide/unhide and skip/unskip. Minor potential overlap between list_matches and get_transaction_matches is resolved by their descriptions (one is global, one is transaction-specific).

    Naming Consistency4/5

    Most tools consistently use verb_noun snake_case (get_, list_, create_, delete_, hide_, confirm_, reject_, skip_). A few analytics tools (spending_summary, top_vendors) deviate by omitting the verb, which breaks the pattern slightly.

    Tool Count2/5

    With 36 tools, the set is over the 25+ threshold for 'too many'. Many hide/unhide/status operations for statements, receipts, and transactions add bulk that could be consolidated into fewer parameterized operations.

    Completeness4/5

    The core receipt-transaction matching workflow is well covered: listing, matching, confirming, rejecting, skipping, and unmaking matches. Missing update operations for receipts/transactions and statement upload/delete are minor gaps, but the domain surface is largely complete.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A personal financial management tool that enables AI assistants to record transactions, check balances, and provide monthly financial summaries via the Model Context Protocol. It allows users to manage their expenses and income through natural language interactions using standardized MCP tools and resources.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with secure, read-only access to over 15,000 financial institutions across the US and Europe via the Model Context Protocol. It enables users to query account balances, transactions, and spending breakdowns through natural language conversation.
      5
      239 npm
      54
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Firefly III personal finance accounts and transactions through the Model Context Protocol.
      22 npm
      90
      MIT