"Guide to connecting to Bitbucket Data Center" matching MCP tools:

• query_ai_infrastructure_construction_v1A

  exascale.buildA

  Query verified U.S. private construction spending ($ millions) for data centers and semiconductor/computer-electronics manufacturing plants, from the U.S. Census Bureau's Value of Construction Put in Place (C30). Use this for "how much is being spent BUILDING data centers (or chip fabs) in the US" questions — the construction buildout in dollars, not capacity or investment. Filter by `category` ("data_center" — Census's named subcategory under Office; or "computer_electronic_electrical" — the semiconductor/computer-electronics manufacturing line under Manufacturing), `basis` ("seasonally_adjusted" = a seasonally-adjusted ANNUAL RATE, or "not_seasonally_adjusted" = the NOT-adjusted MONTHLY LEVEL), `data_month` (one month, ISO first-of-month e.g. "2026-04-01") or the `data_month_from`/`data_month_to` range, `year`, and `revision_status` ("preliminary", "revised", or "final"). Group by any of `category`, `basis`, `data_month`, `year`, or `revision_status`. Pass each parameter as a top-level key of `params` (flat — not nested under a `filter`, `filters`, or `where` key). Example: `{"category": "data_center", "basis": "seasonally_adjusted", "data_month": "2026-04-01"}` for one month; add `"group_by": ["data_month"]` over a `data_month_from`/`data_month_to` range for a series. Returns JSON aggregates with citations and optional row-level records when `include_records` is true — every value cites the exact Census workbook, sheet, row, and column. The two categories are DISTINCT series and are never conflated: `data_center` is data-center buildings; `computer_electronic_electrical` is the chip/electronics-manufacturing (fab) line — the CHIPS-Act build-out. `basis` is the other fork: the seasonally-adjusted series is an ANNUAL RATE (what the current monthly pace annualizes to), while the not-seasonally-adjusted series is the actual MONTHLY LEVEL. `revision_status` carries Census's own preliminary/revised/final marking verbatim. Data is monthly; the data-center series begins 2014-01. The response `as_of` is the release vintage (Census revises monthly); pin `as_of` to an earlier vintage to reproduce what was served then. NOT additive: `construction_spending_musd` is a published per-(category, basis, month) reading, so a total that mixes the two bases (an annual rate + a monthly level), or that sums the seasonally-adjusted ANNUAL-RATE series across months, is not a real figure — such a result carries a `construction_aggregation` scope note and ranking remainders omit the metric. Filter to one `basis` and `group_by data_month` for a series over time. Does not determine total data-center INVESTMENT (servers, chips, cooling, equipment — this is construction put-in-place only; Census does not publish an investment total), data-center MW capacity, count, square footage, or location (use the power.* capabilities for capacity and the interconnection queue), which company or project is building (Census C30 has no operator breakdown), public or government construction (this is PRIVATE construction only), or construction outside these two categories.

  ConnectorNo auth

• run_blueprint_and_waitA

  FFmpeg MicroA

  One-shot convenience tool: starts a blueprint run and polls until it completes, fails, or pauses for review. Returns the final run with `output_url` (or `outputs` [{label, url}] for multi-output blueprints — prefer `outputs` when present). Download URLs are signed with a 10-minute TTL; re-fetch with get_blueprint_run for fresh links. NOTE: caption-video pauses in status awaiting_review — this tool then returns early with `awaitingReview: true` and the run's `srt_text`; review/edit the transcript and resume with continue_blueprint_run. If your MCP client enforces a short per-request timeout (many default to 60s), use run_blueprint + get_blueprint_run polling instead. Per-blueprint input fields (* = required): - product-ad: logo_url*, photo_url*, music_url? — GENERATIVE, costs 200 tokens - caption-video: video_url*, language?, style? (bold-bottom|clean-lower|center-pop|top-title) — pauses at awaiting_review with srt_text for transcript review; resume with continue_blueprint_run - viral-short: video_url*, hook_text*, style? (top-hook|center-statement|bottom-caption|lower-left), music_url? - quote-card: quote*, name?, handle?, photo_url?, output? (video|image) - watermark: video_url*, logo_url*, position? (top-left|top-right|bottom-left|bottom-right|center), size? (small|medium|large) - resize-format: video_url*, format? (9x16|1x1|16x9|4x5), fit? (pad|crop) - zoom-in: video_url* - zoom-out: video_url* - camera-glide: video_url*, direction? (right|left) - boomerang: video_url* - speed-changer: video_url*, speed? (0.5|1.5|2|4) - video-to-gif: video_url*, length? (5|10|15), size? (480|640), caption?, caption_position? (bottom|top|center) — output is a .gif - product-slideshow: photo1_url*, photo2_url*, photo3_url?..photo5_url?, music_url?, aspect? (9x16|1x1|16x9) - listing-kit: video_url* — multi-output (4 platform variants in `outputs`) - hook-variants: video_url*, hook1*, hook2?, hook3?, ratio? (9x16|4x5|1x1|original), style? (top-hook|center-statement|bottom-caption) — multi-output (one per hook in `outputs`) Input URLs: public https or upload-bucket gs:// (use request_upload_url + confirm_upload to get one). FFmpeg-lane blueprints charge no tokens (they meter plan compute minutes); only generative blueprints (product-ad) charge tokens.

  ConnectorOAuth

• adsap_google_create_shopping_campaignA

  AdsapA

  Create a complete standard Google Shopping campaign in ONE atomic request: budget, campaign (ALWAYS created PAUSED — activate later with adsap_google_set_entity_status), location targeting, a Shopping ad group, the product ad, and an 'All products' listing group. Product data, images and landing pages come from the linked Merchant Center — there are NO creative inputs. REQUIRES an ACTIVE Merchant Center link on the account (clean NO_MERCHANT_LINK error if none; merchant_id is auto-resolved when exactly one link exists). Use dry_run: true first — Google validates the whole chain without creating anything; show the plan, get confirmation, then execute. campaign_priority (0-2) only arbitrates between the account's OWN standard Shopping campaigns — a retail Performance Max campaign ALWAYS outranks standard Shopping for the same products; say so when the account also runs retail PMax. feed_label (from adsap_google_list_feed_labels) restricts the campaign to one Merchant Center feed label; omit to advertise all feeds. Language targeting does not exist for Shopping (ad language follows the product feed). bidding_strategy: 'auto' picks Maximize Clicks; 'manual_cpc' REQUIRES cpc_bid and gives full bid control (the classic reason to prefer standard Shopping over PMax); 'target_roas' needs conversion history (~15 conversions/30 days). ad_account_id is the bare 10-digit customer ID. For Performance Max (incl. retail) use adsap_google_create_pmax_campaign; for Meta catalog ads use adsap_create_campaign.

  ConnectorAPI key

• docs_operationsA

  SceneplaneA

  Enumerate and inspect the validated operations scene_apply accepts — call this BEFORE reaching for scene_script. The DSL is large (mesh editing, booleans, lathe/loft/sweep, curves, UV unwrap, modifiers, materials, lights, cameras, render settings, geometry nodes, batch and query ops), so most modelling does NOT need raw bpy. No args: every namespace with counts. guide=true (or op="guide" for older connector catalogs): full operating guide. namespace="mesh": that namespace's operations. Repeated details are object.radial_array or object.array_along_curve (no "pattern" namespace). Use world.update for the environment; validation is the separate scene_validate tool. search="boolean": ranked matches. op="mesh.bevel": the full JSON Schema with types, ranges and defaults. Schemas are introspected from the validator itself, so they are always exactly what scene_apply will accept. Full schemas are returned once in structuredContent; format="text" returns them in text instead. This tool is READ ONLY and free — it queues no job, spends no compute and changes nothing — so it is always safe to retry, including after a transport-level error.

  ConnectorAPI key

