Introducing the Actionstep MCP Server

The Actionstep MCP Server connects your Actionstep practice management data to AI assistants like Claude, letting you and your team work with matters, contacts, documents, and custom data using plain, everyday language. Instead of clicking through screens, you can simply ask — "What are the custom fields on this matter?", "Log two hours to the Smith vs Smith matter", or "Upload this document to the correspondence folder" — and the assistant carries it out securely against your live Actionstep data. Built on the open Model Context Protocol, it uses your existing Actionstep sign-in and permissions, so nothing is exposed that a user couldn't already access, and every action is auditable. The result is a faster, more natural way to get information out of Actionstep and keep it up to date — without leaving the tools you already use.

BETA Programme

The Actionstep MCP Server is currently in BETA. If you would like to participate in the BETA programme please contact your Customer Service Manager to register your interest.

Technical Overview

Under the hood, the Actionstep MCP Server is a stateless service that implements the Model Context Protocol over Streamable HTTP, so it works with any MCP-compatible client. Authentication is handled through the standards-based OAuth 2.0 flow that proxies Actionstep's own sign-in — the server never stores your Actionstep password, and every request acts strictly within the authenticated user's security context. Document transfers happen out-of-band via short-lived, single-use secure links rather than over the protocol channel itself. Each request is traced with a correlation identifier and every data-changing action is written to a durable audit log, giving integrators clear, end-to-end visibility. The result is a secure, observable, production-grade foundation you can build client integrations against with confidence.

Model Context Protocol Version

The Actionstep MCP Server implements the Model Context Protocol (MCP) version 2.0 (28 July 2026 specification). It is compatible with any MCP 2.0 client, including the latest versions of Claude and other AI assistants that support the protocol.

Currently Supported Tools and Resources

Documents

• prepare_matter_document_upload
• prepare_matter_document_download
• prepare_contact_document_download
• list_matter_documents
• list_contact_documents

Folders

• list_matter_folders
• get_matter_folder
• create_matter_folder
• list_contact_folders
• get_contact_folder

Custom fields (matter)

• set_custom_field_value
• set_custom_field_values
• list_custom_fields
• list_dropdown_choices
• get_custom_field_values
• add_custom_data_record

Custom fields (participant/contact)

• set_participant_custom_field_value
• list_participant_custom_fields
• get_participant_custom_field_values
• list_participant_dropdown_choices

Tasks

• create_task
• update_task
• list_tasks
• get_task

File notes

• create_filenote
• list_filenotes
• get_filenote
• list_tags
• update_filenote

Matter/contact lookup

• search_for_matter
• get_contact
• list_contacts
• list_matter_participants

Contacts

• create_person_contact
• create_company_contact
• update_contact

Participant types

• list_participant_types

Contact types (roles)

• list_contact_types
• list_contacts_with_type

Users

• get_my_user_info
• find_user

Resources (read-only URIs)

• contacts/{id}
• contacts/{contactId}/types
• contacts/{contactId}/customfields
• filenotes/{id}
• matters/{matterId}/filenotes
• matters/{matterId}/tasks
• matters/{matterId}/participants
• matters/{matterId}/documents
• matters/{matterId}/folders
• matters/{matterId}/customfields
• tasks/{id}
• tags