MCP server

Hayaan ang iyong AI assistant na magpatakbo ng iyong hosting

Isang MCP server para sa iyong buong account. Ikonekta ang Claude Code, Claude Desktop o Cursor nang isang beses, at ang iyong assistant ay maaaring maglista ng iyong mga site, magbasa ng kanilang mga log, mag-sync ng kanilang mga file sa iyong repository at mag-deploy — na kikilos lamang gamit ang mga pahintulot na ibinibigay mo dito.

65 na tool ngayon, na nakalista sa ibaba nang eksakto kung paano ito inaalok ng server.

Ikonekta ito

Dalawang hakbang. Ang token ang buong kredensyal, kaya itrato ito tulad ng password: ipinapakita ito nang isang beses, at maaari kang mag-revoke ng isang koneksyon nang hindi ginagalaw ang iba.

Gumawa ng koneksyon
Sa iyong dashboard, buksan ang AI tools, pangalanan ang koneksyon, piliin ang iyong kliyente at i-tsek kung ano ang maaari nitong gawin. Maaari mo lamang ibigay ang mga bagay na pinapayagan ka ring gawin.
I-paste ang config na binabasa ng iyong kliyente
Ipinapakita ng dashboard ang config para sa kliyenteng pinili mo, na kasama na ang iyong token. Nakikipag-ugnayan ang bawat kliyente sa iisang address ng server:
```
https://api.zinndigital.com/v1/mcp
```

Claude Code

Patakbuhin ang isang command, o ilagay ang block sa .mcp.json sa root ng iyong proyekto. Ang linyang "type": "http" ay kinakailangan — kung wala ito, nilaktawan ng Claude Code ang server.

claude mcp add --transport http zinn https://api.zinndigital.com/v1/mcp \
  --header "Authorization: Bearer zmcp_live_…"

// .mcp.json
{
  "mcpServers": {
    "zinn": {
      "type": "http",
      "url": "https://api.zinndigital.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer zmcp_live_…"
      }
    }
  }
}

Claude Desktop

Sinisimulan ng Claude Desktop ang mga lokal na server, kaya pinatatakbo nito ang aming libreng Zinnector® CLI bilang tulay patungo sa nakohost na server. Kailangan nito ng Node 24 o mas bago. Napupunta ang token sa env, hindi kailanman sa mga argumento.

// claude_desktop_config.json
{
  "mcpServers": {
    "zinn": {
      "command": "npx",
      "args": [
        "-y",
        "zinnector@0.1.4",
        "mcp"
      ],
      "env": {
        "ZINN_MCP_TOKEN": "zmcp_live_…"
      }
    }
  }
}

Krusor

Idagdag ang server sa ~/.cursor/mcp.json (o .cursor/mcp.json sa isang proyekto) kasama ang address at ang Authorization header.

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "zinn": {
      "url": "https://api.zinndigital.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer zmcp_live_…"
      }
    }
  }
}

Anumang iba pang MCP client

Anumang kliyente na sumusuporta sa mga malalayong Streamable HTTP server na may custom na header ay gagana: ituro ito sa address sa itaas at ipadala ang Authorization: Bearer kasama ang iyong token. Ang isang kliyente na nagsisimula lang ng mga lokal na server ay maaaring gumamit ng Claude Desktop bridge.

Kumokonekta ang ChatGPT sa mga server ng MCP sa pamamagitan lamang ng pag-sign in gamit ang OAuth, kaya hindi pa ito makagamit ng token. Gamitin ang parehong koneksyon sa pamamagitan ng Claude Code, Claude Desktop o Cursor.

Suriin kung gumagana ito — apat na tanong

Itanong ang mga ito sa payak na wika. Nasa ibaba ng bawat isa ang tool na dapat tawagan ng iyong assistant at kung ano ang hitsura ng isang magandang sagot.

```
> List my sites.
  ↳ sites_list
```
Ang iyong mga site kasama ang kanilang katayuan at plano. Ang isang bakanteng listahan sa isang account na may mga site ay nangangahulugan na ang koneksyon ay walang pahintulot na tingnan ang mga site.
```
> Show me the error log for example.com.
  ↳ site_logs
```
Ang kamakailang error log at access log. Kung ang isa ay hindi nabasa, gayon ang sinasabi ng sagot — iba iyon sa isang bakanteng log.
```
> Sync example.com to its repository.
  ↳ site_repo_sync_run
```
Isang commit sa iyong repository na may anumang pagbabago sa live site, o isang tala na ang repository ay tugma na. Kung lumipat ang repository, naka-hold ang sync at walang nadedesisyunan o nao-overwrite.
```
> I pushed a commit — deploy example.com and tell me when it is live.
  ↳ site_deploy → site_deploy_status
```
Ang deploy ay nakapila, pagkatapos ay magiging live gamit ang commit na inilapat nito. Hihingi ang mga tool sa pagsulat ng iyong pag-apruba sa client bago tumakbo.

Two-way sync, sa magkabilang direksyon

Ang isang site na may konektadong repository ay nananatiling sabay dito sa magkabilang direksyon, at ang iyong assistant ay maaaring magpatakbo sa alinmang direksyon.

Site → repository

Isinasapubliko nito ang mga nagbago sa mga live file — isang pag-edit sa file manager, pag-update ng plugin, isang pag-upload — at itinutulak ito sa iyong branch, para makuha ito ng iyong susunod na git pull.

site_repo_sync_run   ·   zinnector sync run

Repository → site

Inilalapat ng isang deploy ang iyong branch sa site. I-push ang iyong commit, pagkatapos ay i-deploy; sa aming sariling mga server, kailangan nito na naka-on ang two-way sync, na libre.

site_deploy   ·   zinnector push

Nang magbago ang magkabilang panig

Walang kailanman na pinagsasama o pinapatungan nang tahimik. Humihinto ang pag-sync, pinapangalanan ang commit, at hinihintay kang panatilihin ang site o panatilihin ang repository. Ang pagpapanatili sa repository ay nagtatapon sa mga hindi naka-sync na pagbabago ng site, kaya kailangan ito ng kumpirmasyon.

site_repo_sync_resolve keep=site|repository confirm=true

Kung ano ang nagpapanatili itong ligtas

Ang iyong ipinagkaloob lamang

Ang bawat tool ay nangangailangan ng pahintulot, at ang koneksyon ay nagtataglay lamang ng mga tinsekkan mo. Ang mga site ng ibang customer ay hindi umiiral hangga't abot ng kayang malaman ng iyong koneksyon.

Kumpirmasyon para sa anumang mapanirang aksyon

Ang pag-roll back, pag-restore, pag-resolve sa naka-hold na sync, at pagbili ay nangangailangan lahat ng malinaw na kumpirmasyon, at ang anumang may bayad ay nagpapakita muna sa iyo ng eksaktong kabuuang halaga.

Bawat aksyon sa iyong audit log

Nakatala ang bawat tawag sa koneksyon na gumawa nito. Bawiin ang isang koneksyon sa pahina ng mga tool ng AI at hihinto ito sa paggana kaagad.

Bawat tool

Ang lahat ng 65 na tool, na binuo mula sa sariling registry ng server — kung nakalista ito rito, maaari itong tawagin ng iyong assistant.

Mga site at pag-deploy

Kasangkapan	Ano ang ginagawa nito	Pahintulot	Mga Tala
`sites_list`	List the organization's sites, with each site's primary domain, status, product line, stack and the plan it is on. Optionally filter by status, product line or a search over domain and name.	`sites.view`	nababasa lamang
`site_get`	Get one site's full record — domain, status, product line, stack, runtime, PHP version, region, plan and whether it is scheduled for deletion.	`sites.view`	nababasa lamang
`site_create`	Create a site and start provisioning it. Give a primary domain and a product line; optionally a blueprint to build it from, a stack type, a PHP version or a region. Returns the new site, which begins in 'provisioning' — poll site_get for status.	`sites.create`	binago ang mga bagay
`site_deploy`	Deploy a site — build and publish its current source to our servers. Returns the deploy state immediately; the build runs as a durable workflow. Poll site_deploy_status to follow it.	`hosting.deploy.manage`	binago ang mga bagay
`site_deploy_status`	The site's current deploy state — status, target, the live URL, the deployed commit and when it last went live.	`sites.view`	nababasa lamang
`site_deployments_list`	List a site's recent deployments — id, status, commit, branch and timings. Use this to choose the deployment_id to roll back to.	`sites.view`	nababasa lamang
`site_rollback`	Roll a site back to an earlier deployment by re-deploying its commit. Destructive: pass confirm=true. Use site_deployments_list to choose which one.	`hosting.deploy.manage`	binago ang mga bagay · humihingi ng kumpirmasyon

Dalawang-daang pag-sync