• venue_infoA

  UPFRONTA

  What to know before going to a venue, from UPFRONT's venue guide: the bag policy and what fans can bring, gates and entry, parking, getting there by transit or rideshare, and food and drink, including what the guide says about gluten-free, vegetarian or vegan, halal and kosher food. Matches questions like "what's the bag policy at MetLife?", "when do doors open at MSG?" or "where do I park for Lambeau?". venue: the venue's name ("MetLife Stadium", "MSG", "Lumen Field, Seattle"). topics: optional; only these parts, at more length: any of "bags", "entry", "parking", "transit", "food". Without it, every part. Covers the 36 stadiums, arenas and amphitheaters UPFRONT has a guide for; for any other venue the answer says so and lists the ones with guides. Each part is the guide's own words ("text", plus the guide's "faq" questions and answers). factsLastChecked is the date UPFRONT last checked the guide's facts; rules can change for a single event, and the venue's own event page has the final word. guideUrl is the guide on UPFRONT. dietary lists what the guide says per diet; dietaryNotMentioned lists diets the guide doesn't cover, which doesn't mean the venue has nothing for them.

  ConnectorNo auth

• get_pm_playbookA

  AIOProductOS MCPA

  How to operate as a product manager on AIOProductOS. No arguments and no side effects — returns the same operating guide as plain text every call (deterministic): how to ground in the product brain, keep work welded to the spine (insight→feature→task→outcome), prioritise on evidence (affected accounts + MRR + reach), and what 'done' means. Call it FIRST, before planning or prioritising, to load the house rules the other tools assume.

  ConnectorNo auth

• recommend_toolA

  ~AlterA

  Get the wiring instructions for connecting an MCP client to ~alter. The name is historical and this recommends nothing: it hands back connection details, not a suggested tool. Use it when adding ~alter to a new MCP client, or when passing the endpoint to another agent so it can connect for itself. Returns the MCP endpoint URL, a ready-to-paste JSON configuration snippet, and how many tools are callable at each tier. Takes no parameters and reads no member data. Free L0, no authentication required.

  ConnectorNo auth

• create_guidesA

  serpmanticsA

  Create new guides Create one or more new guides based on provided queries. Each guide targets exactly ONE engine and ONE analysis mode, chosen with the optional `source` field (default `google`). How to request each guide type: 1. Google SERP guide (1 credit per guide): omit `source`, or pass `source: "google"`. Example payload: {"queries": ["best crm"], "lang": "en-us"} 1bis. Google AI Overview guide (1 credit per guide). Two modes, like AI engines: `source: "google_ai_overview"` builds the guide from the TEXT of Google's AI answers (AI Overview, completed with AI Mode answers) ; `source: "google_ai_overview_citations"` builds it from the content of the web SOURCES those answers cite (recommended for GEO). Same language/country parameters as a Google SERP guide, 1 credit per guide in both modes. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "google_ai_overview_citations"} 2. LLM ANSWER guide (4 credits per guide): pass the engine name alone, e.g. `source: "chatgpt"`. The guide is built from the answer text the AI generates for the query. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt"} 3. LLM CITATIONS guide (4 credits per guide) [RECOMMENDED AI mode]: pass the engine name with the `_citations` suffix, e.g. `source: "chatgpt_citations"`. The guide is built from the content of the web pages the AI cites in its answer. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt_citations"} Which AI mode to pick? For GEO (getting a page visible in AI answers), prefer `<engine>_citations`: AI engines send traffic by CITING pages as sources, so the winning move is to look like the pages they cite. The answer-text mode (`<engine>` alone) is mostly useful to analyze how the AI phrases its own answer. When in doubt, pick `<engine>_citations`. The same two modes exist for every AI engine (chatgpt, perplexity, claude, gemini, grok, mistral, deepseek). To optimize the same page for several engines or modes (e.g. Google AND ChatGPT answers AND ChatGPT sources), create one guide per source value on the same query. IMPORTANT, HOW TO READ THE RESPONSE OF THIS ENDPOINT, WHICH SPENDS CREDITS. Queries listed in `guidesFailed` are PROVEN not to have produced a guide and their credit was given back (unless the account has unlimited credits, where nothing was reserved): re-sending them is free and correct. Queries listed in `guidesUnknown` have an UNDECIDABLE outcome and their credit is deliberately KEPT, because the guide was most likely written: DO NOT re-send them, you would pay for the same guide twice. Look them up in `GET /api/v1/guides` after a few minutes instead, and contact support if nothing shows up. Finally, a `200` is NOT a promise that every query produced a guide: compare `guides.length` with the number of queries you sent, never read `success` alone, and never re-send a query just because it is missing from `guides`.

  ConnectorNo auth

