Moneybird MCP Server

Created By
vanderheijden86a year ago
Moneybird MCP Server - Let Claude cook the books
Overview

What is Moneybird MCP Server?

Moneybird MCP Server is a Model Context Protocol (MCP) server that connects AI assistants like Claude to Moneybird accounting software via API, enabling seamless interaction with financial data.

How to use Moneybird MCP Server?

To use the Moneybird MCP Server, install the package, set up your Moneybird credentials in a .env file, and run the server. You can then connect it to AI assistants by providing the server URL.

Key features of Moneybird MCP Server?

  • Contact Management: List, retrieve, filter, create, and update contacts with advanced filtering options.
  • Financial Data Access: View sales invoices, financial accounts, and payments.
  • Business Operations Management: Manage products, projects, and time entries.
  • Custom API Requests: Make custom requests to Moneybird endpoints.
  • Interactive Assistant: Preconfigured prompt for a Moneybird assistant.

Use cases of Moneybird MCP Server?

  1. Automating financial data retrieval for AI assistants.
  2. Managing contacts and invoices through voice commands.
  3. Integrating financial operations into AI-driven applications.

FAQ from Moneybird MCP Server?

  • Can I use Moneybird MCP Server with any AI assistant?

Yes! It is compatible with any AI assistant that supports the Model Context Protocol.

  • Is there a cost to use Moneybird MCP Server?

No! The Moneybird MCP Server is open-source and free to use.

  • What are the prerequisites for running the server?

You need Node.js (v18 or higher) and a Moneybird account with API access.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
vanderheijden86
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago