Shire Automations
LocalAbout Shire Automations
Shire Automations provides a CLI and local stdio MCP server for accessing its public service catalog and planning business workflows. It offers catalog lookups and JSON-based planning tools without storing requests or initiating paid work.
Key features
- 01Browse services and pricing
- 02Inspect catalog and planning tools
- 03Draft editable workflow SOPs
- 04Assess automation and AI readiness
- 05Plan integrations and onboarding
- 06Estimate workload and ROI
Use cases
- 01Check Shire service offerings and prices
- 02Create an editable workflow procedure
- 03Assess an automation opportunity
- 04Prepare integration and onboarding plans
MCP support
The local stdio MCP server exposes catalog lookup, planning-tool listing, and workflow planning to MCP clients. It calls the same versioned public API as the CLI and does not request credentials or save planning requests.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEShire 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:
npm install --global https://github.com/praisondani/shireautomations-cli/releases/latest/download/shireautomations-cli.tgz
shire --help
After the npm package is published, you can also use:
npm install --global shireautomations
Or run a command without a global install:
npx --yes shireautomations tools
To run from a source checkout before publication:
npm install --prefix cli
node cli/bin/shire.js tools
Commands
shire services
shire pricing
shire tools
shire catalog
shire plan workflow-mapper --input workflow.json
cat 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:
shire mcp
Example client configuration:
{
"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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.