Zoopit

no.zoopitPublished by zoopit.noOfficial publisherv1.0.0Updated Oct 24, 2026

Read-only access to a Zoopit account: orders, routes, fleet and live vehicle positions.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Gives an assistant read-only access to a Zoopit account's orders, routes, fleet and live vehicle positions.

What you can do
This remote MCP server connects an assistant to a Zoopit account for read-only lookups. According to the registry description, it exposes orders, routes, fleet data and live vehicle positions. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to answer questions about delivery orders, planned routes, fleet vehicles or current vehicle locations without opening the Zoopit interface yourself.
Requirements
A remote endpoint at mcp.cloud.zoopit.no over streamable HTTP. Authentication is required: a bearer token in the Authorization header, issued for a Zoopit API client with read scopes. No local runtime, packages or environment variables are declared.
Before you install
The Authorization header carries a secret bearer token; keep it out of logs and shared transcripts. Issuing a new token revokes the client's previous one, so creating one can break other integrations using the same client. Access is described as read-only, but the token's scopes determine what it can reach.

Installation

In SourceWeft

  1. Open Zoopit in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/no.zoopit%2Fmcp/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.

{
  "mcpServers": {
    "zoopit": {
      "type": "http",
      "url": "https://mcp.cloud.zoopit.no/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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.

  • 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.