SupportAPI SpecsAPI Docs
LogoDeveloper Portal

Get started

OverviewGetting StartedMCP ServerMCP Server Release NotesNotifications

Actionstep MCP Server — Release Notes

Checking your MCP Server Version

To check which version of the Actionstep MCP Server you are running, simply ask your AI Agent:

"What version of the Actionstep MCP server am I running?"

It will respond with the current version number similar to the following example:

"You're running actionstep-mcp-server version 1.18.0 (build commit 0c58071)"

NB: This feature is available from v1.18.0 onwards.

What's New in v1.21.4

Released 16 November 2026

  • Faster, steadier responses when you ask for a lot at once. When an AI Assistant worked through many matters in quick succession, the MCP server could slow down sharply and some requests failed with a "Bad Gateway" error. Each request was spending far more processing time than it needed on securing your sign-in. That work is now done once, so busy periods stay responsive and requests no longer fail this way.

  • Searches for "any of" a list work again in the advanced search form. Searches such as "matters that are active, inactive or closed", written with "in (…)" in the advanced search form, were refused in the previous release. Actionstep accepts them, and your AI Assistant can use them again. A list without brackets is still caught before anything is sent, and your AI Assistant is shown the form that works.

  • A clearer page when signing in doesn't work. If a sign-in link had expired or had already been used, for example after going back in the browser, you saw a server error. You now see a short page that explains what happened, says to start the connection again from your AI app, and gives a reference for support. The same readable page replaces the raw error text in the other sign-in failures, including a sign-in you cancelled.

  • Clearer guidance when completing some tasks. For some tasks, Actionstep refuses an update unless the task's matter is given again. Your AI Assistant is now told exactly that, so it can repeat the update with the matter.

  • Clearer errors when a contact's custom field can't be saved. If Actionstep refused a value for a contact's custom field, the message gave no hint why. It now explains that the contact may not have the role the field belongs to, and how to check.

  • Custom field values for large matters load faster. Reading every custom field value on a matter with a lot of custom data could take more than ten seconds. It now takes a fraction of that.

  • Improvements to connection handling and logging. Occasional "Bad Gateway" errors at quiet times are fixed. Our logs now keep court file and registry numbers that our support team needs to investigate a problem you report. Phone numbers, account numbers and other personal references are still hidden.

  • Updated supporting libraries. The MCP server now runs on current versions of its supporting libraries, including their security fixes. Nothing changes in how you connect or sign in.

What's New in v1.21.3

Released 09 November 2026

  • Saving several custom fields at once no longer fails when one of them is a linked calendar appointment field. When your AI Assistant updated several custom fields together and gave a linked calendar appointment field a date, Actionstep rejected the whole update and none of the values were saved. That kind of field holds a link to a calendar appointment, not a date. Your AI Assistant now checks the value first. You can also clear a linked appointment by asking your AI Assistant to remove it.

  • File note searches now answer quickly instead of stalling. Asking for file notes without saying which ones meant Actionstep had to count every file note in your organization before replying, which could take many seconds and end in "too many results". Your AI Assistant is now asked straight away to narrow the search to a matter, the note's author, or a date range, so you get a useful answer sooner.

  • Searches for "any of" or "none of" in a list no longer fail with a syntax error. Actionstep offers two ways of writing a search, and only one of them understands "in" and "not in". When your AI Assistant used them in the free-text form, for example "file notes on any of these matters", Actionstep rejected the search with a syntax error. Your AI Assistant is now told before anything is sent and shown the form that does work, so it gets the search right on its next try and keeps your "none of" meaning intact.

  • Asking for the next page at the end of a list no longer shows an error. If there were no more results, asking for another page came back as an Actionstep error. It now simply returns no further results.

  • Your AI Assistant no longer guesses when a save can't be confirmed. If the connection to Actionstep dropped partway through saving custom fields, your AI Assistant could be told nothing was saved when the save had in fact gone through. It is now told that the result is uncertain and to check the current values before trying again, so changes aren't applied twice or reported wrongly.

  • Improvements to error handling and logging. Badly formed requests now get a clear "bad request" reply instead of being treated as a server fault, which helps AI Agents recover on their own. The one-time links used for document uploads and downloads are never written to our logs, and our logs now keep the reference numbers and dates our support team needs to investigate a problem you report.

  • Updated to the latest MCP software. The MCP server now runs on the latest Model Context Protocol software and current versions of its supporting libraries, including their security fixes. Nothing changes in how you connect or sign in.

What's New in v1.21.2

