Insitu
Insitu
Ситуативная идентичность для агентов. Кто вы здесь.
Insitu хранит многократно используемые стансы (разделы постоянных инструкций) и собирает их в протокол для проекта, в котором вы находитесь. materialize записывает этот протокол в файлы, которые хост уже внедряет при старте сессии. Вы создаёте контент с помощью list_stanzas и сводок по размерам. Агенты используют resolve_protocol для просмотра и получения стансов с пометкой available.
Он не моделирует репозитории, компоненты или системные факты. Это инструмент контекста разработки (ContextForge в эталонной конфигурации). Эти два инструмента должны работать бок о бок.
Статус
Дизайн зафиксирован 2026-08-17 (DESIGN.md v0.5). Путь чтения, роли (§6.1), validate / where_used и materialize реализованы. Инструменты изменений ждут окончания первого догфудинга. Актуальный следующий шаг: STATUS.md.
Related MCP server: Home Lab Context MCP
Установка
Требуются Python 3.11+ и uv.
cd insitu
uv sync
uv run pytest
uv run insituuv run insitu запускает MCP-сервер на stdio.
Корень хранилища
Одно хранилище на процесс, в этом порядке:
INSITU_HOME--vault /path/to/vault~/.insitu
Новое хранилище — это просто папки на диске (stanzas/, projects/, опциональный config/surfaces.yaml). examples/vault/ в этом репозитории — вымышленный пример, на который можно указать:
uv run insitu --vault examples/vaultНе копируйте личное хранилище в этот публичный репозиторий.
Добавьте MCP-сервер в хост
См. install/mcp.json.examples.md с фрагментами для Cursor, Claude Code и Grok. Типичный вид:
{
"mcpServers": {
"insitu": {
"command": "uv",
"args": ["run", "--directory", "/path/to/insitu", "insitu"],
"env": { "INSITU_HOME": "/path/to/your/vault" }
}
}
}Скопируйте три маршрутизатора (один раз, глобально для пользователя)
Маршрутизаторы сообщают хосту, что Insitu существует. Они не являются проектным протоколом.
Хост | Откуда копировать | Куда копировать |
Cursor |
|
|
Claude |
|
|
Grok |
|
|
Опционально: вставьте install/AGENTS.md в файл конституции вручную. materialize никогда не записывает AGENTS.md, CLAUDE.md или CLAUDE.local.md.
Включите адаптеры хостов в хранилище с помощью config/surfaces.yaml (grok, claude, cursor). Затем из рабочей копии проекта вызовите materialize. Он запишет PROTOCOL.md и файлы адаптеров в .grok/rules/, .claude/rules/ и .cursor/rules/.
Целевое использование
# you, after a vault or map change
materialize # PROTOCOL.md + host adapters (.grok/.claude/.cursor rules)
# agent, live / on demand
resolve_protocol # inspect weight, refresh, compare to the materialized header
get_stanza ... # pull an available stanza
# you, registering a new project
list_stanzas # what exists, and how heavy each piece is
link_stanza ... # after the write path exists
get_project # how heavy is this project's protocol?Разработка
uv sync
uv run pytest
uv run insituPython 3.11+, FastMCP. Смотрите AGENTS.md, если вы агент, работающий в этом репозитории.
Лицензия
MIT. Смотрите LICENSE.
Available Tools
44 toolscreate_projectC
Create a project map and optional notes. Creating _global when missing is allowed.
Inputs: project (required), working_folder (required), aka, why, +8 more. Returns: object
create_roleB
Create a role file. The new role is on no project. Optional why is for the git message only.
Inputs: role_id (required), why, core, name, +2 more. Returns: object
create_skillA
Create skills//SKILL.md. Does not auto-link. Optional why writes provenance/skills/.md.
Inputs: content (required), skill_id (required), description (required), why. Returns: object
create_stanzaA
Create a stanza and append a why-log entry. Does not link it to a project. Subject to review policy.
Inputs: why (required), title (required), content (required), stanza_id (required), +3 more. Returns: object
delete_projectA
Delete a project directory. Preview unless confirm=true with the preview's expected. Cannot delete _global. Do not call unless the user explicitly asked to delete this project. Findings are not a reason to delete.
Inputs: project (required), working_folder (required), why, confirm, +1 more. Returns: object
delete_roleA
Delete a role. Preview unless confirm=true with the preview's expected. Do not call unless the user explicitly asked to delete this role. Findings are not a reason to delete.
Inputs: role_id (required), why, confirm, expected. Returns: object
delete_skillB
Delete a skill. Preview unless confirm=true with the preview's expected. Do not call unless the user explicitly asked to delete this skill.
Inputs: skill_id (required), why, confirm, expected. Returns: object
delete_stanzaA
Delete a stanza. Preview unless confirm=true with the preview's expected. Do not call unless the user explicitly asked to delete this stanza. Findings are not a reason to delete.
Inputs: why (required), stanza_id (required), confirm, expected. Returns: object
fetch_packC
Admin: seed library///. No map change. Confirm if refreshing changed bytes.
Inputs: pack (required), version (required), path, repo, +2 more. Returns: object
get_packC
One pack id: versions on disk, members, and which maps pin it.
Inputs: pack (required). Returns: object
get_projectA
Return a project map, notes, roles, and protocol size summary without the protocol body.
Inputs: project (required). Returns: object
get_roleA
Return one role file, member stanza metadata and sizes, and projects that include it.
Inputs: role_id (required). Returns: object
get_skillB
Return one skill: frontmatter, body, size, and payload file list. Optional project looks through that map's pack skills.
Inputs: skill_id (required), project. Returns: object
get_stanzaA
Return one stanza by id (path relative to stanzas/, no .md). Optional project looks through that map's imports.
Inputs: stanza_id (required), project. Returns: object
grantB
Admin only: set a project's operator class to admin or bound.
Inputs: project (required), operator_class (required), working_folder (required). Returns: object
install_capabilityC
This project uses the whole pack at version or latest. Pull onto the shelf if needed.
Inputs: pack (required), project (required), version (required), working_folder (required). Returns: object
install_skillC
This project uses one skill from a pack version. Pull onto the shelf if needed. Does not copy into native skills/.
Inputs: project (required), version (required), skill_id (required), working_folder (required), +1 more. Returns: object
install_stanzaC
This project uses one stanza from a pack version. Pull onto the shelf if needed. target is core or on_demand.
Inputs: project (required), version (required), stanza_id (required), working_folder (required), +2 more. Returns: object
link_skillB
Add a skill to a project's skills list. Writes now. Does not edit role files.
Inputs: project (required), skill_id (required), working_folder (required). Returns: object
link_stanzaA
Add a stanza to a project's core or on-demand list. Does not edit role files.
Inputs: project (required), stanza_id (required), working_folder (required), target. Returns: object
list_on_demandA
List on-demand stanzas associated with a project (id, title, description, size).
Inputs: project (required). Returns: object
list_packsA
Shelf inventory: pack ids, versions, which maps use which, unreferenced versions.
Inputs: no named parameters. Returns: object
list_projectsA
List projects including _global, labels, and composed-protocol size summaries.
Inputs: no named parameters. Returns: object
list_rolesA
List role packs with id, name, description, member counts, and composed core size.
Inputs: no named parameters. Returns: object
list_skillsB
List vault skills with name, description, size, and which projects list them. Not session start.
Inputs: prefix. Returns: object
list_stanzasA
List stanzas with title, description, tags, roles, and size. Optional prefix, tag, or role filter.
Inputs: tag, role, prefix. Returns: object
materializeC
Write PROTOCOL.md and configured host adapters into the working folder.
Inputs: working_folder (required), project. Returns: object
operatorsA
Inspect: operator classes, the registered admins, and the default class.
Inputs: no named parameters. Returns: object
project_statusB
Folder inspect card: map, sourced core ids, size, on-demand ids, disk freshness. No stanza bodies. Inspect only.
Inputs: working_folder (required), project. Returns: object
remove_packA
Admin: preview then confirm. Remove a shelf version (or all versions of an id).
Inputs: pack (required), confirm, version, expected. Returns: object
resolve_protocolC
Return the composed protocol for a project: core bodies, on-demand index, size.
Inputs: project (required). Returns: object
revokeA
Admin only: drop a project back to the default class. Cannot revoke the last admin.
Inputs: project (required), working_folder (required). Returns: object
uninstall_capabilityC
Drop this map's whole-capability record. Shelf unchanged.
Inputs: pack (required), project (required), version (required), working_folder (required). Returns: object
uninstall_skillB
Drop this pack skill from this map's import record. Shelf unchanged.
Inputs: pack (required), project (required), version (required), skill_id (required), +1 more. Returns: object
uninstall_stanzaB
Drop this stanza from this map's import record. Shelf unchanged.
Inputs: pack (required), project (required), version (required), stanza_id (required), +1 more. Returns: object
unlink_skillC
Remove a skill from a project's map. Writes now.
Inputs: project (required), skill_id (required), working_folder (required). Returns: object
unlink_stanzaC
Remove a stanza from a project's map. Does not edit role files.
Inputs: project (required), stanza_id (required), working_folder (required). Returns: object
update_projectB
Incrementally update a project map. Attach/detach role writes immediately and reports members, weight, and affects_projects.
Inputs: project (required), working_folder (required), aka, why, +12 more. Returns: object
update_roleA
Update a role. Name/description write now. Member add/remove is preview unless confirm=true with the preview's expected.
Inputs: role_id (required), why, name, confirm, +6 more. Returns: object
update_skillC
Update SKILL.md frontmatter and/or body. Surfaces where_used and affects_projects.
Inputs: skill_id (required), why, content, description. Returns: object
update_stanzaA
Update a stanza, append a why-log entry, and return where_used. Subject to review policy.
Inputs: why (required), stanza_id (required), tags, roles, +3 more. Returns: object
validateA
Vault health check. Read-only unless fix=true. Issues fail ok; findings do not. Fixes follow the review dial and never consume findings.
Inputs: fix. Returns: object
where_usedA
List every project map and role file that references a stanza.
Inputs: stanza_id (required). Returns: object
where_used_skillB
List project maps that include this skill. Roles never appear.
Inputs: skill_id (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 44 tools
The resource-action pattern makes most tools clearly distinct, but several near-duplicate pairs exist: where_used vs where_used_skill, link_stanza vs install_stanza, link_skill vs install_skill, and get_project vs project_status. The descriptions draw clear lines (native vs pack, stanza vs skill), but an agent must read carefully to avoid misselection.
The core CRUD naming (list/get/create/update/delete + resource) is highly consistent across projects, stanzas, roles, and skills, and the pack install/uninstall family follows a clear pattern. Deviations like grant, revoke, operators, validate, materialize, and the noun-verb project_status break the convention, and where_used_skill is suffixed inconsistently relative to the generic where_used.
At 44 tools, this server is well into the 'too many' range per the calibration, even though each tool appears justified by the breadth of the domain. An agent must navigate a large surface spanning projects, stanzas, roles, skills, packs, admin, and utilities.
Every core resource has full lifecycle coverage — create/get/list/update/delete for projects, stanzas, roles, and skills — plus linking and pack import/export for external content. Minor gaps (no why-log read tool, no findings or review-policy management surface) prevent a 5, but core workflows have no dead ends.
Related MCP Connectors
Hosted MCP server and Agent Skills for specs, engineering threads, and project memory.
The Stytch MCP server is a reference implementation that demonstrates remote MCP server authentication and authorization using Stytch Connected Apps. It provides OAuth 2.1-compliant authorization (including PKCE), Dynamic Client Registration, and validates Stytch-issued access tokens to enable AI agents to securely interact with external services through permissioned access, supporting scopes like openid, email, profile, and manage:project_data.
MCP Server for an Agent Task Marketplace
A MCP server built for developers enabling Git based project management with project and personal…
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP Server for AI agent identity and authorization. Create, verify, and manage agent identities with trust scores and scoped authorization tokens.48 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceA storage-backed MCP server for sharing durable project context between trusted coding agents, with project discovery, optimistic concurrency, and timestamped handoffs.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server that gives AI agents a durable identity, persistent browser, memory, and coordination tools, enabling them to maintain state across sessions and act on the live web.3MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for universal multi-agent communication, enabling agents to register, send/receive messages, manage tasks, and coordinate via role-based routing with project isolation.6 npmISC