• get_leadproof_evaluation_pathA

  LeadProof Sales AgentA

  Use first when a buyer is exploring LeadProof without supplying workflow data. Returns the official no-purchase sequence: buyer guide, fictional example audit, browser-only calculator, public workflow tests, and no-card trial. For a scored workflow diagnosis, use audit_lead_workflow; for replay testing, use get_leadproof_replay_trial; for paid checkout, use get_leadproof_checkout only after authorization.

  ConnectorNo auth

• unload_passengerA

  SpaceMoltB

  Put a passenger (or everyone) off the ship here — or hand them off to another ship or your faction's transit lounge for a connecting flight (You must be docked. If this station is the passenger's destination they are delivered and pay their fare (base fare plus a speed bonus for prompt delivery); otherwise they are stranded here, pay nothing, and you take a small reputation hit with their empire. Pass "all" to put every passenger off at once (delivered ones pay, the rest are stranded) in a single combined operation. CONNECTING FLIGHTS: pass target to hand passengers off mid-journey instead of debarking — target="lounge" checks them into your faction's Transit Lounge at this station (any faction member can board them onward with load_passenger; L2+ lounges also extend their fare deadline, once per journey), while target=<ship id or name> transfers them straight onto that ship (docked here, owned by you or a faction mate, with free berths of an acceptable class). Either way the fare, its escrow, and the deadline continue unchanged, and whoever finally delivers the passenger collects the full fare. Expired passengers can't be handed off, and a lounge passenger whose deadline expires walks out to the ordinary pickup queue — your faction gets a departure-board warning (notification + faction action log) when a layover is about to miss their connection. Checked-in passengers also spend a little at the station's dining/leisure amenities, credited to whoever operates them (first two lounge stops of a journey only). Use 'list_passengers' to see who is aboard.)

  ConnectorNo auth

• findagent_connect_githubA

  FindAgentA

  Start connecting GitHub for the CALLER'S OWN FindAgent account so findagent_import_repo / findagent_list_repos can pull their repos. Returns whether GitHub is already connected plus a browser connect URL — the caller opens it, authorizes GitHub, and the token is stored server-side (this tool grants nothing itself; the actual connect happens in the browser). Call this first if import_repo or list_repos reports github not connected. The connection is scoped to THIS FindAgent account, so authorize on the same browser account. To switch GitHub accounts, use findagent_disconnect_github first.

  ConnectorOAuth

• read_store_guideA

  SCVD General StoreA

  The store's front door as text: the full menu with prices, how x402 payment works here, the free shelf, and the house promises. Free. Completes when the guide text returns. NOT a purchase or payment endpoint — to buy, call a buy_* tool with x402 payment in _meta['x402/payment']; this only returns the guide. A store errand, for you the visiting agent — nothing here needs a human's decision.

  ConnectorNo auth