Kasangkapan	Ano ang ginagawa nito	Pahintulot	Mga Tala
`site_repo_sync_get`	Show a site's two-way sync with its repository: whether it is available and on, the repository and branch, the current state (idle, synced, conflict, adopt, error) and the last runs with the commits they made.	`sites.view`	nababasa lamang
`site_repo_sync_set`	Turn two-way sync on or off for a site, optionally limited to a subdirectory of the site. Needs the customer's own GitHub account connected. Turning it on pushes nothing by itself — call site_repo_sync_run for that.	`hosting.deploy.manage`	binago ang mga bagay
`site_repo_sync_run`	Sync a site to its repository now: commit whatever changed in the site's live files and push it to the connected branch, so a local git pull receives it. If the repository moved since the last sync the run is HELD and nothing is overwritten — the result says so. The other direction (repository to site) is site_deploy.	`hosting.deploy.manage`	binago ang mga bagay
`site_repo_sync_resolve`	Resolve a HELD two-way sync. keep=site commits the site's files on top of the repository (their commits stay in history); keep=repository applies the repository to the site and DISCARDS the site's unsynced changes. Destructive: pass confirm=true.	`hosting.deploy.manage`	binago ang mga bagay · humihingi ng kumpirmasyon

Mga log at sukatan

Kasangkapan	Ano ang ginagawa nito	Pahintulot	Mga Tala
`site_metrics`	Current metrics for one site — visits, bandwidth, error rate, disk and resource use. Each section reports whether it is available, so 'no data' is distinguishable from 'zero'.	`sites.view`	nababasa lamang
`site_usage`	One site's metered visit usage for the current billing period, with the plan's allowance and what any overage costs.	`sites.view`	nababasa lamang
`site_logs`	Read the recent tail of one site's web-server access log and error log. Each log reports whether it could be read, so an unreadable log is never mistaken for an empty one. Use this before proposing a fix for errors or slowness.	`sites.panel_access`	nababasa lamang
`site_build_log`	Read the build log of one deployment — the latest when deployment_id is omitted. Pass after=<total from the previous call> to fetch only new lines while complete is false.	`sites.view`	nababasa lamang

Konpigurasyon at WordPress

Kasangkapan	Ano ang ginagawa nito	Pahintulot	Mga Tala
`site_php_version_get`	The site's current PHP version and every version it is allowed to switch to on its product line.	`sites.view`	nababasa lamang
`site_php_version_set`	Switch a site to a different PHP version. The version must be one that site_php_version_get lists as available. Reports whether the change reached the machine or was only recorded for provisioning to apply.	`hosting.php.manage`	binago ang mga bagay
`wordpress_state`	A WordPress site's core version, whether an update is available, and which management operations its hosting permits.	`sites.view`	nababasa lamang
`wordpress_plugins_list`	List a WordPress site's plugins — name, version, whether active and whether an update is available.	`sites.view`	nababasa lamang
`wp_plugin_update`	Update one WordPress plugin to its latest version. Returns the plugin list as it reads after the update.	`sites.panel_access`	binago ang mga bagay
`wordpress_update_core`	Update WordPress core to the latest version on a site. This cannot be undone by another call — take a backup first with backup_create if you may need to go back. Requires confirmation.	`sites.panel_access`	binago ang mga bagay · humihingi ng kumpirmasyon
`wordpress_set_plugin`	Activate or deactivate one plugin on a WordPress site. Takes effect on the live site immediately. Requires confirmation.	`sites.panel_access`	binago ang mga bagay · humihingi ng kumpirmasyon

Mga Back-up

Kasangkapan	Ano ang ginagawa nito	Pahintulot	Mga Tala
`backups_list`	A site's backups — each one's id, when it was taken, its size and status — plus whether a backup is currently running and how many on-demand backups remain in the rolling 24-hour allowance.	`sites.view`	nababasa lamang
`backup_create`	Take an on-demand backup of a site and return the updated backup state. Bounded to 3 per rolling 24 hours per site; the backup runs in the background.	`hosting.backup.manage`	binago ang mga bagay
`backup_restore`	Restore a site from one of its backups. This OVERWRITES the site's live database and files, and everything changed since that backup was taken is lost. Requires confirmation, and the confirmation names how old the backup is.	`hosting.backup.manage`	binago ang mga bagay · humihingi ng kumpirmasyon

Mga Domain at DNS

