Skip to main content
Glama
Actionstep MCP Server

Actionstep MCP Server

by mayank2012

Actionstep MCP Server

This project is a starter TypeScript implementation of an MCP server for Actionstep-style conveyancing automation. It exposes a small set of example tools and includes a simple HTTP health endpoint for local testing.

Project overview

The current implementation provides:

  • A basic Express HTTP server

  • A health check endpoint at /health

  • An MCP server with two example tools:

    • ping

    • list_conveyancing_actions

Related MCP server: mcp-base

Tech stack

  • TypeScript

  • Node.js

  • Express

  • Model Context Protocol SDK

  • Zod

  • dotenv

Folder structure

  • src/ – application source code

  • dist/ – compiled JavaScript output

  • package.json – scripts and dependencies

  • tsconfig.json – TypeScript compiler configuration

Installation

From the project root, install dependencies:

npm install

Build

Compile the TypeScript source:

npm run build

Run

Start the server:

npm start

Or run the build and start flow directly:

npm run dev

Health check

Once running, the server responds at:

http://localhost:3000/health

Next steps

This starter project is intended as a foundation for a production-ready Actionstep MCP server. Suggested next steps include:

  • Connecting the tools to the real Actionstep API

  • Adding OAuth 2.0 authentication and token refresh

  • Expanding the tool registry for matters, documents, tasks, and settlement workflows

  • Adding secure secret storage and audit logging

Node.js_MCP_Server_Development

Available Tools

2 tools
list_conveyancing_actionsB

Lists starter conveyancing automation actions exposed by the MCP server.

Inputs: no named parameters.

pingA

Returns a simple readiness response from the Actionstep MCP server.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: one lists conveyancing actions, the other is a health check. There is no overlap or confusion.

    Naming Consistency3/5

    '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.

    Tool Count2/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      A basic starter project for building Model Context Protocol (MCP) servers that enables standardized interactions between AI systems and various data sources through secure, controlled tool implementations.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A bare-bones FastMCP server template designed to serve as a starting point for building custom Model Context Protocol servers. It provides a foundational structure for implementing tools over HTTP and includes a built-in health check utility.
      GPL 3.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server scaffold that exposes stubbed tools for listing, searching, and summarizing sources, with built-in OAuth 2.1 authorization flow for Claude integration.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Framework for building and running MCP servers as HTTP services. Define tools as pure Python functions, wire up with two lines, run with one command.
      -