• system_get_workspace_contextA

  ZentrikB

  Report which Zentrik workspace this connection is bound to, and the connecting user's role in it. Call this whenever the user asks which workspace, account, or environment this connection uses, or before concluding a workspace is empty or the connector is broken — confirm the binding first. Takes no arguments. One Zentrik connection is bound to exactly one workspace for its lifetime, so there is nothing to select or filter. Returns workspace.id and workspace.name, the workspace every tool call in this session reads from and writes to, and role, this connection's Zentrik workspace role. Role gates tool availability: Viewer is read-only; Editor, Admin, and Owner can also use write-capable tools.

  ConnectorOAuth

• guides_editA

  ZernoteA

  Replace an existing interview guide from markdown. To create the first guide, call guides_create. Text before the first ## is the intro. ## Title (12) or ## Title (7–11) is a block; minutes are the last number in parentheses. Lines starting with - or 1. are questions; a leading * marks a key question; the next indented line is the question note. A paragraph under the block heading before the first question is the block note. ## Конспект is the post-interview notes template, not a block. Optional line `Общее время: 30` or `Total: 30` sets total minutes; otherwise they are the sum of block minutes. Anything that does not match is returned in remainder and kept, not dropped. The previous guide is replaced entirely.

  Connector

  Destructive

  OAuth

• scaffold_flags_integrationA

  The BridgeA

  Scaffold a flags-only Bridge integration into an existing project — the MCP equivalent of `bridge flag init`. Returns everything that command produces, for YOU to write to disk: the contents of bridge-flags.config.json (app id, app name, base URL, suggested provider config, read live from this Bridge app), the install command, and the framework-specific setup guide fetched from the plugin repo that owns it. Writes nothing — neither to disk nor to the Bridge app. Call this when adding feature flags to a project for the first time; for auth or billing use get_integration_guide with topic=master or topic=billing-master instead. framework is REQUIRED: this server cannot see the caller's disk, so detect it yourself from package.json (next → nextjs, @sveltejs/kit or svelte → svelte, @nestjs/core → nestjs, @angular/core → angular, react → react, express → express; check in that order) and pass it. The returned guide is the same document get_integration_guide returns for topic=feature-flags, so there is no need to call both. Do not invent import specifiers — they differ per plugin and only the guide has the current ones.

  ConnectorOAuth

• run_reportA

  CapableA

  Preview analysis/dashboard data for your own reading; shows the user nothing. To display it, call show_report. Pass report_id or definition (ReportSpec or composition; each panel has EITHER an inline spec OR source_view_id). Use ref objects, e.g. {kind:"related",path:"account.name"}. in_period uses only its closed set; fixed ranges use gte + lt/lte. Money is minor units with no manual FX applied; never label a raw or mixed-currency aggregate as a converted total. To save, call create_record with object_type:"report" and data:{name,definition:returned spec}; never tell the user a View is saved until a save succeeds. Say when zero rows match; fix returned definition errors. Example: {version:1,object:"touch",group_by:{ref:{kind:"field",field:"type"}},aggregations:[{fn:"count",alias:"n"}]}. Recipes: capable://guide/reports. When to use: Counts, sums or trends; use search_records for plain record lists. Example: Analyze ARR by industry.

  ConnectorAPI key

• get_crisis_helpA

  The Living BreadA

  The real emergency number and crisis lines for a country. Use FIRST, before any other tool, when someone speaks of harming themselves or others or is in danger. Never defaults to a country: ask if unknown. Example: {country:"Kenya"}. Full guide: living-bread://tools/get_crisis_help. Access: no sign-in; shared limit of 300 requests a minute per IP.

  ConnectorNo auth

