Studio Ghibli

What Studio Ghibli MCP server does

The Studio Ghibli MCP server gives MCP-compatible clients access to data from ghibliapi.vercel.app, a fan-built API covering Studio Ghibli films and related entities. It supports both collection queries and individual-record lookups for films, people, locations, species, and vehicles.

Collection tools accept an optional limit argument. Detail tools accept an id, allowing an agent to retrieve one film, person, location, species, or vehicle. The package is keyless, so the documented configurations do not require an API token or account.

How it works

You can connect to the hosted Pipeworx endpoint at https://gateway.pipeworx.io/studio-ghibli/mcp. That endpoint lists the Studio Ghibli tools together with shared Pipeworx meta-tools, including ask_pipeworx, discover_tools, search_within, and memory-related tools. The exact tool scope is reported by the MCP initialize response and may change.

The hosted endpoint can route questions beyond this data pack through ask_pipeworx. Alternatively, the full Pipeworx endpoint at https://gateway.pipeworx.io/mcp exposes the wider catalog directly. Both hosted URLs use the same gateway and data-source infrastructure; the difference is which pack appears directly in the tool list.

A local installation runs as a standard stdio MCP process. The standalone Studio Ghibli MCP server exposes only the pack’s own tools and does not include the gateway meta-tools or cross-catalog routing.

Setup and configuration

For a hosted connection, add the following MCP server configuration to a compatible client:

{
  "mcpServers": {
    "studio-ghibli": {
      "url": "https://gateway.pipeworx.io/studio-ghibli/mcp"
    }
  }
}

For local stdio use, configure the package through npx:

{
  "mcpServers": {
    "studio-ghibli": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-studio-ghibli"]
    }
  }
}

You can also verify that the local process starts with npx -y @pipeworx/mcp-studio-ghibli. The local mode needs no Pipeworx account and avoids a gateway round trip. The README also documents direct HTTP calls, such as posting to /v1/tools/films with a JSON limit value.

Tools and capabilities

The Studio Ghibli MCP server provides these pack-specific tools:

• films(limit?) lists films.
• film(id) retrieves one film.
• people(limit?) lists characters.
• person(id) retrieves one character.
• locations(limit?) lists locations.
• location(id) retrieves one location.
• species(limit?) lists species.
• species_one(id) retrieves one species.
• vehicles(limit?) lists vehicles.
• vehicle(id) retrieves one vehicle.

For natural-language requests, ask_pipeworx can select a tool and populate its arguments when using a gateway connection. That capability belongs to the gateway configuration, not the standalone package.

Limitations and notes

The underlying source is a fan-built API, not identified in the documentation as an official Studio Ghibli data service. Hosted pack connections include shared gateway schemas in addition to the pack tools, which can increase the tool count and context size. A standalone connection avoids those extra schemas but also cannot use ask_pipeworx for broader routing.

The documented HTTP and hosted MCP examples do not require an account for the first calls. The package is released under the MIT license.