Solvent MCP Server
Enables Claude to interact with Solvent Personal Finance Manager through natural language to manage expenses, incomes, categories, and recurring transactions.
README
Solvent MCP Server
A dynamic MCP (Model Context Protocol) server for Solvent - Personal Finance Manager. This allows Claude to interact with your Solvent data through natural language.
Architecture
This MCP server uses dynamic tool discovery:
- On startup, fetches API metadata from
GET {SOLVENT_API_URL}/api/v1/meta - Dynamically generates MCP tools from the metadata
- When tools are called, proxies requests to the actual API endpoints
This means the tools are always in sync with the API—no manual updates needed when the API changes.
Features
- Expenses: List, create, update, and delete expenses
- Incomes: List, create, update, and delete incomes
- Categories: List, create, update, and delete categories
- Recurring Transactions: List, create, update, and delete recurring transactions
- Receipts: List, create, update, and delete receipts
Setup
1. Create an MCP Token
- Log into your Solvent account
- Go to Settings > Tokens
- Click Create Token
- Select MCP as the token type
- Set the permissions you want to grant
- Copy the token (you won't be able to see it again!)
2. Choose Your Connection Method
Option A: Claude.ai Connector (Recommended for Web)
Use this if you want to use Claude through the web interface (claude.ai).
- After creating your MCP token, copy the Connector URL shown
- Go to Claude.ai
- Click on "Search and tools" > "Add connectors"
- Select "Add custom connector"
- Paste the Connector URL
- Click Connect
The Connector URL format is:
https://your-solvent-domain.com/api/mcp?token=slvt_your_token_here
Option B: Claude Desktop (Local)
Use this if you want to use Claude Desktop on your computer.
-
Install Node.js (v18 or later) from nodejs.org
-
Install the MCP server globally:
npm install -g solvent-mcp
Or run directly with npx:
npx solvent-mcp --token slvt_xxx --api-url https://your-solvent-domain.com
- Configure Claude Desktop by editing the config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Add the following configuration:
{
"mcpServers": {
"solvent": {
"command": "npx",
"args": ["solvent-mcp", "--token", "slvt_your_token_here"],
"env": {
"SOLVENT_API_URL": "https://your-solvent-domain.com"
}
}
}
}
- Restart Claude Desktop
Configuration
Environment Variables
| Variable | Description | Default |
|---|---|---|
SOLVENT_API_URL |
Base URL of the Solvent API | http://localhost:3000 |
SOLVENT_API_TOKEN |
Your API token (starts with slvt_) |
Required |
Command Line Arguments
solvent-mcp --token <token> [--api-url <url>]
| Argument | Description |
|---|---|
--token <token> |
Your Solvent API token (required) |
--api-url <url> |
The Solvent API URL (optional) |
--help, -h |
Show help message |
Usage Examples
Once connected, you can ask Claude things like:
- "Show me my expenses from last week"
- "Create a new expense of $50 for groceries"
- "List all my income categories"
- "What are my recurring expenses?"
- "Create a monthly recurring expense of $15 for Netflix"
Generated Tools
Tools are automatically generated based on the API metadata. The naming convention is:
| Pattern | Tool Name | Description |
|---|---|---|
GET /api/v1/{entity} |
list_{entity} |
List all items |
GET /api/v1/{entity}/:id |
get_{singular} |
Get a single item by ID |
POST /api/v1/{entity} |
create_{singular} |
Create a new item |
PUT /api/v1/{entity}/:id |
update_{singular} |
Update an existing item |
DELETE /api/v1/{entity}/:id |
delete_{singular} |
Delete an item |
Expected Tools (25 total)
| Entity | Tools |
|---|---|
| Expenses | list_expenses, get_expense, create_expense, update_expense, delete_expense |
| Incomes | list_incomes, get_income, create_income, update_income, delete_income |
| Categories | list_categories, get_category, create_category, update_category, delete_category |
| Recurrings | list_recurrings, get_recurring, create_recurring, update_recurring, delete_recurring |
| Receipts | list_receipts, get_receipt, create_receipt, update_receipt, delete_receipt |
Permissions
When creating an MCP token, you can control which operations Claude can perform:
| Permission | Allows |
|---|---|
| Expenses: Read | List and view expenses |
| Expenses: Write | Create, update, delete expenses |
| Incomes: Read | List and view incomes |
| Incomes: Write | Create, update, delete incomes |
| Categories: Read | List and view categories |
| Categories: Write | Create, update, delete categories |
| Recurrings: Read | List and view recurring transactions |
| Recurrings: Write | Create, update, delete recurring transactions |
| Receipts: Read | List and view receipts |
| Receipts: Write | Create, update, delete receipts |
Development
Building from Source
npm install
npm run build
Running in Development
npm run dev -- --token slvt_xxx --api-url http://localhost:3000
Project Structure
src/
├── cli.ts # CLI entry point (stdio transport)
├── server.ts # Dynamic MCP server (tool discovery & proxying)
├── http-handler.ts # HTTP/SSE handler for remote MCP
├── types.ts # TypeScript types for API metadata
└── index.ts # Package exports
Security Notes
- Your MCP token grants access to your financial data
- Only create tokens with the minimum permissions needed
- Revoke tokens you no longer need from the Settings page
- The token is stored locally on your machine (Claude Desktop) or transmitted securely (Claude.ai)
Troubleshooting
"Token is not an MCP token"
Make sure you selected MCP as the token type when creating the token. API tokens cannot be used for MCP connections.
"Invalid or revoked token"
Your token may have been revoked. Create a new MCP token in Settings.
"Failed to fetch API metadata"
The server couldn't connect to the Solvent API. Check:
- The
SOLVENT_API_URLis correct - The API server is running
- Your network can reach the API
Connection issues with Claude Desktop
- Make sure Node.js is installed:
node --version - Check the Claude Desktop logs for errors
- Verify your config file is valid JSON
- Restart Claude Desktop after making config changes
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
E2B
Using MCP to run code via e2b.