Mini Accountant
Remote MCP server for Mini Accountant that lets AI assistants manage invoices, customers, expenses, services, payment settings, analytics, and account/profile data via OAuth 2.1-secured streamable HTTP.
README
Mini Accountant — MCP setup
Connect your AI assistant to your Mini Accountant workspace through our hosted Model Context Protocol (MCP) server. No local setup, no API keys — the server is remote and protected by OAuth 2.1, so you sign in once with your Mini Accountant account and your assistant acts on your behalf.
- Server:
mini-accountant - Transport: streamable HTTP
- URL:
https://mcp.miniaccountant.app/v1beta - Auth: OAuth 2.1 / OIDC (Authorization Code + PKCE) — you'll be prompted to sign in.
What you can do
Once connected, the assistant can:
- Invoices — create, read, update, delete; add/update/remove positions and transactions; change the customer on an invoice.
- Customers — create, read, update, delete; set a customer's payment method.
- Expenses — create, read, update, delete; fetch expenses for a period.
- Services — manage your reusable product/service catalogue.
- Payment settings — manage the payment-method documents customers reference.
- Analytics — run reporting queries; get invoices/transactions/expenses for a date range; estimate tax for a period.
- Account — read and update your user profile and app settings.
Guided skills and prompts (e.g. "create an invoice") are also exposed so the assistant discovers the right workflow automatically.
Install in Claude Code (plugin)
The quickest path — installs the remote server as a plugin, no manual config file.
/plugin marketplace add miniaccountant/mcp-setup
/plugin install mini-accountant@miniaccountant
/reload-plugins
Then run /mcp and complete the OAuth sign-in when prompted. That's it — the
mini-accountant tools are now available in your session.
Prefer not to use the marketplace? Add the server directly:
claude mcp add --transport http mini-accountant https://mcp.miniaccountant.app/v1beta
Connect from other clients
Same remote URL, same OAuth sign-in — only the config location differs.
Claude Desktop / claude.ai connectors
Add a custom connector pointing at the server URL:
- Open Settings → Connectors → Add custom connector (claude.ai) or the equivalent in Claude Desktop.
- Name:
Mini Accountant - URL:
https://mcp.miniaccountant.app/v1beta - Save, then connect and sign in with your Mini Accountant account when prompted.
Cursor
Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):
{
"mcpServers": {
"mini-accountant": {
"url": "https://mcp.miniaccountant.app/v1beta"
}
}
}
Reload Cursor, then authorize the server when Cursor opens the OAuth prompt.
VS Code (GitHub Copilot / MCP) and other clients
Any client that supports remote/streamable-HTTP MCP servers works with the same endpoint. Use the client's HTTP-server form:
{
"servers": {
"mini-accountant": {
"type": "http",
"url": "https://mcp.miniaccountant.app/v1beta"
}
}
}
Authentication
The server implements OAuth 2.1 / OpenID Connect with:
- Authorization Code grant + PKCE (S256), refresh tokens.
- Dynamic Client Registration (RFC 7591) — clients register automatically.
- Discovery documents:
https://mcp.miniaccountant.app/.well-known/oauth-authorization-serverhttps://mcp.miniaccountant.app/.well-known/oauth-protected-resourcehttps://mcp.miniaccountant.app/.well-known/openid-configuration
Compliant MCP clients discover these automatically — you only need the server URL. Tokens are issued to your account; the assistant can only see and change your data.
Troubleshooting
401 Unauthorized/ prompted to sign in again — the access token expired (1h TTL). Re-run the client's connect/authorize action.- Tools don't appear — confirm the client finished the OAuth flow (in Claude
Code, run
/mcpand check the server shows connected). - Wrong workspace — sign out of the connector and reconnect with the correct Mini Accountant account.
Support
- Website: https://ad.miniaccountant.app
- Support: support@miniaccountant.app
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.
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.
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.
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.
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.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
E2B
Using MCP to run code via e2b.