Dido distribution ERP

com.sindansolutionsPublished by sindansolutions.comOfficial publisherv1.0.0Updated Nov 5, 2026

Stock, quotes, orders, invoices, vans and credit control in Dido, scoped to the user's role.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for Dido distribution ERP, giving an assistant role-scoped access to stock, quotes, orders, invoices, vans and credit control.

What you can do
  • Work with stock and quotes in Dido
  • Create and follow orders and invoices
  • Look up vans and delivery-related records
  • Check credit control information
  • All access is limited to what the signed-in user's role permits
When to use it
Useful when a distribution or wholesale business runs Dido as its ERP and wants an assistant to look up or act on stock, quotes, orders, invoices, vans and credit control without leaving the chat.
Requirements
A remote MCP connection to the provider's hosted endpoint over streamable HTTP, plus OAuth sign-in with a Dido account; access is scoped to the user's role. No packages, environment variables or headers are declared.
Before you install
The server can reach business records such as orders, invoices and credit control, and may create or change them; confirm before letting an assistant write. Business data is sent to the provider's hosted service, and what is visible depends on the account's role permissions.

Installation

In SourceWeft

  1. Open Dido distribution ERP 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/com.sindansolutions%2Fdido/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": {
    "dido-distribution-erp": {
      "type": "http",
      "url": "https://dido.sindansolutions.com/api/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. v1.0.0LatestNov 5, 2026

Score

83% 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
  • 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.