ZimQi

au.com.zimqiPublished by zimqi.com.auOfficial publisherv1.0.0Updated Oct 27, 2026

Manage multi-site crews, rosters, check-ins and timesheets in ZimQi from any MCP client.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote ZimQi MCP server that lets an assistant manage multi-site crews, rosters, check-ins and timesheets from any MCP client.

What you can do
  • Manage crews and staff across multiple sites
  • Build and adjust rosters and shift assignments
  • Record and review worker check-ins
  • Create, review and update timesheets
  • All actions run against a ZimQi account through the hosted endpoint
When to use it
Useful when a team already runs its workforce scheduling and time tracking in ZimQi and wants an assistant to look up or update rosters, check-ins and timesheets without switching apps.
Requirements
A ZimQi account with API access. A bearer key created under ZimQi > Integrations & API, sent in the Authorization header. Connection to the remote endpoint at zimqi.com.au over streamable HTTP; OAuth is declared as required.
Before you install
The Authorization header carries a secret API key; keep it out of logs and shared transcripts. The server manages rosters, check-ins and timesheets, so assistant actions may create or change workforce records that affect payroll or billing. No tool list is published, so confirm what it can write before granting access.

Installation

In SourceWeft

  1. Open ZimQi 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/au.com.zimqi%2Ftimesheets/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": {
    "zimqi": {
      "type": "http",
      "url": "https://zimqi.com.au/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

1
  1. v1.0.0LatestOct 20, 2026

Score

56% 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

    Publish an icon in the registry entry.

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