MCP server

Registry

CloudAlly MCP Server

Name: CloudAlly MCP MCP Server
Author: servosity

Restore or download CloudAlly mailboxes as of a past date, and find failing backups

CloudAlly MCP scores 55 (Fair), with no SPDX license recorded. It installs as a local process. It does not declare tools yet. Filed under Productivity. Install configs are generated for 10 clients. Being listed in the registry is not the same as being vendor-official.

by servosityNo license

Install View on GitHub

Trust score

55Fair

Fair trust

55 of 100 from six public signals. Nobody can buy a point.

Listed in the official MCP registry.
No license recorded.

How we score trust

Scorecard

License, quality and maintenance

How grades work

License: Not graded
No license is recorded for this server.
How license is graded
Quality: Not graded
No README or tool list has been captured yet.
How quality is graded
Maintenance: Not graded
No commit or release date has been recorded.
How maintenance is graded

Trust breakdown

Where the 55 comes from

22 + 20 + 0 + 0 + 10 + 3 = 55. Each factor is capped, so no single signal can carry a listing.

Registry22 / 30

Active in the official MCP registry, plus a known vendor namespace.

Maintenance20 / 20

How recently the repository saw a commit or release.

Popularity0 / 20

GitHub stars and weekly downloads, on a log scale.

License0 / 10

A clear, OSI-style open-source license.

Security10 / 10

Not archived, a secure install path, a pinned version.

Docs3 / 10

A real summary, a README with depth, listed tools.

Install

Pick your client, copy the config, paste it in.

Add to Cursor Install in VS Code Install in VS Code Insiders

Needs Cursor or VS Code installed on this device. The button opens the app and asks you to confirm before it adds the server.

~/Library/Application Support/Claude/claude_desktop_config.json

{  "mcpServers": {    "servosity-cloudally": {      "command": "npx",      "args": [        "-y",        "https://github.com/Servosity/msp-skills/releases/download/cloudally-v0.2.0/cloudally-mcp.mcpb"      ],      "env": {        "CLOUDALLY_CLIENT_ID": "YOUR_CLOUDALLY_CLIENT_ID",        "CLOUDALLY_CLIENT_SECRET": "YOUR_CLOUDALLY_CLIENT_SECRET",        "CLOUDALLY_ACCESS_TOKEN": "YOUR_CLOUDALLY_ACCESS_TOKEN",        "CLOUDALLY_EMAIL": "",        "CLOUDALLY_PASSWORD": "YOUR_CLOUDALLY_PASSWORD",        "CLOUDALLY_PARTNER_EMAIL": "",        "CLOUDALLY_PARTNER_PASSWORD": "YOUR_CLOUDALLY_PARTNER_PASSWORD",        "CLOUDALLY_BASE_URL": "",        "CLOUDALLY_PORTAL_URL": "",        "CLOUDALLY_MCP_READ_ONLY": "",        "CLOUDALLY_NO_LOCAL_DATA": "",        "CLOUDALLY_MCP_HTTP_TOKEN": "YOUR_CLOUDALLY_MCP_HTTP_TOKEN",        "CLOUDALLY_USER_AGENT": "",        "PRINTING_PRESS_CLIENT_PROFILE": "YOUR_PRINTING_PRESS_CLIENT_PROFILE"      }    }  }}

Install guide

Environment variables

