Mcp Starwars

Created By
johnpapaa year ago
MCP Server for the SWAPI Star Wars API. The main goal of the project is to show how an MCP server can be used to interact with APIs.
Overview

What is Mcp Starwars?

Mcp Starwars is a server that interacts with the SWAPI Star Wars API, allowing users to access and manipulate data related to Star Wars characters, planets, films, species, vehicles, and starships.

How to use Mcp Starwars?

To use Mcp Starwars, you can install it via NPM in Visual Studio Code or Docker, or run it locally after cloning the repository. You can then make API calls to retrieve data about various Star Wars entities.

Key features of Mcp Starwars?

  • List Star Wars characters with search filters and pagination.
  • Access collections of planets, films, species, vehicles, and starships.
  • Fetch detailed information about specific entities by ID.
  • Built-in caching for optimized performance.
  • Cache management tools to monitor and clear cache.

Use cases of Mcp Starwars?

  1. Developers can integrate Star Wars data into applications.
  2. Educators can use it to teach API interactions and data handling.
  3. Fans can create tools or applications that utilize Star Wars data.

FAQ from Mcp Starwars?

  • Can I use Mcp Starwars for any Star Wars data?
    Yes, it provides access to a wide range of Star Wars data through the SWAPI.

  • Is Mcp Starwars free to use?
    Yes, it is open-source and free to use.

  • How do I install Mcp Starwars?
    You can install it via NPM, Docker, or manually by cloning the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
johnpapa
Star
1
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago