Updates

Inbound EDI that the parser stops reading part-way through now fails instead of being delivered as a partial document, accented characters now survive SFTP ingest, and a file lost from a consume-on-read SFTP mailbox now produces an error.

Each transaction setting now has a usage indicator, Production (P) or Test (T), that sets the ISA15 on outbound interchanges and is recorded on every inbound document, instead of every interchange going out as P.

Tediware now has an official Model Context Protocol (MCP) server at https://tediware.com/mcp, so a coding agent like Claude Code or Cursor can read your configuration, trace EDI transactions as they run through the platform, and send and receive data using an API key.

When you are signed in, the in-app help assistant now reads your partners, flows, mappings and transactions and answers your questions about what you have open, instead of answering from the documentation alone.

Webhook deliveries that fail with a server error, a 429, a timeout, or a dropped connection are now retried for about 16 minutes instead of failing on the first answer, and any inbound document can be redelivered to your webhook without resubmitting the EDI.

You can generate key pairs when creating or editing an SFTP connection within Tediware, so you can send a partner a public key without running ssh-keygen yourself.