Trackberry

com.trackberryPublished by trackberry.comOfficial publisherv1.1.0Updated Nov 14, 2026

Your fresh produce shipments: ETAs, tracking, free time, documents, pre-allocations and notes.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Trackberry connects an assistant to fresh produce shipment data: ETAs, tracking, free time, documents, pre-allocations and notes.

What you can do
  • Look up fresh produce shipments and their ETAs and tracking status
  • Check free time, pre-allocations and shipment notes
  • Access shipment documents
  • (No individual tools are listed in the manifest; capabilities are taken from the provider's description.)
When to use it
Useful when you work with fresh produce logistics and want an assistant to answer questions about shipment ETAs, tracking, free time, documents or pre-allocations without switching to the Trackberry app.
Requirements
A remote MCP endpoint at trackberry.com over streamable HTTP. Authentication is required: OAuth sign-in through a browser (one organization per connection) for clients like Claude, ChatGPT and Cursor, or an Authorization header with a Bearer API token for server environments.
Before you install
The connection is tied to one organization and is read-only unless permissions are widened, so check which organization you approve. The Authorization header carries a secret API token; keep it out of logs and shared configs. Shipment data is sent to the assistant and its model provider.

Installation

In SourceWeft

  1. Open Trackberry 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.trackberry%2Ftrackberry/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": {
    "trackberry": {
      "type": "http",
      "url": "https://trackberry.com/mcp"
    }
  }
}

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

3
  1. v1.1.0LatestNov 14, 2026
  2. v1.0.1Oct 4, 2026
  3. v1.0.0Sep 29, 2026

Score

83% 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
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.