Name	Required	Notes
`CLOUDALLY_CLIENT_ID`Secret	Required	The client-id of your CloudAlly API application (partner portal > Integrations > REST API), sent as the client-id header on every request.
`CLOUDALLY_CLIENT_SECRET`Secret	Required	The client-secret of the same API application, sent as the client-secret header on every request.
`CLOUDALLY_ACCESS_TOKEN`Secret	Optional	Optional override; leave blank. Run `cloudally-cli auth login --partner` (or `auth login` for one company) in a terminal instead, which saves and refreshes the token. A pasted token expires and keeps overriding the saved one.
`CLOUDALLY_EMAIL`	Optional	Optional. Company account login used by `auth login`; every command is then limited to that one company. Most operators run `auth login` once in a terminal and leave this blank.
`CLOUDALLY_PASSWORD`Secret	Optional	Optional. Password for the company account login above.
`CLOUDALLY_PARTNER_EMAIL`	Optional	Optional. Partner portal login used by `auth login --partner`; it reaches every customer account and is needed for the distributor and reseller commands, `auth use-account`, past backup dates and downloads.
`CLOUDALLY_PARTNER_PASSWORD`Secret	Optional	Optional. Password for the partner portal login above.
`CLOUDALLY_BASE_URL`	Optional	Optional; leave blank. Sends every CloudAlly API call to this base URL instead of https://api.cloudally.com, for tests and mock servers.
`CLOUDALLY_PORTAL_URL`	Optional	Optional; leave blank. The customer portal origin used for past backup dates, restores resolved from them and downloads (default https://app.cloudally.com). It must be https (plain http only on a loopback test host), and portal credentials go only to https://app.cloudally.com or the CLOUDALLY_BASE_URL origin, so any other portal is refused before anything is sent. Needed when CLOUDALLY_BASE_URL points away from api.cloudally.com: portal commands then refuse to assume the production portal.
`CLOUDALLY_MCP_READ_ONLY`	Optional	Optional. Set to 1 to list only read-only tools: it removes cloudally_execute, restore_submit, download_submit, download_start, download_link, sync, export, workflow_archive, jobs_prune and the learn-store writers, and cloudally_read refuses every state-changing endpoint. The tools it keeps can still write the learn journal and create an empty local store.
`CLOUDALLY_NO_LOCAL_DATA`	Optional	Optional. Set to 1 to keep no local copy of API responses: reads go to the API, the response cache is off, and sync refuses to run. Leave blank to keep the local store.
`CLOUDALLY_MCP_HTTP_TOKEN`Secret	Optional	Required only when running the MCP server with --transport http (a remote/hosted deployment); callers must send a matching Authorization: Bearer header. Leave blank for Claude Desktop.
`CLOUDALLY_USER_AGENT`	Optional	Optional. Overrides the User-Agent the CLI sends to CloudAlly. Leave blank to use the built-in one.
`PRINTING_PRESS_CLIENT_PROFILE`Secret	Optional	Only used when the MCP server is bound to a tenant-gated client profile. This connector registers no tenant-gated source, so leave it blank.

Tools

All capabilities

Tools show up when the registry metadata or the repository README lists them. Public READMEs are read directly. A GitHub token is used only when one is already configured.

About

Restore or download CloudAlly mailboxes as of a past date, and find failing backups

Frequently asked questions

What is CloudAlly MCP Server?

Restore or download CloudAlly mailboxes as of a past date, and find failing backups

How do I install CloudAlly MCP Server in Claude Desktop, Cursor, or VS Code?

Pick your client in the Install section on this page and copy the generated config into the client's config file. Step-by-step guides: Claude Desktop, Cursor, and VS Code. CloudAlly MCP Server runs locally from the MCP bundle https://github.com/Servosity/msp-skills/releases/download/cloudally-v0.2.0/cloudally-mcp.mcpb with the command npx -y https://github.com/Servosity/msp-skills/releases/download/cloudally-v0.2.0/cloudally-mcp.mcpb.

Does CloudAlly MCP Server support remote (HTTP) connections?

No remote endpoint is listed for CloudAlly MCP Server. It runs locally on your machine over stdio, started by your MCP client.

How is CloudAlly MCP Server's trust score calculated?

CloudAlly MCP Server scores 55 out of 100 (Fair). The score adds six capped public signals: registry status, maintenance, popularity, license, documentation, and security. Nobody can pay for points. Read the methodology for the full formula.

Reviews

No reviews yet

—Be the first to review

5 star0

4 star0

3 star0

2 star0

1 star0

No published reviews yet. Used it? Tell the next person how it went.

Add badge to your README

Paste either snippet into the repository README. The image links to this listing.

Markdown

HTML

Manage this listing

Claim this server

Fair trust

License, quality and maintenance

License: Not graded

Quality: Not graded

Maintenance: Not graded

Where the 55 comes from

Install

Environment variables

Tools

About

Frequently asked questions

Reviews

Add badge to your README

Top 5 MCP servers

Manage this listing

Related servers

Microsoft 365 MCP Server

iCloud MCP

AIquila — Nextcloud MCP Server

seekstone

intervals-icu-mcp

Keeper.sh