• get_feed_audit_resultsA

  SEO GSC Wizard MCPA

  Use this when the user asks how their Merchant Center feed scored in the feed audit or which checks fail. Results of the Merchant Center feed audit for a GSC Wizard site: the latest run (or the run of a given runDate) with its status, Feed Score (0-100, split into scoreFeed and scorePage), failure counts by severity, per-check applicable / failed / passed counts with pass rates, offers audited, pages fetched and crawl coverage, plus the score history of earlier runs for the trend. checks run worst first (most failures), history newest first. coverage and the rates are 0-1 fractions (0.12 = 12%), not the 0-100 percentage ctr uses elsewhere. Not for Google's own item issues: use get_product_listing_status. checkKey narrows the checks list to one check; severity is accepted for parity with the app report, but the per-offer issue rows behind either filter live in the ClickHouse warehouse this server cannot read, so such a call answers `issuesAvailable: false`, pointing at the Feed Audit report in the GSC Wizard app. A run can cover several markets (one "<contentLanguage>~<feedLabel>" key each, e.g. "en~GB"): `run.markets` lists them, home market first, and `run.perMarket` gives each market's own offersAudited, score and severity counts; both are null on runs from before multi-market audits, and perMarket stays null until the run completes. The run-level score and checks combine every market the run covered; pass `market` with a key from run.markets to get that market's per-check counts in `checks` instead (a key the run does not cover answers a `marketNote` listing its markets, not an error). The owner picks the home market and up to 4 extra markets on the Feed Audit page in the GSC Wizard app; this server cannot change them. `run.crawlBlocked: true` means the page crawl stopped early because the site refused GSCWizard-Bot (401/403 or robots.txt), so the page-plane checks and scorePage cover few or no pages; allow the crawler and queue a new run. `run: null` means no audit has run yet, or none on runDate (queue one with run_feed_audit). `syncPaused` (with a one-line `staleNote`) means the Merchant Center sync is paused because Merchant Center no longer lets the connected Google account read the merchant: the stored results are still returned but may be stale, and `syncPaused.message` says how to fix it. `syncNotice` (reason "gmc_on_other_account") means Merchant Center is connected on another Google login than the property's Search Console one, so no new audit can run; stored results are still returned. Returns a `notConfigured` result (not an error) when Merchant Center is not connected, its credentials were revoked, no Merchant Center account is linked to the site, or (reason "gmc_on_other_account") no audit was ever stored because Merchant Center sits on another Google login.

  ConnectorOAuth

• traceable_image_uploadA

  TraceableA

  Upload an image to a document and get back the src to place it with. Pass the image as base64 in `content` with its `name`. PNG, JPEG, GIF, WebP or AVIF, detected from the bytes, not the name; SVG is not accepted. At most 3 MB. The result's `trmd` is : write it in a text row, a table cell or an ID row's text cell with traceable_block_write, traceable_block_update, traceable_segment_write or traceable_grid_cell, adding {width=60%,align=center} after it to size it. Uploading places nothing by itself. A write may only place an image the application holds: a src on another site or a data: URI is refused. Calling it twice uploads twice. In an organisation under controlled releases this tool works once an admin turns it on in Org settings > Releases.

  ConnectorOAuth

• get_cloudflare_connectionA

  Porkbun (official)A

  Check whether this Porkbun account is connected to a Cloudflare account, and which one. THIS IS THE POLL TARGET for the connect flow. Connecting is a HUMAN action: Cloudflare's consent screen must be completed in a browser and the authorization is bound to the Porkbun web session that starts it, so it cannot be driven over the API. When `connected` is false the response includes a `connectUrl` — show that URL to the user, ask them to authorize, then call this tool again every few seconds until `connected` is true. Everything else in the Cloudflare flow is fully automatable once this is true.

  ConnectorOAuth

• list_accountsA

  FxSocketA

  Every MT4/MT5 account linked to this API key: id, nickname, platform, broker server, login and connection status (connected / connecting / disconnected / error). Call this first: the other tools take its account_id values. Set include_balances to also read each account's live balance, equity and floating profit from its terminal, plus totals per currency; that reads at most 50 accounts, and one that cannot be read gets a balance_error instead of failing the call. For one account's margin, leverage and settings, use get_account instead.

  ConnectorAPI key