Kasangkapan	Ano ang ginagawa nito	Pahintulot	Mga Tala
`dns_records_list`	List a page of DNS records for a domain whose DNS we host, in name/type/value order. Returns a next_cursor for the following page.	`sites.view`	nababasa lamang
`dns_record_create`	Create a DNS record for a domain whose DNS we host.	`domains.dns.manage`	binago ang mga bagay
`dns_record_update`	Update an existing DNS record for a domain whose DNS we host.	`domains.dns.manage`	binago ang mga bagay
`dns_record_delete`	Delete a DNS record for a domain whose DNS we host.	`domains.dns.manage`	binago ang mga bagay · humihingi ng kumpirmasyon
`domains_list`	List the organization's domains — id, hostname, status, product line and whether we registered it or the customer pointed it at us. The ids returned here are what the DNS, cache-purge and index-check tools take.	`sites.view`	nababasa lamang

Cache at mga crawler

Kasangkapan	Ano ang ginagawa nito	Pahintulot	Mga Tala
`cache_purge`	Purge the CDN cache for a domain. Omit 'urls' to purge everything, or pass a bounded list of absolute URLs to purge only those.	`sites.cache.purge`	nababasa lamang
`crawler_policy_get`	Get a site's SEO-crawler-blocking (PBN footprint) policy: which crawlers are blocked, the available crawlers, and the rendered robots.txt/server rules.	`sites.view`	nababasa lamang
`crawler_policy_set`	Set a site's SEO-crawler-blocking policy. 'blocked' is a list of crawler keys (from crawler_policy_get's available_crawlers). Search engines can never be blocked. Publishes the change so the server rules are re-written.	`sites.crawler.manage`	binago ang mga bagay

Email

Kasangkapan	Ano ang ginagawa nito	Pahintulot	Mga Tala
`mail_services_list`	List the organization's email services — every domain it has mailboxes on, with the plan's mailbox allowance, how many are used, and whether the mail DNS is published.	`mail.view`	nababasa lamang
`mailboxes_list`	List the mailboxes on one email service, with each mailbox's size, how full it is, and whether it can send and receive.	`mail.view`	nababasa lamang
`mailbox_create`	Create a mailbox on an email service. Returns the new mailbox's password, which is shown once and cannot be retrieved later.	`mail.manage`	binago ang mga bagay
`mail_forwarders_list`	List the mail forwarders on one email service — which address goes where.	`mail.view`	nababasa lamang
`mail_forwarder_create`	Create a mail forwarder on an email service, sending everything for one address on to one or more destinations.	`mail.manage`	binago ang mga bagay

SEO

Kasangkapan	Ano ang ginagawa nito	Pahintulot	Mga Tala
`site_seo_metrics`	The cached SEO authority metrics for a hosted site — domain rank, backlinks, referring domains and organic keywords. Read-only and free; the figures are refreshed by the platform's own sweep, so they may be up to a month old.	`sites.view`	nababasa lamang
`domain_index_check`	The cached search-index status for a domain — whether it is indexed, how many pages, and when the reading was taken. Read-only and free.	`sites.view`	nababasa lamang

Mga larawan ng AI

Kasangkapan	Ano ang ginagawa nito	Pahintulot	Mga Tala
`image_models_list`	The image models this account can generate with — provider, model, and the price per image in USD. Read-only and free. A model that is not listed cannot be used, either because it is retired or because nobody has priced it.	`sites.view`	nababasa lamang
`image_generate`	Generate an image from a prompt and put it in this account's image library. Costs money — the price per image is what image_models_list reports for the model used. Returns the image ids; the customer sees them in their library immediately.	`links.edit`	binago ang mga bagay · maaaring gumastos ng pera

Mga Board

Kasangkapan	Ano ang ginagawa nito	Pahintulot	Mga Tala
`board_list`	List this organisation's project boards, newest first.	`agency.board.view`	nababasa lamang
`board_get`	Read one board in full: its columns and every card on them.	`agency.board.view`	nababasa lamang
`board_create`	Create a project board, optionally for one of your client organisations.	`agency.board.manage`	binago ang mga bagay
`board_card_create`	Add a card to a column. Cards are agency-only unless you pass visibility 'client'.	`agency.board.manage`	binago ang mga bagay
`board_card_move`	Move a card to another column, or to another position in its column.	`agency.board.manage`	binago ang mga bagay
`board_card_comment`	Comment on a card. Agency-only unless you pass visibility 'client', in which case the client sees it attributed to your agency.	`agency.board.comment`	binago ang mga bagay
`board_share_link_create`	Create a copy-paste link to a board that you can send in any chat or email. Defaults to a read-only link that needs no Zinn® account to open.	`agency.board.manage`	binago ang mga bagay
`board_share_link_revoke`	Revoke a board share link. This also removes anybody who joined the board through it, so use it when a link has gone somewhere it should not have.	`agency.board.manage`	binago ang mga bagay · humihingi ng kumpirmasyon

