CloudVikings

nl.cloudvikingsPublished by cloudvikings.nlOfficial publisherv1.0.1Updated Nov 1, 2026

Domains, DNS, hosting and mail you manage by chatting, with every change approved by you.

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

Remote MCP server from CloudVikings that lets an assistant manage your domains, DNS, hosting and mail through chat, with each change approved by you.

What you can do
  • Manage domains, DNS records, hosting and mail through chat.
  • Every change is presented for your approval before it is applied.
  • No tool list is published, so the exact actions available are not documented in the registry entry.
When to use it
Useful if you already have domains, DNS, hosting or mail with CloudVikings and want to make routine changes conversationally instead of through a control panel.
Requirements
A remote endpoint at mijn.cloudvikings.nl reached over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared. A CloudVikings account with the relevant domains and services is implied.
Before you install
The server can change live DNS, hosting and mail settings, so mistakes can take sites or email offline; the approval step is the main safeguard. Access is granted through OAuth to your CloudVikings account, so review the scopes you authorize. The tool list is not published, so verify what it can do before connecting.

Installation

In SourceWeft

  1. Open CloudVikings 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/nl.cloudvikings%2Fmijn/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": {
    "cloudvikings": {
      "type": "http",
      "url": "https://mijn.cloudvikings.nl/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

2
  1. v1.0.1LatestNov 1, 2026
  2. v1.0.0Oct 24, 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.