PipeLedger

ai.pipeledgerPublished by pipeledger.aiOfficial publisherv0.1.0Updated Oct 30, 2026

Governed financial statements, metrics, and General Ledger detail from QuickBooks and NetSuite.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP server that gives an assistant governed access to financial statements, metrics and General Ledger detail from QuickBooks and NetSuite.

What you can do
  • Retrieve financial statements from connected QuickBooks and NetSuite accounts
  • Look up financial metrics
  • Read General Ledger detail
  • All access is presented as governed, with no tool list published in the manifest
When to use it
Useful when an assistant needs to answer accounting or reporting questions from QuickBooks or NetSuite data, such as reviewing statements, metrics or ledger entries, without exporting spreadsheets by hand.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or environment variables are declared. OAuth authentication is required, so a PipeLedger account and a connection to the relevant QuickBooks or NetSuite data are needed.
Before you install
The server exposes financial records, including General Ledger detail, so treat connected accounting data as sensitive. OAuth grants access to that data; review the scopes requested and who can reach the endpoint. No tool list is published, so confirm read versus write behavior before relying on it.

Installation

In SourceWeft

  1. Open PipeLedger in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.pipeledger%2Fpipeledger/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "pipeledger": {
      "type": "http",
      "url": "https://mcp.pipeledger.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.