ExducerAI GPU cloud

● Active

ai.exducer/turbo

Rent whole RTX PRO 6000 Blackwell GPUs in Montréal: quote, book, connect, stop, billing.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "turbo": {
      "url": "https://exducer.ai/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http turbo https://exducer.ai/mcp
VS Code
code --add-mcp '{"name":"turbo","type":"http","url":"https://exducer.ai/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
AI & Agents
Version
1.0.2
Registry
active
Published
11/19/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Mostly fine: ExducerAI GPU cloud is maintained, hosted endpoint answering without a key.

Maintained
Active
Last commit 3 days ago (Nov 19, 2026), 0 open issues.
Official registry
Active
Published as ai.exducer/turbo in the official MCP registry, version 1.0.2.
Source
No licence found
Public repository, but GitHub reports no recognised licence (0 stars). Check the README before shipping it in a product.
Runs
Hosted by the publisher
Your client talks to exducer.ai: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 10:07 UTCStatus history & uptime →
● Working174 msprotocol 2025-06-18v1.0.2tools

The endpoint answered the MCP handshake as "ExducerAI" and listed 22 tools. Answering since Nov 19, 2026.

Context cost ≈ 4.1k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 22 tools.

Tools (22)

  • List prices in CAD: GPU-hour per GPU model, object storage per GB-month, and the Models API. Use this instead of any remembered price.

  • One yes or no per GPU model: is it free right now. A no does not block a request; the request waits for capacity.

  • The public status of each service (console, API, GPU region, object storage, Models API).

  • list_servers

    The servers a booking can name: id (the server_id of quote_booking and create_booking), GPU model, price per GPU-hour in CAD, allowed_gpu_counts, region, and whether it is free now.

  • The templates a booking can name: slug, name, the container image it runs, category. Without a template a deployment runs the default PyTorch image.

    Show parameters
    • categorystringOnly this category slug.
    • qstringFree-text filter.
  • quote_booking3 params

    What a booking would cost in CAD: GPU cost, tax and total for the whole duration, and the hourly rates. Books nothing and charges nothing. Always quote and show the user the total before create_booking.

    Show parameters
    • server_idstringrequiredServer id from list_servers.
    • gpusintegerrequiredNumber of GPUs: one of the server's allowed_gpu_counts.
    • hoursintegerrequiredDuration in hours.
  • search_docs2 params

    Search the documentation by keyword. Returns the matching sections with a snippet and the slug to pass to read_doc.

    Show parameters
    • querystringrequiredWhat to look for, in a few words.
    • limitintegerHow many sections to return.
  • read_doc1 param

    One documentation page as Markdown, by its slug (from search_docs). Read the page before answering a question about how the platform works.

    Show parameters
    • slugstringrequiredThe page slug, e.g. c-provisioning (from search_docs).
  • The account behind the API key (email, company, type), whether the key is a sandbox key, and the prepaid balance in CAD (simulated under a sandbox key).

  • list_deployments1 param

    Every deployment of the account with its state, GPU count, rate, cost so far and end time. States: requested, queued, provisioning, running, then stopped, ended, failed or cancelled.

    Show parameters
    • include_sandboxbooleanOn a live key, also list sandbox deployments.
  • get_deployment1 param

    One deployment in full: state and reason, SSH host and port, the host key fingerprint to verify, rate per GPU-hour, cost so far, start and end time, endpoints.

    Show parameters
    • idstringrequiredThe deployment id (rnt_… on a live key, snd_… in the sandbox).
  • get_deployment_events2 params

    The state changes of a deployment, oldest first, each with its reason, actor and time. Read this to learn why a deployment failed, ended or is waiting.

    Show parameters
    • idstringrequiredThe deployment id (rnt_… on a live key, snd_… in the sandbox).
    • limitintegerHow many events.
  • wait_for_deployment3 params

    Poll a deployment until it reaches a state (default running) or a final state, for at most 50 seconds per call. Returns reached, the current state and whether it is final. While reached is false and final is false, call again; a live request can stay requested until staff place it, so after a few minutes tell the user and check back later instead of looping.

    Show parameters
    • idstringrequiredThe deployment id (rnt_… on a live key, snd_… in the sandbox).
    • untilstringThe state to wait for.
    • timeout_secondsintegerHow long to wait in this call.
  • get_billing1 param

    The prepaid balance and the most recent credit ledger lines (top-ups and charges) in CAD.

    Show parameters
    • limitintegerHow many ledger lines, newest first.
  • get_usage4 params

    What the account was charged for GPU time, object storage and the Models API over a date range, in CAD before tax. Only deployments that ran appear.

    Show parameters
    • fromstringFirst day, YYYY-MM-DD, America/Toronto. Default: the first of the month.
    • tostringLast day, YYYY-MM-DD, included. Default: today.
    • groupstringday: one row per day and type. type: one row per type for the range.
    • deployment_idstringOnly the GPU time of this deployment.
  • The account's invoices (not available to a sandbox key).

  • list_ssh_keys

    The SSH public keys saved on the account: a booking with no ssh_public_key uses them (not available to a sandbox key). Adding or removing keys is done by the user in the console.

  • get_storage_usage

    Object storage: GB stored, active keys, price per GB-month and the amount billed this month (not available to a sandbox key).

  • Send a GPU request. It is created as requested or queued and becomes running later (use wait_for_deployment); nothing is charged before it runs, then credit is drawn per minute. Quote first with quote_booking and get the user's yes on the total. Retry-safe: see idempotency_key.

    Show parameters
    • server_idstringrequiredServer id from list_servers.
    • gpusintegerrequiredNumber of GPUs: one of the server's allowed_gpu_counts.
    • hoursintegerrequiredDuration in hours. A live booking has a minimum (the API answers duration_below_minimum under it).
    • ssh_public_keystringThe text of the user's SSH public key (.pub), one key per line. Left out, the keys saved on the account are used. Required with a sandbox key.
    • templatestringTemplate slug from list_templates. Left out: the default PyTorch image.
    • imagestringA container image instead of a template. Only images the platform already runs are accepted.
    • notesstringA note for the staff who place the request.
    • client_referencestringYour own reference for this deployment; unique among the account's live deployments.
    • auto_renewbooleanRenew by itself at the end of the term while credit lasts.
    • renew_hoursintegerThe renewal block in hours.
    • sandbox_scenariostringSandbox keys only: the lifecycle to simulate.
    • sandbox_speedintegerSandbox keys only: shorten every simulated wait this many times.
    • idempotency_keystringOptional. 8 to 128 characters. Reuse the same value when retrying the same request. Left out, one is derived from the request and the UTC date, so the identical
    • confirmbooleanrequiredMust be true. It states that the user approved this exact action after seeing what it does and costs. With a sandbox key (tml_test_…) nothing is real and it may
  • extend_deployment4 params

    Add hours to the term of a deployment that is requested, queued, provisioning or running. Same machine, same SSH details; billing stays per minute. Tell the user the extra cost (hours × gpu_count × rate) and get a yes first. Retry-safe: see idempotency_key.

    Show parameters
    • idstringrequiredThe deployment id (rnt_… on a live key, snd_… in the sandbox).
    • hoursintegerrequiredHours to add. The new end may not be more than 720 hours away.
    • idempotency_keystringOptional. 8 to 128 characters. Reuse the same value when retrying the same request. Left out, one is derived from the request and the UTC date, so the identical
    • confirmbooleanrequiredMust be true. It states that the user approved this exact action after seeing what it does and costs. With a sandbox key (tml_test_…) nothing is real and it may
  • set_auto_renew4 params

    Turn automatic renewal of a deployment on or off. On, it keeps running and drawing credit past its end time until it is turned off or credit runs short, so get the user's yes first.

    Show parameters
    • idstringrequiredThe deployment id (rnt_… on a live key, snd_… in the sandbox).
    • enabledbooleanrequiredtrue: renew at the end of each term while credit lasts. false: end as booked.
    • renew_hoursintegerThe renewal block in hours (default 720).
    • confirmbooleanrequiredMust be true. It states that the user approved this exact action after seeing what it does and costs. With a sandbox key (tml_test_…) nothing is real and it may
  • stop_deployment2 params

    Stop a deployment now: billing ends at this minute and its container and NVMe scratch disk are deleted and cannot be recovered. A request that has not started is withdrawn at no cost. Make sure results are copied off, tell the user the disk is deleted, and get a yes first.

    Show parameters
    • idstringrequiredThe deployment id (rnt_… on a live key, snd_… in the sandbox).
    • confirmbooleanrequiredMust be true. It states that the user approved this exact action after seeing what it does and costs. With a sandbox key (tml_test_…) nothing is real and it may

Checked by Serverdex with a plain initialize + tools/list call to exducer.ai/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 21, 2026
Stars
0
Forks
0
Last push
Nov 19, 2026
License
—

Python

From the README

ExducerAI GPU cloud for coding agents ExducerAI rents whole GPUs in Montréal by the hour and serves an OpenAI-compatible Models API. This repository is the kit that lets a coding agent use it for you: check availability, quote, book, wait, connect over SSH, stop, and read billing, with your approval at every step that costs money. The MCP server and the API are hosted services. Their code is not in this repository. The setup text, the skills and the CLI here are copies of what exducer.ai serves; if a copy and the site ever differ, the site is right (sh scripts/check-against-site.sh compares). Set up with one prompt Paste this into Claude Code, Codex, Cursor or another coding agent: The agent installs the CLI, asks you to create an API key and to type it into turbo login yourself, then installs the skills and registers the MCP server. The steps it follows are in SETUP.md. Start with a sandbox key (https://cloud.exducer.ai, Account, then API keys, with the Sandbox key option). It runs the same commands against a simulated lifecycle, so the agent can rehearse a booking from request to stop and nothing is charged. Set up by hand turbo agent setup --dry-run prints the changes without making them, and turbo agent remove undoes them. More in cli/README.md. In Claude Code the skills and the server also install as a plugin.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://exducer.ai/mcp

The most-starred AI & Agents servers in the index, with their live-check result.

ServerStarsLast pushLive check
Ruflo81,994Nov 2026Local / not checked
Claude Flow81,985Nov 2026Local / not checked
CodeBurn11,880Nov 2026Local / not checked
Kaneo9,825Nov 2026Local / not checked
Ha MCP7,958Nov 2026Local / not checked

ExducerAI GPU cloud: questions people ask

Is ExducerAI GPU cloud a remote or a local MCP server?
According to its entry in the official MCP registry, ExducerAI GPU cloud ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does ExducerAI GPU cloud need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is ExducerAI GPU cloud safe to use?
Mostly fine: ExducerAI GPU cloud is maintained, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: No licence found; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is ExducerAI GPU cloud still maintained?
Active: the repository's last commit 3 days ago. Last push Nov 19, 2026, 0 GitHub stars. Read from GitHub on Nov 21, 2026.
What tools does ExducerAI GPU cloud expose?
22 tools as listed by the server itself during the live check, including get_pricing, check_availability, get_service_status, list_servers, list_templates. The full list with parameters is in the Live check section above.
How do I add ExducerAI GPU cloud to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all AI & Agents →

Add the badge to your site

Show visitors that ExducerAI GPU cloud is listed here — it’s also the link we check for a free listing.

ExducerAI GPU cloud — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/ai-exducer-turbo?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="ExducerAI GPU cloud — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![ExducerAI GPU cloud — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/ai-exducer-turbo?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/ai-exducer-turbo) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/ai-exducer-turbo) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/ai-exducer-turbo)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/ai-exducer-turbo"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/ai-exducer-turbo"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/ai-exducer-turbo"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).