Hydracept

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Computer or cloud
• Transport: stdio, Streamable HTTP
• Category: Other
• You need to fill in: HYDRACEPT_API_KEY

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet
• PyPIPython’s uv installed (for the uvx command)

Which app do you use?

{
  "mcpServers": {
    "hydracept": {
      "command": "uvx",
      "args": [
        "hydracept",
        "mcp",
        "serve"
      ],
      "env": {
        "HYDRACEPT_API_KEY": "your-value",
        "HYDRACEPT_MCP_TOOL_PROFILE": "your-value"
      }
    }
  }
}

claude mcp add --transport http hydracept https://api.hydracept.com/mcp --header 'Authorization: Bearer {HYDRACEPT_API_KEY}'

claude mcp add hydracept --env HYDRACEPT_API_KEY=your-value --env HYDRACEPT_MCP_TOOL_PROFILE=your-value -- uvx hydracept mcp serve

{
  "mcpServers": {
    "hydracept": {
      "url": "https://api.hydracept.com/mcp",
      "headers": {
        "Authorization": "Bearer {HYDRACEPT_API_KEY}"
      }
    }
  }
}

{
  "mcpServers": {
    "hydracept": {
      "command": "uvx",
      "args": [
        "hydracept",
        "mcp",
        "serve"
      ],
      "env": {
        "HYDRACEPT_API_KEY": "your-value",
        "HYDRACEPT_MCP_TOOL_PROFILE": "your-value"
      }
    }
  }
}

{
  "servers": {
    "hydracept": {
      "type": "http",
      "url": "https://api.hydracept.com/mcp",
      "headers": {
        "Authorization": "Bearer {HYDRACEPT_API_KEY}"
      }
    }
  }
}

{
  "servers": {
    "hydracept": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "hydracept",
        "mcp",
        "serve"
      ],
      "env": {
        "HYDRACEPT_API_KEY": "your-value",
        "HYDRACEPT_MCP_TOOL_PROFILE": "your-value"
      }
    }
  }
}

Your choice stays on this device in a cookie; no account needed.

Values you fill in

• HYDRACEPT_API_KEY secret required env
  Hydracept API key from https://hydracept.com/start (or use project secrets after init)
• HYDRACEPT_MCP_TOOL_PROFILE env
  Stdio MCP tools/list for the process lifetime: full (default when unset) or compact (eleven lifecycle tools). Hosted POST /mcp defaults to compact for new API keys; POST /mcp/full always lists all sp…
• Authorization HTTP header

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

• hydracept_workspace_status

  Check workspace/session authentication and readiness, plus common setup errors. Use when setup, auth, or project binding is in doubt; use hydracept_job_status for a specific execution. Does not execute capabilities or spend money. Hosted requires bearer (WORKSPACE_KEY_REQUIRED wh

• hydracept_capabilities

  Browse or fetch capability descriptors (keys, modes, schemas). Use hydracept_resolve_capability when routing from intent alone. List/resolve is keyless; a bearer key may add project-scoped fields. No charge. Read-only. Returns: Capability list or single CapabilityDescriptor when

• hydracept_resolve_capability

  Match the user's goal to a capability key using natural language. Use when the key is unknown; use hydracept_capabilities when you already have a key or need the catalog. Keyless. No charge. Read-only. Returns: CapabilityResolutionResponse with ranked keys and rationale. Errors:

• hydracept_quote_capability

  Preview what a run would cost — does not execute, create a job, or charge the wallet. Use before spending when the user asks about price; use hydracept_run or hydracept_submit_job only to execute. Not the same as request_capability_quote (POST /mcp/full) on the full profile (huma

• hydracept_run

  Run a capability (paid). Use when the user wants execution — not for quotes (hydracept_quote_capability), status (hydracept_job_status), or receipts (hydracept_get_receipt). Default wait=true waits until the job finishes; use hydracept_submit_job when this call must return immedi

• hydracept_submit_job

  Start a capability job and return its id immediately (paid). Use when execution is required but this MCP call must not block — not for quotes or status checks. Prefer hydracept_run when waiting is acceptable. Poll with hydracept_job_status. Same billing as hydracept_run. Requires

• hydracept_job_status

  Read one job's current status. Use after hydracept_submit_job or hydracept_run with wait=false; use hydracept_get_receipt after success. If the job id is unknown, use hydracept_jobs_find first. Requires bearer key. No charge. Returns: HydraceptJob status projection for the jobId.

• hydracept_cancel_job

  Request cancellation of one job. Use only when the user explicitly asks to cancel the job itself; stopping a local polling loop is not a cancellation. Returns whether the request was accepted, whether the job is already terminal, and the next action. Never promise that upstream p

• hydracept_get_receipt

  Read billing and provenance for a finished job. Does not run capabilities or spend money. Use after terminal success; use hydracept_job_status while still running. Hosted MCP accepts job_id only. Requires bearer key. No charge. Returns: HydraceptReceipt JSON for a terminal job. E

• hydracept_download_artifact

  Fetch artifact metadata (and SHA-256 on hosted MCP) for a succeeded job output. Stdio may also write bytes when output_path is set. Requires bearer key. No charge on hosted. Returns: Artifact downloadUrl, mediaType, sha256 (hosted does not write local files). Errors: WORKSPACE_KE

• hydracept_jobs_find

  Find a prior job in the bound project when you do not have its id. intent is recent, failed, or reusable. The list never includes prompt text. Use after context loss, for failure triage, or to recover a job to cancel. Requires bearer key. No charge. Read-only. Returns: Matching j

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain hydracept.com (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 113 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 11 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 18676 servers in this category
• Published to the registry more recently than 78% of the other 18676 servers in this category
• Basic checks equal to or better than 100% of the other 18676 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

pip install -U hydracept

python -m hydracept run image.generate.v1 --prompt "transparent 1024x1024 blue slime icon" --json

from hydracept.client import HydraceptClient

python -m hydracept capabilities find "generate an image"

python -m hydracept init --apply --yes --json   # binds MCP to workspace secrets; reload MCP if prompted