Released 02 November 2026

  • The search_for_matter tool now supports filtering by primary participant. The primaryParticipants field can now be used in structured search filters. This is an array field and must be filtered using the in operator. Any detected instances of the eq operator will be automatically converted to in. The free-text search form doesn't support this field. Your AI Assistant gets a clear message pointing it to the structured form, instead of an Actionstep 400 or 500.

  • Minor improvements to internal logging. Targeted enhancements to improve the quality of logs generated by the MCP server. Logs now include more context for errors and warnings, making it easier to diagnose issues.

What's New in v1.21.1

Released 28 October 2026

  • An occasional unexplained error on one request has been removed. When your assistant sent several requests at the same moment and your session happened to fall due for renewal at exactly that point, one of those requests could come back as an error while the others succeeded. Your session was fine — asking again worked, and everything after it behaved normally. Requests in that position now pick up the renewed session and complete as they should.

  • More advanced searches now work first time. A search that combined an exact match with a wildcard one — for example file notes entered by a person that also mention a particular phrase — could be rejected with "Invalid operator detected". Actionstep offers two ways of writing a search and they spell their comparisons differently — "is equal to", "is not", "greater than" and so on; your assistant was using the spellings from the other one. We now correct that automatically.

What's New in v1.21.0

Released 21 October 2026

  • Assigning a task to yourself now works first time. Asking your assistant to create a task for you, rather than for a colleague, would fail with a message saying the assignee "must be a system user who has READ access to this task". Actionstep identifies a person in two different ways, and when your assistant looked you up it was being handed the wrong one of the two — so the task was refused even though you had every right to it. It now receives only the identifier that assignment actually needs, and you can simply say "assign it to me" without it having to look you up at all.

  • Creating a contact with an address now works. If you gave a country for a new contact's address, the attempt was rejected with a message about the mailing country not being allowed to be empty. Actionstep expects a contact's physical and mailing addresses either to both carry a country or for neither to, and your assistant was sending only the one you had mentioned. It now fills in the matching one for you.

  • More "does not contain" and numeric searches now work. Searches phrased as an exclusion — matters whose name does not contain "Westinghouse", or people whose surname is not like a given spelling — were being rejected, as were comparisons against zero such as quantity greater than 0. We have corrected the guidance your assistant works from so it gets them right first time. Sorting by a related field — a matter's step, or the person a task is assigned to — also now works instead of returning an error.

  • Searches that find exactly one result now behave like every other search. When a search matched a single record — the most precise kind of search, such as looking up one matter by its reference — Actionstep returns it in a subtly different form, and your assistant was passing the entire raw record through instead of the short summary it uses everywhere else. The information was never wrong, but it was bulkier and less consistent, which made answers slower and gave your assistant more room to misread a detail. One-result searches now return the same tidy summary as any other.

What's New in v1.20.1

Released 20 October 2026

  • Your assistant now shows you the newest records first, instead of the oldest. When it listed tasks, file notes, contacts or matters you asked about, it received only the first page of results — fifty records, oldest first — because it had not told Actionstep what order it wanted. On anything with more than fifty records that meant the work you were most likely asking about was missing from the answer: the note added this morning, the time entry recorded yesterday, the task just assigned. Nothing about it looked like an error, so the assistant answered confidently from an unrepresentative page. All of these lists now come back newest first, so the first thing you see is the most recent.

  • Lists you search by name are now in alphabetical order, and complete. Tags, matter types, participant types and the document folders on a matter or contact are the lists your assistant reads to turn a name you have used into the right record, so alphabetical order is what makes them usable. Previously they came back oldest first and stopped at fifty. You can now also ask for any of these in a different order, which was not possible before.

  • Folder lists were also affected, and are now fully fixed. As well as being in no particular order, they never told the assistant how many folders there were in total, and did not ask Actionstep for a sensible number of them — so on a matter with a large filing structure the assistant could be shown part of the folder tree with nothing to indicate the rest existed, and file a document into the wrong place as a result. Folder lists now state their order, request a full page, and report the true total.

What's New in v1.20.0

