OxaDash

fr.oxadashPublished by oxadash.frOfficial publisherv1.1.287Updated Oct 27, 2026

Gérez vos sites, serveurs de jeu, VPS, DNS et mails OxalisHeberg.

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

Remote MCP server for OxaDash that lets an assistant manage OxalisHeberg websites, game servers, VPS, DNS and mail.

What you can do
  • Manage hosted websites, game servers and VPS through OxaDash.
  • Handle DNS records and mail settings for the hosted services.
  • No tool list is published, so the exact actions available are not documented here.
When to use it
Useful if you host sites, game servers, VPS, DNS or mail with OxalisHeberg and want an assistant to inspect or change those resources from chat instead of the OxaDash dashboard.
Requirements
A remote MCP endpoint at oxadash.fr over streamable HTTP, with no local install. Requires an OxaDash API key, created under Profile then API keys, sent in the X-API-Key header.
Before you install
The API key grants access to your hosting account, so treat it as a secret and scope or rotate it as needed. The server is described as managing resources, which likely includes changes to sites, servers, DNS and mail; confirm before letting an assistant modify or delete anything.

Installation

In SourceWeft

  1. Open OxaDash in the dashboard and add it to a workspace.
  2. Connect X-API-Key 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/fr.oxadash%2Foxadash/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": {
    "oxadash": {
      "type": "http",
      "url": "https://oxadash.fr/api/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

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.1.287LatestSep 25, 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.