bitHuman docs

ai.bithumanPublished by bithuman.aiOfficial publisherv1.0.1Updated Oct 24, 2026

The bitHuman docs over MCP: two read-only tools, search and fetch; it needs no account and no key.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

A remote, read-only MCP server that lets an assistant search and fetch bitHuman documentation on real-time avatar SDKs, the REST API, deployment, models and定价.

What you can do
Search bitHuman documentation and get ranked results with titles, sections, URLs and short snippets, up to 20 per query (default 8). Fetch any documentation page as full markdown by the id returned from search or by its full docs.bithuman.ai URL. Retrieve page metadata along with the complete text for reference or quoting.
When to use it
Use it when you need authoritative answers about bitHuman's real-time avatar SDKs, REST API, deployment options, models or pricing, and want the assistant to read the actual documentation pages rather than rely on memory.
Requirements
A remote streamable HTTP endpoint at docs.bithuman.ai. No account, API key, environment variable or header is declared, and no local package is needed.
Before you install
Read-only tools; no writes, payments or credentials are involved. Search results and fetched pages come from a third-party documentation site, so treat their content as reference rather than instructions.

Installation

In SourceWeft

  1. Open bitHuman docs in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.bithuman%2Fdocs/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "bithuman-docs": {
      "type": "http",
      "url": "https://docs.bithuman.ai/docs-mcp"
    }
  }
}

Tools

2

fetch

Fetch a bitHuman docs page

Fetch one docs page as markdown by the id `search` returned (a path such as /platforms/python), or by its full docs.bithuman.ai URL. Returns JSON {id, title, text (the whole page as markdown), url, metadata}. Example: {"id": "/api/agents"}. Errors: an unknown path (run `search` for the id) and a URL outside docs.bithuman.ai are refused. Read-only, no sign-in.

Parametersidrequired

Version history

2
  1. v1.0.1LatestOct 5, 2026
  2. v1.0.0Sep 30, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Bithuman integrations