Released 16 October 2026

  • Your assistant can now find every document on a matter, not just the oldest fifty. Previously it asked Actionstep for documents without saying how many or in what order, so it received only the first page — fifty documents, oldest first — and had no way of knowing there were more. It would then describe that page as the matter's complete list. On a matter with hundreds of documents the most recent filing was effectively invisible, and a question like "what's the latest version of the agreement?" could be answered confidently and wrongly. Documents now come back newest first, your assistant is told the true total, and it can work through the remaining pages when it needs to.

  • Deleted documents no longer appear among your live ones. Actionstep keeps a deleted document on the record rather than removing it, and these were being returned alongside current documents with nothing to tell them apart — padding out lists and counts, and crowding genuinely current documents out of view. They are now left out by default. One thing to expect: document counts may look lower than before. That is the count being corrected rather than documents going missing — on some matters nearly half the records were deleted ones. If a document you are certain about still cannot be found, your assistant can now look through deleted documents as well and tell you it was most likely deleted rather than never filed.

  • You can ask for a document by name. Rather than listing everything on a matter and reading through it, your assistant can now search document names directly — so "is the signed lease on this matter?" is a single reliable lookup instead of a scan that might miss anything past the first page. This is the quickest way to settle whether a particular document is there.

  • The same improvements apply to documents filed against a contact. Ordering, paging, totals and search by name all work the same way for contact documents.

  • You will be told if a document list is incomplete, rather than quietly given a short one. When your assistant reads a long list across several pages, a document added or removed by a colleague midway through could previously cause one to be skipped with no sign that anything was missing. It now stops and reports the problem instead of presenting an incomplete list as complete.

What's New in v1.19.1

Released 14 October 2026

  • Large document uploads and downloads no longer stop part-way through. Transferring a sizeable document takes long enough that your access could quietly expire mid-transfer. The transfer now renews your access behind the scenes and carries on from where it was.

  • Routine security and maintenance updates. The components the server is built on have been updated to their current supported versions, including several security patches. No change in behaviour.

What's New in v1.19.0

Released 14 October 2026

  • Stronger encryption on the connection. Traffic between your assistant and the Actionstep MCP server now uses a FIPS-validated TLS configuration, with TLS 1.2 as the minimum accepted version. You don't need to do anything, and there's no change to how you connect or what you can ask.

What's New in v1.18.4

Released 12 October 2026

  • Your session now recovers by itself when you are connected in more than one place. Actionstep allows only one active sign-in per user for a given application, so connecting a second assistant could quietly invalidate the access your first connection was using. We now detect this straight away, renew your access behind the scenes and retry, so in almost all cases the request simply succeeds and you notice nothing.

  • The assistant no longer offers task statuses that cannot be saved. Asking to remove or hide a task would have your assistant set its status to "Deleted" — a value Actionstep currently rejects. The assistant now offers only the two statuses Actionstep accepts, Complete and Incomplete, and will tell you plainly that removing a task is not available in this release rather than trying and failing.

  • Fewer failed "is not one of" searches. Advanced filters that excluded a list of values — for example matters that are not Active, Inactive or Closed — could be rejected, because your assistant was using list operators that Actionstep's advanced filter does not support. It is now pointed at the supported way to express the same thing.

What's New in v1.18.3

Released 4 October 2026

  • "Everything except…" searches now work. Filters that excluded something — for example matters that aren't a particular type, or tasks whose status isn't Closed — could come back with an error. Behind the scenes your assistant was using a "not equal to" symbol that Actionstep doesn't accept. We now use the correct one and automatically correct the old one if it slips through, so these exclusion searches succeed first time instead of failing.

What's New in v1.18.2

Released 28 September 2026

  • Fewer failed filtered searches. Some advanced filters could fail when the wording sent by your assistant contained characters that had been converted to their web-safe form (for example a >= arriving as >=). We now recognise and correct these automatically, so those searches succeed instead of returning an error.

What's New in v1.18.1

Released 19 September 2026

  • More reliable searches and filters. Narrowing results — by status, date, name, and so on — now works correctly the first time, so you'll hit far fewer failed or empty searches when filtering matters, contacts, tasks, and file notes. You can also now filter on a wider range of fields than before.

  • No more unexpected sign-outs during busy sessions. We fixed a rare issue where several actions running at once could sign you out and make you reconnect. Your session now stays put through bursts of activity.

What's New in v1.18.0

Released 16 September 2026

  • Complete lists, every time. We fixed cases where long lists could stop short. Most noticeably, custom-field listings on a matter or contact now return every entry instead of capping at the first 50. Very large result sets can also be retrieved a page at a time.

  • Check your version in a click. You can now just ask "What version of the Actionstep MCP server am I running?" and get a clear answer — handy for confirming a release includes the fixes you asked for.

  • More complete date filters on file notes. Filtering file notes by date now also picks up system-generated notes (such as custom-field change entries) that could previously be missed.

  • Clearer "nothing found" responses. A search that matches no records now says so plainly, rather than returning an ambiguous empty result.

  • More accurate guidance. The assistant no longer suggests actions that aren't switched on in this release, so you won't be pointed toward features that aren't available yet.