Repository navigation
Onboarding request: LedgerCrossing (com.ledgercrossing/quickbooks-desktop) #3813
Replies: 2 comments
|
This repository, its issues and discussions are not the best forum for requests for MCP Registry inclusion and related discussions. Please follow the advice here: https://github.blog/ai-and-ml/generative-ai/how-to-find-install-and-manage-mcp-servers-with-the-github-mcp-registry#h-how-to-publish-your-own-mcp-server |
0 replies
|
Thanks, understood. The server is already in the MCP Registry ( |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Onboarding request: LedgerCrossing (
com.ledgercrossing/quickbooks-desktop)Owner request. I'm an admin of the LedgerCrossing GitHub org. The namespace is verified for ledgercrossing.com (HTTP), and the server was published to the open-source MCP Registry first. Opening this per the maintainer note in #1257; it replaces my comment there from Nov 3.
com.ledgercrossing/quickbooks-desktopactive,isLatesthttps://github.com/LedgerCrossing/quickbooks-desktop-mcp/releases/download/v1.15.4/ledgercrossing.mcpb, sha2560dc1f89c7835b0cc6a7c3962699551fe79094f2c7d0fb1c10bd68c736e83663c. It runs on the Windows computer where QuickBooks Desktop runs.https://{remote_address}/mcp, Streamable HTTP. One address per customer, through LedgerCrossing Remote;remote_addressis a required variable in the registry record.Verification:
Testing it end to end needs QuickBooks Desktop on Windows, so there's no shared public endpoint; each Remote customer has their own address.
Thanks!
All reactions