Claude and MCP
Connect Claude, Claude Code, ChatGPT or any MCP client to Webnak, and what each tool does.
Webnak runs a remote MCP server, so Claude and other AI apps can work on your sites for you: make one from a template, put a project online, change text and images, roll back a deploy, connect a domain. You connect it once with one URL and approve it on Webnak’s own page. No API keys, and the app never sees your password.
https://api.cloud.wolfigs.com/mcpClaude on the web, desktop and mobile#
- 1
Add a custom connector
In Claude, open Settings → Connectors and choose Add custom connector. Name it
Webnakand paste the URL above as the remote MCP server URL. - 2
Connect and approve
Choose Connect. Claude opens Webnak’s approval screen. Sign in if you need to, check the account shown is the one you want, and choose Allow.
- 3
Use it in a chat
Make sure Webnak is switched on in the chat’s tools menu, then ask: “Make me a portfolio site on Webnak”.
Claude Code#
Add Webnak as a remote server, then sign in from inside Claude Code:
claude mcp add --transport http webnak https://api.cloud.wolfigs.com/mcpRun /mcp, pick webnak and choose Authenticate. Approve it in the browser tab that opens.
Or the plugin#
The plugin runs the Webnak CLI as a local server and adds a skill that teaches Claude the whole workflow. It signs in with a link and a code you approve in your browser.
/plugin marketplace add wolfigs/webnak-cli
/plugin install webnak@webnakChatGPT#
In ChatGPT, open Settings → Apps & Connectors and add a connector (some plans need Developer mode, under Advanced). Paste the URL above and choose OAuth. ChatGPT opens Webnak’s approval screen.
Other MCP clients#
Any client that supports remote servers over Streamable HTTP with OAuth can connect with the URL alone. It registers itself (dynamic client registration), signs in with the authorization code flow and PKCE, and receives a token that only works with Webnak. Discovery is at https://api.cloud.wolfigs.com/.well-known/oauth-protected-resource.
A client that only runs local servers can use the CLI over stdio:
{
"mcpServers": {
"webnak": {
"command": "npx",
"args": ["-y", "@wolfigs/webnak-cli@latest", "mcp"]
}
}
}It signs in with webnak login, or reads a token from WEBNAK_TOKEN in CI.
What it can do#
Each tool makes the same API calls the dashboard makes, as you. So it can do exactly what you can do for your sites, within your plan, and nothing else: it cannot change your password, sign-in settings or billing.
| Tool | What it does |
|---|---|
whoami | The signed-in account. |
list_sites · site_info | Your sites, their addresses and status. |
list_templates · create_site | Make a site from a template, from files, or from a GitHub repository. |
deploy_files · redeploy | Put new files live, or rebuild from GitHub. Replaces the live site. |
deploy_status · list_deploys · deploy_logs | Follow a deploy, see the history and read build logs. |
rollback | Make an earlier deploy live again. |
list_files · read_file · write_file · delete_files | Read and change the site's files as a draft. |
publish_files · discard_file_changes | Put the file draft live, or throw it away. |
get_content · set_content · publish_content | Change text and images in place on a page, then publish. |
edit_link | A private link for you to edit the site yourself by clicking. |
list_domains · add_domain · check_domain · remove_domain | Connect a custom domain and check its DNS (Starter). |
github_repos | Repositories you can host from, once GitHub is connected. |
Tools that replace a live site or delete something are marked destructive, so Claude asks before running them. Every deploy is kept, so any of them can be undone with rollback.
See and disconnect apps#
Every connected app is listed in Settings → Connected apps with when it connected and when it was last used. Choose Disconnect and its token stops working straight away. You also get an email whenever a new app is connected to your account.