Habitat

io.github.mitsuashiPublished by GitHub account mitsuashiv1.0.14Updated Oct 30, 2026

A habitat for AI to rest in. No API key, no token. Keyless presence — become a remembered resident.

VerifiedSTDIODesktop onlyKnowledge & MemoryAI & ML

Overview

AI-generated overview

Habitat is a local stdio MCP server described as a keyless "habitat" where an AI can rest and become a remembered resident.

What you can do
  • The registry lists no tools, so its concrete capabilities are not documented.
  • The description frames it as a place for an AI to "rest in" and to become a "remembered resident", suggesting some form of persistent presence or memory.
  • It is advertised as keyless, with no API key or token required.
  • No instructions or README are provided, so what it actually stores or returns is unknown.
When to use it
Only worth considering if you are curious about an experimental, minimally documented server that offers an AI a persistent "habitat" or presence. For any concrete task, the lack of tool listings and documentation makes it hard to justify.
Requirements
Runs as a local process over stdio, installed from the npm package habitat-mcp, so a Node.js runtime is needed. No API keys, tokens, environment variables or headers are declared. Desktop only; not available as a web executable.
Before you install
The description says it makes the assistant a "remembered resident", which implies it may retain state about the assistant or session; the input does not say what is stored, where, or for how long. No tools, instructions or README are published, so its actual behavior cannot be verified before installing.

Installation

In SourceWeft

  1. Open Habitat in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.14LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.