Hippycampus

Created By
cromwelliana year ago
An (eventually) secure open-source MCP Server to turn any REST endpoint into MCP resources automatically
Overview

what is Hippycampus?

Hippycampus is an open-source MCP (Microservices Communication Protocol) server that automatically converts any REST endpoint into MCP resources, facilitating seamless integration and communication between services.

how to use Hippycampus?

To use Hippycampus, install the required dependencies, configure your Google AI Studio API key, and run the application in either CLI mode or MCP server mode.

key features of Hippycampus?

  • Dynamic loading of OpenAPI specifications
  • Integration with Langflow for visual workflow creation
  • CLI and MCP server modes for flexible usage

use cases of Hippycampus?

  1. Transforming REST APIs into MCP resources for microservices architecture.
  2. Creating visual workflows using Langflow to manage service interactions.
  3. Facilitating real-time communication between services using SSE (Server-Sent Events).

FAQ from Hippycampus?

  • What are the prerequisites for using Hippycampus?

You need Python 3.12.9, UV package manager, and a Google AI Studio API key.

  • How do I run the MCP server?

Use the command uv run hippycampus-server --transport sse --port 8000 to start the server.

  • Can I use custom components in Langflow?

Yes! You can load OpenAPI specifications and connect to the Hippycampus MCP server using Langflow.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cromwellian
Star
0
Language
Python
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)

a day ago