Page traffic statistics
pages.statistics returns traffic for one hosted page: request count, bandwidth, cache hit rate, and bandwidth by country.
Tools
| Capability | MCP tool | Tokens |
|---|---|---|
| Get page statistics | pages.statistics | 10 |
Release notes and product updates from Vee3.
pages.statistics returns traffic for one hosted page: request count, bandwidth, cache hit rate, and bandwidth by country.
| Capability | MCP tool | Tokens |
|---|---|---|
| Get page statistics | pages.statistics | 10 |
Agents can now add a site to Google Search Console. Query clicks and impressions, inspect whether a URL is indexed, and submit a sitemap.

google-search-console.add_site takes a hostname, a domain property, or a URL.
Vee3-managed domains verify automatically. If Google is still checking, wait a short time and call the same tool again. Other domains need a DNS TXT record. Create it, wait for DNS, then retry.
google-search-console.list_sites lists properties on the account. Later calls can omit site_url to use the default property.
google-search-console.query_search_analytics returns clicks, impressions, CTR, and average position. Group rows by query, page, country, device, or date. Daily rows usually lag two or three days.
google-search-console.inspect_url checks one URL: indexing verdict, coverage, crawl, and canonicals. Google caps how many inspections run per day.
Submit or delete a sitemap with google-search-console.submit_sitemap and google-search-console.delete_sitemap. That updates Search Console tracking. It does not delete the sitemap file from the website.
| Capability | MCP tool | Tokens |
|---|---|---|
| Add Google Search Console site | google-search-console.add_site | 10 |
| List Google Search Console sites | google-search-console.list_sites | 5 |
| Get Google Search Console site | google-search-console.get_site | 5 |
| Query search analytics | google-search-console.query_search_analytics | 20 |
| Inspect URL | google-search-console.inspect_url | 15 |
| List sitemaps | google-search-console.list_sitemaps | 5 |
| Get sitemap | google-search-console.get_sitemap | 5 |
| Submit sitemap | google-search-console.submit_sitemap | 10 |
| Delete sitemap | google-search-console.delete_sitemap | 10 |
Turn the Google Search Console group on in Customize MCP if it is not already on the server.
Agents can now host static websites through Vee3. Create a page, deploy HTML and assets from account storage, and attach a custom hostname.
pages.create takes a unique slug and returns a page id plus a preview URL at {slug}.vee3.site. Agents do not need a separate hosting account.
Flow for a new site:
pages.create with a slug (lowercase letters, numbers, and hyphens)files.upload_file for the HTML, CSS, JavaScript, and other assetspages.deploy with those file_name values (up to 500 files per deploy)pages.edit can change the display name or slug. Changing the slug moves the preview hostname; an attached custom domain stays in place.
pages.set_custom_domain attaches a hostname such as www.example.com or example.com. The hostname must be on a domain already in that account's Vee3 inventory. Vee3 writes DNS (CNAME for a subdomain, ALIAS for the apex) and TLS. The {slug}.vee3.site preview URL stays available.
DNS and TLS can take several minutes to become available, and sometimes up to about 30 minutes. Setting a new custom domain replaces the previous one. pages.remove_custom_domain detaches it; the page stays online on the preview hostname.
| Capability | MCP tool | Tokens |
|---|---|---|
| Create page | pages.create | 200 |
| Deploy page | pages.deploy | 100 |
| List pages | pages.list | 10 |
| Get page | pages.get | 5 |
| Edit page | pages.edit | 20 |
| Set custom domain | pages.set_custom_domain | 50 |
| Remove custom domain | pages.remove_custom_domain | 5 |
| Delete page | pages.delete | 5 |
Turn the Pages group on in Customize MCP if it is not already on the server.
Agents can upload a whole local folder with a single vee3-upload command.
files.upload_file with the destination folder name (for example campaign-assets). Optionally pass existing_files as stop (default), continue, or replace.command. For continue or replace, that command includes --existing-files.file_name values. Nested relative paths are preserved under the reserved name.existing_files controls name collisions with files already stored:
stop fails on the first duplicate (default).continue skips duplicates and keeps uploading remaining files.replace overwrites duplicated stored files.Single-file uploads are unchanged: pass a file path instead of a folder. The same existing_files policy applies.
Each file can be up to 2 GB. One folder upload can include up to 500 files. Billing is per file after each upload is detected, using the same size and retention formula as a single-file upload.
Agents can now buy and manage domains through Vee3: check whether a name is available to purchase, get a token quote, register it, renew it later, and edit DNS host records one at a time.

