QuickBooks Time MCP Server (Combined)

Created By
aallsburya year ago
A Message Control Protocol (MCP) server that provides unified access to QuickBooks Time API functionality. Developed with AI assistance.
Overview

what is QuickBooks Time MCP Server?

QuickBooks Time MCP Server is a Message Control Protocol (MCP) server that provides unified access to all QuickBooks Time API functionalities through a single interface, combining the features of multiple servers into one.

how to use QuickBooks Time MCP Server?

To use the server, install the required dependencies, create a .env file with your QuickBooks Time access token, and run the server using Python. Configuration is also needed for integration with Claude Desktop.

key features of QuickBooks Time MCP Server?

  • Unified access to QuickBooks Time API functionalities
  • Support for JobCode, Timesheet, User, and Project Management tools
  • Ability to filter and retrieve specific data through various API endpoints

use cases of QuickBooks Time MCP Server?

  1. Managing job codes and timesheets efficiently.
  2. Generating payroll reports based on job codes and time entries.
  3. Accessing user and project management data seamlessly.

FAQ from QuickBooks Time MCP Server?

  • What is the purpose of this server?

It provides a single interface to access all QuickBooks Time API functionalities, simplifying integration and usage.

  • How do I contribute to the project?

Contributions are welcome! You can submit a Pull Request on GitHub.

  • Is there support available for issues?

Yes, you can report issues or feature requests on the GitHub issues page.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aallsbury
Star
-
Language
-
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