Actionstep MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Returns a simple readiness response from the Actionstep MCP server. |
| list_conveyancing_actionsB | Lists starter conveyancing automation actions exposed by the MCP server. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one lists conveyancing actions, the other is a health check. There is no overlap or confusion.
'list_conveyancing_actions' follows a descriptive verb_noun pattern, but 'ping' uses a different single-verb style. While acceptable, the inconsistency prevents a higher score.
With only 2 tools, the server feels extremely minimal for a system named 'Actionstep'. Most servers in this domain would require more tools to be useful.
Only a listing operation and a health check are provided. No creation, modification, deletion, or execution of actions, which are essential for a conveyancing tool.