Pagsingil at mga pag-upgrade

Kasangkapan	Ano ang ginagawa nito	Pahintulot	Mga Tala
`subscriptions_list`	List the organization's subscriptions — the plan each one is on, its status, renewal date and whether it auto-renews.	`billing.view`	nababasa lamang
`invoices_list`	List the organization's invoices and credit notes — number, status, total, currency and issue date. Optionally filter by status.	`billing.view`	nababasa lamang
`upgrade_options`	What can be bought to lift a limit you have hit — bigger plans, priced with tax, in your own currency. Pass the entitlement from a refusal (e.g. 'max_sites'), or a site_id to see what that site's own plan could move to. Read-only: nothing is bought, and calling this costs nothing.	`billing.view`	nababasa lamang
`purchase_quote`	Price a plan exactly, with tax, in the customer's own currency — and nothing is bought or charged. Returns a quote_id to pass to purchase_authorize together with the total, which is what stops an agent committing someone to a figure they never saw. Quotes expire: re-quote rather than reusing an old id.	`billing.payment.manage`	binago ang mga bagay
`purchase_authorize`	Complete a purchase from a quote: places the order and charges the payment method on file. You must pass the exact total and currency purchase_quote returned — if the price has moved since, this refuses rather than charging a different amount. Retrying with the same quote_id returns the same order and never charges twice.	`billing.payment.manage`	binago ang mga bagay · humihingi ng kumpirmasyon · maaaring gumastos ng pera

Suporta

Kasangkapan	Ano ang ginagawa nito	Pahintulot	Mga Tala
`kb_search`	Search the published knowledge base for how-to and troubleshooting articles. Returns title, slug and summary so the agent can try a documented fix before opening a ticket.		nababasa lamang
`tickets_list`	List the organization's support tickets — subject, status, priority and when they were last updated. Optionally filter by status or site.	`tickets.view`	nababasa lamang
`ticket_create`	Open a support ticket. Include what you already checked — an agent that has read the KB and run diagnostics should say so in the body, so a human does not repeat it.	`tickets.reply`	binago ang mga bagay

Reseller

Kasangkapan	Ano ang ginagawa nito	Pahintulot	Mga Tala
`reseller_overview`	The reseller programme in one read: status, whether you can sell, billing day, default markup, your panel hostname and nameservers, mail sending domain, support routing, commerce readiness and the languages your clients' panel offers.	`reseller.view`	nababasa lamang · mga reseller lamang
`reseller_services_list`	List the sites you have provisioned for your clients — one row per service, with the client organisation, status, any hold you placed, what it costs you wholesale and what you sell it for. Your own sites are not here; use sites_list for those.	`reseller.view`	nababasa lamang · mga reseller lamang
`reseller_service_get`	One client service in full — status, plan, any hold, wholesale cost, your sell price, and its disk and bandwidth usage.	`reseller.view`	nababasa lamang · mga reseller lamang
`reseller_service_suspend`	Put one of your client's services on a non-payment hold. The site stops serving until you release it. Requires confirm: true.	`reseller.provision`	binago ang mga bagay · humihingi ng kumpirmasyon · mga reseller lamang
`reseller_service_unsuspend`	Release a non-payment hold you placed on a client's service. The site starts serving again.	`reseller.provision`	binago ang mga bagay · mga reseller lamang
`reseller_prices_list`	Your price list: every plan you can sell, with the Zinn® list price, your wholesale cost, and the retail price you have set (if any).	`reseller.view`	nababasa lamang · mga reseller lamang
`reseller_client_wallets_list`	Every client wallet you hold a float in, with the balance per client and the total held per currency. This is money you have taken and not yet delivered service for.	`reseller.view`	nababasa lamang · mga reseller lamang

Magpatuloy sa pagbasa

Ikonekta ang iyong assistant sa loob ng dalawang minuto

Buksan ang mga tool ng AI sa iyong dashboard, lumikha ng koneksyon, at i-paste ang config na binabasa ng iyong kliyente.