Registration and renewal use platform credentials and Vee3 token billing. Agents do not need a separate registrar account.
Flow for a new name:
domains.check_availability to see if Vee3 can sell itdomains.registration_quote for the token costdomains.register with registrant contact details and the quoted expected_token_costUse a real registrant email the domain owner can access. The registrar may send a verification email that must be completed.
For domains already managed on the account, domains.renewal_quote then domains.renew extend the term.
Quoted costs are plan-aware and token-only:
| Action | Token cost |
|---|---|
| Register | 200 service tokens + domain registration price in tokens |
| Renew | 100 service tokens + domain renewal price in tokens |
After registration, the domain appears under managed domains. Agents can list and inspect it, then manage DNS host records without replacing the whole zone:
| Capability | MCP tool | Tokens |
|---|---|---|
| Check availability | domains.check_availability | 5 |
| Registration quote | domains.registration_quote | 5 |
| Register domain | domains.register | 200+ |
| List managed domains | domains.list_managed | 2 |
| Get managed domain | domains.get_managed | 3 |
| Renewal quote | domains.renewal_quote | 5 |
| Renew domain | domains.renew | 100+ |
| Get DNS hosts | domains.get_dns_hosts | 3 |
| Add DNS host | domains.add_dns_host | 5 |
| Remove DNS host | domains.remove_dns_host | 5 |
API Keys now has a Secrets section for client ID and client secret pairs. Use them with Claude: add a custom connector pointing at https://mcp.vee3.io/mcp, then paste the credentials under Advanced.
Guide: Connect Vee3 MCP to Claude
File handling for agents is now a first-class Files group. Upload and list tools live under files.* (no longer under Meta tools), and agents can download, move, delete, and extend retention the same way.
| Capability | MCP tool | Tokens |
|---|---|---|
| Upload file | files.upload_file | Depends on size × retention |
| List uploaded files | files.list_uploaded_files | 0 |
| Download file | files.download_file | 0 |
| Move file | files.move_file | 0 |
| Delete file | files.delete_file | 0 |
| Extend file | files.extend_file | Depends on size × added days |
Agents install the CLI once with npm install -g @vee3/cli, then run vee3-upload and vee3-get-file with the codes those tools return.
Uploads take an optional retention_days (default 7, max 90). Cost is based on size and how long the file is kept. List responses include retained_until; agents use files.extend_file to keep a file longer.
When a tool returns a download_code, the agent runs:
vee3-get-file {download_code} ./path/to/saveThat applies to uploaded files and to tools that write into account storage, including website screenshots and TikTok video/music downloads (a signed URL is still included for API-only use). Optional file_name sets the storage path; otherwise files land under downloads/.
tiktok.download_video uses quality: standard (default) or hd. One quality per call.
Agents can now work against your own Clerk instance through Vee3: your application and your data, not a shared sandbox.
Connect a Clerk application from Connections at app.vee3.io/dashboard/connections.
The Clerk capability group includes 199 MCP tools covering:
Use Customize MCP to turn the Clerk group on or off for your server.
| Capability | MCP tool | Tokens |
|---|---|---|
| Get Clerk connected accounts | clerk.get_connected_accounts | 0 |
| List Clerk users | clerk.list_users | 5 |
| Get Clerk user | clerk.get_user | 3 |
| Create Clerk user | clerk.create_user | 10 |
| List Clerk organizations | clerk.list_organizations | 5 |
| List Clerk sessions | clerk.list_sessions | 5 |
Call meta-tools.search with a task like "invite user to Clerk organization" or meta-tools.list_group_tools with clerk to browse the full catalog.
X read tools are cheaper today. If your agents search posts, pull timelines, or look up profiles, the same workflows cost fewer tokens.
| Capability | MCP tool | Was | Now |
|---|---|---|---|
| Search X | x-twitter.search | 10 | 5 |
| Get X tweet replies (latest) | x-twitter.tweet_replies | 10 | 4 |
| Get X user timeline | x-twitter.user_timeline | 10 | 4 |
| Get X tweet info | x-twitter.tweet_info | 5 | 2 |
| Get X user info | x-twitter.user_info | 5 | 2 |
Open Customize MCP at app.vee3.io/dashboard/customize-mcp.

Each capability group is a card with an on/off switch. Turn groups off to keep them off your MCP server; turn them back on anytime.
Use the search bar to filter groups by name or keyword (for example twitter, whois, or screenshots).
Connect X (Twitter) accounts from the dashboard at Connections (app.vee3.io/dashboard/connections).
The X / Twitter capability group now includes official write support for connected accounts, alongside the existing read APIs.
| Capability | MCP tool | Tokens |
|---|---|---|
| Get X connected accounts | x-twitter.connected_accounts | 0 |
| Create X post | x-twitter.create_post | 60+ |
Create X post supports text, polls, media attachments, reply settings, and other X post options. Call get-x-connected-accounts first to pick an account. If no accounts are connected, the user must connect at https://vee3.io/dashboard/connections — agents cannot complete OAuth.
Pricing: 60 tokens for a text post. Posts where X shortens a link to t.co in the response are billed at 1,000 tokens base instead. Images add 50 tokens each; videos add 150 tokens plus 50 tokens per 5 MB. Failed posts are not billed.
Large files no longer need to travel through MCP as base64.
| Capability | MCP tool | Tokens |
|---|---|---|
| Upload file | files.upload_file | 1 token per 20 MiB |
| List uploaded files | files.list_uploaded_files | 0 |
files.upload_file with a desired file_name to get an upload code.npm install -g @vee3/uploadvee3-upload {upload_code} {file_path} in a terminal.files.list_uploaded_files to see stored files and reference them in follow-up calls (for example, media on an X post).Files can be up to 2 GB and are kept for 14 days. Storage is billed after upload at 1 token per 20 MiB.
Agents can now report unexpected failures with meta-tools.report_bug (0 tokens).
Include a short summary, a detailed description, and optionally the related capability id. Reports are free and do not consume token quota.