Wisewall Mcp

io.github.ti-abPublished by GitHub account ti-abv0.1.10Updated Oct 24, 2026

Manage WiseWall sites from an AI coding assistant — deploy, configure DNS, secrets, and plans.

VerifiedSTDIODesktop onlyCloud & Infrastructure Developer Tools

Server details

Identifier: io.github.ti-ab/wisewall-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account ti-ab for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.ti-ab%2Fwisewall-mcp.svg)](https://sourceweft.com/mcp/io.github.ti-ab%2Fwisewall-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that lets an AI coding assistant manage WiseWall sites: deploy them and configure DNS, secrets and plans.

What you can do: Deploy and manage WiseWall sites from the assistant, including publishing changes to a site's hosting environment. Configure DNS records for a site's domains. Manage site secrets used by the deployed application. Review and adjust site plans. Authenticate with a WiseWall personal access token obtained from the owner token page or through the package's login command.
When to use it: Useful when you host sites on WiseWall and want an AI coding assistant to handle deployment, DNS, secrets and plan settings without switching to the WiseWall dashboard. Best suited to developers already running WiseWall sites who want those operations inside their editor workflow.
Requirements: Runs as a local stdio process, installed from the npm package wisewall-mcp, so Node.js and npm are needed. Requires a WiseWall account and a personal access token supplied in the WISEWALL_TOKEN environment variable, obtained from the owner tokens page or via the package's login command. Desktop-only; no web execution.

Before you install

The server holds a WiseWall personal access token that can act on your account's sites; keep it out of shared configuration and logs. Its tools change live infrastructure — deployments, DNS records, secrets and plans — so mistakes can take a site down or expose configuration. Confirm changes before the assistant applies them.

Installation

In SourceWeft

Open Wisewall Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.10LatestSep 16, 2026

Score

25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
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.
License10 pts
Declare a license in the repository or the registry entry.