Lithic MCP Server
The Lithic MCP Server provides read-only access to Lithic banking and card services through a TypeScript implementation of the Model Context Protocol (MCP).
With this server, you can:
Fetch specific resources: Retrieve any Lithic resource (card, account, transaction, etc.) by its ID/token using the
get_resourcetoolList resources: Get collections of resources by type using the
list_resourcestoolAccess comprehensive resource types: Interact with cards, accounts, transactions, events, balances, disputes, external bank accounts, reports, webhooks, and account holders
Leverage type-safe interactions: Benefit from TypeScript's type safety when accessing Lithic resources
Run flexibly: Deploy via Docker or run directly with TypeScript
Configure easily: Customize using environment variables like
LITHIC_API_KEYandLITHIC_API_BASE_URL
Provides a TypeScript implementation of a read-only interface to Lithic banking and card services, enabling access to resources like cards, accounts, transactions, balances, disputes, and financial accounts through the Lithic API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Lithic MCP Server list my recent card transactions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Lithic MCP Server (TypeScript)
A TypeScript implementation of a Model Context Protocol (MCP) server for Lithic API that provides read-only access to Lithic banking and card services.
Features
Modern TypeScript implementation using the MCP SDK
Read-only access to all Lithic API endpoints
Type-safe tools for accessing Lithic resources
Docker support
Improved error handling and validation
Related MCP server: MCP (Model Context Protocol) Server
Quick Start
Using Docker (Recommended)
Build the Docker image:
npm run docker:buildRun the server:
LITHIC_API_KEY=your_key_here npm run docker:runManual Setup
Install dependencies:
npm installBuild the TypeScript code:
npm run buildStart the server:
LITHIC_API_KEY=your_key_here npm startMCP Configuration
Add this to your .cursor/mcp.json or Claude Desktop configuration:
{
"lithic": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e", "LITHIC_API_KEY",
"-e", "LITHIC_API_BASE_URL",
"mcp/lithic"
],
"env": {
"LITHIC_API_KEY": "your_lithic_api_key_here",
"LITHIC_API_BASE_URL": "https://api.lithic.com/v1"
}
}
}Available Tools
This MCP server provides the following tools:
get_resource: Fetch a specific Lithic resource by ID/tokenlist_resources: List resources of a given type
Environment Variables
LITHIC_API_KEY- Your Lithic API key (required)LITHIC_API_BASE_URL- Lithic API base URL (default: https://sandbox.lithic.com/v1)
Supported Resource Types
card
account
financial_account
transaction
event
balance
dispute
external_bank_account
report
webhook
account_holder
Development
For development, you can use the watch mode:
npm run devThis will automatically rebuild and restart the server when you make changes to the source code.
Available Tools
2 toolsget_resourceC
Get a specific Lithic resource by ID
Inputs: resourceType (required), resourceId (required).
list_resourcesC
List resources of a specific type
Inputs: resourceType (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get_resource retrieves a single resource by ID, while list_resources retrieves multiple resources of a type. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern (get_resource and list_resources), using snake_case and clear action verbs. The naming is perfectly predictable and uniform.
With only 2 tools, the server feels too thin for a general-purpose resource management domain. It lacks essential operations like create, update, or delete, making it incomplete for typical CRUD workflows.
The tool surface is severely incomplete for resource management. It only supports read operations (get and list), missing create, update, and delete capabilities, which are fundamental for a full lifecycle.
Maintenance
Related MCP Connectors
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
A Model Context Protocol server for Wix AI tools
Model Context Protocol server for Studex tools, notifications, and profile integrations
MCP server for Modern Treasury — payment orders, transactions, counterparties and ledgers.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA TypeScript implementation of a Model Context Protocol server that enables language models to securely query PostgreSQL databases, including those behind SSH bastion tunnels.23 npm1MIT
- -licenseNot gradedqualityDmaintenanceA TypeScript implementation of a Model Context Protocol server and client that enables interaction with language models (specifically Mistral running on Ollama).-
- AlicenseCqualityDmaintenanceTypeScript implementation of the Model Context Protocol that standardizes how LLMs connect to data sources and tools, eliminating vendor lock-in and simplifying AI integration.54 npmISC
- AlicenseNot gradedqualityDmaintenanceA TypeScript implementation of a Model Context Protocol server that enables LLMs to interact with Salesforce data through SOQL queries, SOSL searches, and CRUD operations.2MIT