AI coding tools

Connect Cursor, Claude Code or another MCP tool to Tanzahost, so it can create apps, deploy, read build output and logs, and set variables.

Updated 22 Oct 20264 min read

Tanzahost has an MCP server, the standard way AI coding tools connect to services. Add it to Claude Code, Cursor, VS Code, Windsurf or any tool that speaks MCP, and your AI can create projects and apps, deploy, read build output and logs, and set variables, with your own permissions. It can't delete anything, change DNS or touch money.

The server is hosted at https://api.tanzahost.com/v1/mcp, so there's nothing to install.

The quickest way: copy one prompt

Open your account, then Developers. Only an account's owners see it.
Find Connect your AI coding tool.
Choose What it may do: Deploy, or Full. Then what it reaches: the whole account, or one project.
Choose Make my prompt.
Choose Copy the prompt, and paste it into Claude Code, Cursor or your other AI tool.

The prompt carries a new token, made for your AI tool and shown once, and the exact steps for each tool. Your AI tool connects itself: Claude Code runs one claude mcp add command, and Cursor adds the server to ~/.cursor/mcp.json in your home folder. The prompt tells it never to write the token into your project's files or commit it. Then it lists your projects to check the connection works.

Deploy lets the AI add apps, deploy them and set variables. It can't create a project: for that, choose Full and the whole account, or create the project yourself in the dashboard first. A token limited to one project keeps the AI out of every other project.

The token ends after 90 days. Make a new prompt then, or revoke it under API tokens at any time.

Or set it up by hand

Make a token yourself under API tokens, as the API page shows: name it after the tool, like Cursor, and choose Deploy and one project. It starts with th_.

Put the token in a variable in your shell's profile, like ~/.zshrc, so it never sits in a file you might commit:

Terminal

export TANZAHOST_TOKEN=th_paste_your_token_here

Open a new terminal, and start your AI tool from it, so the tool sees the variable.

Claude Code

Add the hosted server with one command (Claude Code's MCP docs):

Terminal

claude mcp add --transport http --scope user tanzahost https://api.tanzahost.com/v1/mcp \
  --header "Authorization: Bearer $TANZAHOST_TOKEN"

Your shell fills in the token as you run it, and Claude Code keeps it in its own settings for your user, in every project. To share the setting with your team without the token, put it in the project's .mcp.json instead; Claude Code fills in ${TANZAHOST_TOKEN} from each person's own shell:

json

{
  "mcpServers": {
    "tanzahost": {
      "type": "http",
      "url": "https://api.tanzahost.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${TANZAHOST_TOKEN}"
      }
    }
  }
}

Type /mcp in Claude Code to check that tanzahost is connected.

Cursor

Cursor reads MCP servers from ~/.cursor/mcp.json for every project, or .cursor/mcp.json in one project (Cursor's MCP docs). Add Tanzahost's server:

json

{
  "mcpServers": {
    "tanzahost": {
      "url": "https://api.tanzahost.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${env:TANZAHOST_TOKEN}"
      }
    }
  }
}

Other tools

Add an MCP server over HTTP, with the address https://api.tanzahost.com/v1/mcp and the header Authorization: Bearer followed by your token.

Your AI tool sends your code as files in the request, up to 8 MB and 2,000 files, or as one ZIP.

What your AI tool can do

Tool	What it does
`whoami`	Which account the connection acts in, and what its token may do
`list_projects`	The account's projects with their apps, and the locations a new project can go in
`create_project`	Makes a project in a location
`list_apps`	One project's apps, with their state and live deploy
`create_app`	Adds an app to a project
`deploy_files`	Sends an app's code, as files or one ZIP, up to 8 MB, and deploys it
`deploy`	Builds the app again from its own code and deploys it, or rolls back to an earlier build
`deploy_status`	The app's state, newest builds and newest deploys
`build_log`	A build's output, to see why it failed
`deploy_log`	A deploy's output: the checks, and why it didn't go live
`read_logs`	A project's newest log lines, by app, level or a search
`list_variables`	An app's variables' names. Values stay hidden
`set_variables`	Sets an app's variables. They apply at the next deploy
`restart_app`	Starts the live version again, without downtime, and can apply new variables

What it can't do

There's no tool to delete anything, reset or empty a database, change DNS or touch the wallet. If a call tries to reach one of those another way, Tanzahost refuses it. Removing a variable, deleting an app, DNS records and money stay in the dashboard, where you do them yourself.

Everything your AI tool changes is in your account's Activity, like "Asha, through an AI tool". The token's Calls list under Developers shows each call of the last 90 days, with the AI tool's calls marked AI tool. Revoke the token there and the tool stops at once.

Use Tanzahost from Cursor and Claude Code follows Asha as her AI tool deploys her shop and fixes a failed build.

PreviousThe command-line tool NextDeploy a Laravel app