cic-mcp-session
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@cic-mcp-sessionsearch session for 'deploy' status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
cic-mcp-session
Session-scope esemény-/idővonal-/chunk-tár és provenance réteg a CIC agent-kontextus (cic-mcp-* család) számára.
A cic-mcp-* család trust-domain rétegezésében ez a komponens egyetlen beszélgetés/session
kontextusát tárolja és szolgálja ki — nem canonical tudás, nem cross-session memória.
Mi ez és mi nem
Igen:
SessionIngressEnvelopeingestraw event store
turn/timeline projection
chunk store
source/provenance refs
metadata index, full-text search, vector search
session-scope context pack
stabil SQL/API/MCP read tools
Nem:
canonical tudás
shared memory
cross-session graph
végleges döntésbányászat
human review nélküli promotion
A komponensek közti pontos határt lásd: CLAUDE.md.
Related MCP server: MCP Context Server
Státusz
experimental — a repo a cic-mcp-factory job-lifecycle-én keresztül épül fel, kapacitás-jobonként.
A teljes session-specifikus adatfolyam (ingress envelope, Postgres write-path, projection,
chunk/embedding indexelés, FTS/vektor/hibrid retrieval, MCP read tool-ok) MÁR megépült és valódi
Postgres ellen bizonyítva van (~17 capability-job, lásd output/session-*-report.md):
SessionIngressEnvelopewrite-path:session_store/envelope_writer.py:165(insert_envelope) —output/session-raw-event-store-report.mdvalódi hook-producer:
hooks/log-event.py:303-304(insert_envelope()-et hív) —output/session-hook-collector-report.mdraw event store:
session_raw.envelopes(output/session-postgres-schema.sql) — ugyanaz a riportworker loop (turn projection + chunk indexelés, ütemezve):
session_store/turn_projector.py:300(run_projection_batch),session_store/chunk_indexer.py:378(run_indexing_batch),session_store/worker_loop.py:65,93(run_one_iteration/run_loop) —output/session-turn-projector-report.md,output/session-chunk-indexer-report.md,output/session-worker-scheduler-report.mdFTS / vektor / hibrid keresés:
session_api.search_context(),search_context_vector(),search_context_hybrid()(output/session-retrieval-quality-migration.sql,output/session-vector-search-api-migration.sql,output/session-hybrid-search-api-migration.sql) —output/session-vector-search-api-report.md,output/session-hybrid-search-api-report.mdsession_apiréteg (timeline, context pack, status, source refs):output/session-postgres-schema.sql+output/session-source-refs-api-migration.sql—output/session-source-refs-api-report.md7 tool-os MCP szerver:
mcp-server/session_server.py(search_session_context+search_session_context_fts/search_session_context_vector/get_session_timeline/get_session_context_pack/get_session_status/get_session_source_refs) —output/session-mcp-tools-report.md,output/session-mcp-tools-remaining-report.mdhost-natív MCP indítás (
.venv-host, nem a Docker-builderp_venv):.mcp.json.tpl—output/session-mcp-venv-fix-report.md
A dokumentált korlátok: a fenti komponensek production reachability-je jelenleg scaffold
szintű — a write-path-ot és a worker-loop-ot semmilyen permanens, deployolt infrastruktúra
(cron/systemd timer) nem hívja élesben (lásd output/session-worker-scheduler-report.md
"Risks"), és a cic-session MCP szerver nincs bekötve semelyik éles orchestrátor/Claude Code
session .mcp.json-jába (lásd output/session-mcp-config-wiring-report.md). A
status: experimental ezt a reachability-rést jelzi, NEM a session-specifikus implementáció
hiányát.
Kapcsolódó dokumentáció
cic-mcp-factoryfactory-docs — a komponens tervezési alapja (architecture.md,acceptance-contract.md,execution-phases.md)cic-mcp-knowledge— a canonical réteg, amire ez a komponens sosem promote-ol automatikusan
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityCmaintenanceProvides persistent session memory for AI assistants, enabling them to store, search, and retrieve conversation summaries across sessions via the Model Context Protocol.Last updated10MIT
- Alicense-qualityAmaintenanceEnables persistent multimodal context storage for LLM agents with thread-based scoping, metadata filtering, and hybrid search capabilities.Last updated9Elastic 2.0
- AlicenseAqualityBmaintenanceA session-scoped memory layer for LLMs that enables AI assistants to explicitly store and retrieve notes, decisions, and context within a single conversation, ensuring focus without cross-session data contamination.Last updated6115MIT
- Alicense-qualityCmaintenanceProvides session persistence, crash recovery, decision tracking, and context compression for AI assistants, enabling seamless multi-session continuity.Last updatedMIT
Related MCP Connectors
Individual-analyst context layer: recall, remember, and reconcile your data and engineering context.
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
Shared, permission-aware company context for AI agents, with provenance, approvals and audit.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/CentralInfraCore/cic-mcp-session'
If you have feedback or need assistance with the MCP directory API, please join our Discord server