habitat

Created By
dawsonlpa year ago
This is a set of collaborating components which together make it easy to manage, develop, use and migrate MCP servers both locally and on the net.
Overview

what is Habitat?

Habitat is a set of collaborating components designed to simplify the management, development, usage, and migration of Model Context Protocol (MCP) servers both locally and on the internet.

how to use Habitat?

To use Habitat, deploy the components in your desired environment (local, hybrid, or cloud) and utilize the Habitat CLI for managing the lifecycle of MCP servers and services.

key features of Habitat?

  • Comprehensive architecture for managing MCP servers
  • Unified command-line interface for lifecycle management
  • Service discovery and orchestration through the MCP Registry
  • Support for local, hybrid, and cloud deployment models

use cases of Habitat?

  1. Managing MCP servers in a local development environment using Docker.
  2. Deploying MCP servers in a cloud environment for scalability.
  3. Integrating with external services like Jira and GitHub through service adapters.

FAQ from Habitat?

  • What is the purpose of the MCP Registry?

The MCP Registry serves as a central discovery service for managing and authenticating MCP servers.

  • Can Habitat be used for both local and cloud deployments?

Yes! Habitat supports local, hybrid, and cloud deployment models.

  • How does Habitat ensure security?

Habitat implements multiple layers of authentication and authorization to secure communication between clients and servers.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dawsonlp
Star
0
Language
-
License
GPL-3.0 license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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