Shire Automations

io.github.praisondaniPublished by GitHub account praisondaniv0.1.1Updated Oct 26, 2026

Read Shire Automations services and pricing; plan business workflows with stateless tools.

VerifiedSTDIODesktop onlyProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Local stdio MCP server that lets an assistant browse Shire Automations' public service catalog and run stateless workflow-planning tools.

What you can do
  • Browse the Shire Automations service catalog and pricing
  • List the available planning tools
  • Run planning tools on JSON input: map a workflow into an editable SOP draft, score an automation opportunity, assess AI readiness, plan an integration, build an onboarding checklist, or estimate workload and ROI
When to use it
Useful when you want an assistant to explore Shire Automations' offerings or draft automation plans, SOPs, integration plans and ROI estimates from your own JSON input, without submitting anything to the vendor.
Requirements
A local Node.js runtime to install the CLI package (globally, via npx, or from a source checkout) and run its MCP mode. Network access to the Shire Automations public API; the API origin can be overridden with the SHIRE_API_URL environment variable. No credentials are requested.
Before you install
Planning requests are sent to Shire Automations' public API, so avoid sending credentials or sensitive customer, patient or financial-account data. The server does not submit intake forms or start paid work. Estimates depend on input values and are not forecasts or guarantees.

Installation

In SourceWeft

  1. Open Shire Automations in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Shire Automations CLI

The shire CLI and its MCP mode give agents and people access to Shire Automations' public catalog and workflow planning tools.

Install

Install the latest GitHub release:

sh
npm install --global https://github.com/praisondani/shireautomations-cli/releases/latest/download/shireautomations-cli.tgzshire --help

After the npm package is published, you can also use:

sh
npm install --global shireautomations

Or run a command without a global install:

sh
npx --yes shireautomations tools

To run from a source checkout before publication:

sh
npm install --prefix clinode cli/bin/shire.js tools

Commands

sh
shire servicesshire pricingshire toolsshire catalogshire plan workflow-mapper --input workflow.jsoncat workflow.json | shire plan workflow-mapper --input -

Planning commands accept JSON and print JSON. The workflow mapper returns an editable SOP draft. Other tools score an automation opportunity, assess AI readiness, plan an integration, build an onboarding checklist, or estimate workload and ROI.

Set SHIRE_API_URL to an alternate API origin for development. The default is https://shireautomations.com.

MCP client install

For an MCPB-compatible client, download the Shire Automations MCP bundle and import it. The bundle runs the MCP server locally and calls Shire Automations' public API. It does not request credentials, store planning requests, submit intake forms, or start paid work.

MCP server

The CLI package also runs a local stdio MCP server:

sh
shire mcp

Example client configuration:

json
{  "mcpServers": {    "shireautomations": {      "command": "shire",      "args": ["mcp"]    }  }}

The server exposes shire_catalog, shire_list_planning_tools, and shire_plan. It calls the same versioned API as the CLI. It does not ask for API credentials, submit intake forms, or start paid work.

API and privacy

See the developer resources, OpenAPI specification, or Postman collection. The API does not save planning requests. Do not send credentials or sensitive customer, patient, or financial-account data. Estimates depend on the input values and are not forecasts or guarantees.

Source: README.md at commit 147b0e9

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

1
  1. v0.1.1LatestOct 21, 2026

Score

40% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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
  • License10 pts

    Declare a license in the repository or the registry entry.