
Wraps the free Star Wars API at swapi.dev so you can query films, characters, planets, species, starships, and vehicles from the Star Wars universe without dealing with HTTP calls directly. Hosted by Pipeworx as a streamable HTTP gateway, meaning no local install or API keys needed. You can wire it up standalone or use it through the full Pipeworx gateway that bundles 250+ data sources. Includes an ask_pipeworx helper that interprets plain English questions and routes them to the right endpoints automatically. Useful for prototyping, building Star Wars themed demos, or testing MCP integrations with a familiar dataset that won't rate limit you.
Public tool metadata for what this MCP can expose to an agent.
planetsList all planets2 paramsList all planets
pagenumbersearchstringplanetGet a details of a planet by id1 paramsGet a details of a planet by id
idstringpeoplesList all peoples2 paramsList all peoples
pagenumbersearchstringpeopleGet a details of a people by id1 paramsGet a details of a people by id
idstringfilmsList all films2 paramsList all films
pagenumbersearchstringfilmGet a details of a film by id1 paramsGet a details of a film by id
idstringspeciesList all species2 paramsList all species
pagenumbersearchstringspecieGet a details of a specie by id1 paramsGet a details of a specie by id
idstringvehiclesList all vehicles2 paramsList all vehicles
pagenumbersearchstringvehicleGet a details of a vehicle by id1 paramsGet a details of a vehicle by id
idstringstarshipsList all starships2 paramsList all starships
pagenumbersearchstringstarshipGet a details of a starship by id1 paramsGet a details of a starship by id
idstringSWAPI MCP — wraps the Star Wars API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
search_people | Search Star Wars characters by name. Returns name, physical attributes, birth year, gender, and homeworld URL. |
get_planet | Get a Star Wars planet by its numeric ID. Returns name, climate, terrain, population, and orbital data. |
get_starship | Get a Star Wars starship by its numeric ID. Returns name, model, manufacturer, crew capacity, and hyperdrive rating. |
get_film | Get a Star Wars film by its numeric ID. Returns title, episode number, director, producer, release date, and opening crawl. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"swapi": {
"url": "https://gateway.pipeworx.io/swapi/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/swapi/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Swapi data" })
The gateway picks the right tool and fills the arguments automatically.
MIT