Transipal WMS

com.transipalPublished by transipal.comOfficial publisherv1.0.0Updated Oct 24, 2026

Warehouse management for warehouses, missions, tasks, packs, products, and shipments.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Transipal WMS is a remote MCP server that gives an assistant access to warehouse management data covering warehouses, missions, tasks, packs, products and ship

What you can do
Connect an assistant to a warehouse management system covering warehouses, missions, tasks, packs, products and shipments. The manifest lists no individual tools, so the exact operations available are not documented here. Access is through a remote endpoint with OAuth sign-in.
When to use it
Relevant if you work with Transipal and want an assistant to reach your warehouse management data, such as warehouses, missions, tasks, packs, products or shipments, without leaving the conversation.
Requirements
A remote MCP endpoint at app.transipal.com, reachable over the network. OAuth authentication is required, so you need a Transipal account authorized for the connection. No environment variables or headers are declared.
Before you install
The server is hosted by a third party and requires OAuth access to your Transipal account, so review which permissions the authorization grants. The manifest lists no tools, so what the assistant can read or change in warehouse data is not documented; confirm this before connecting.

Installation

In SourceWeft

  1. Open Transipal WMS in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.transipal%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "transipal-wms": {
      "type": "http",
      "url": "https://app.transipal.com/_mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.