🎯

conport-memory

🎯Skill

from nicobailon/conport-mcporter-skills

What it does

Persistently loads, tracks, and updates project context across Claude Code sessions to combat AI memory loss.

📦

Part of

nicobailon/conport-mcporter-skills(2 items)

conport-memory

Installation

npxRun with npx

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" conport.get_product_context

pip installInstall Python package

pip install uvx

npxRun with npx

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" \

Claude Desktop ConfigurationAdd this to your claude_desktop_config.json

{
  "mcpServers": {
    "conport": {
      "command": "uvx",
      "args": ["--f...

📖 Extracted from docs: nicobailon/conport-mcporter-skills

Need more details? View full documentation on GitHub →

2Installs

AddedFeb 4, 2026

View on GitHub Back to Skills

Skill Details

SKILL.md

Access Context Portal (ConPort) as persistent project memory via MCPorter. Load/update project context, log decisions and progress, track patterns. Use PROACTIVELY at session start to load context and throughout work to log decisions. Combats AI amnesia across sessions.

Overview

ConPort is your project's memory bank - a SQLite-backed knowledge base that

persists decisions, progress, patterns, and context across Claude Code sessions.

Access via MCPorter CLI without MCP installation.

Load product_context and active_context

Log decision with rationale and tags

Update progress with status

Log system_pattern for reuse

Update active_context with current state

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" conport.TOOL_NAME

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" \

conport.get_product_context

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" \

conport.update_product_context content:"Project overview text..."

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" \

conport.get_active_context

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" \

conport.update_active_context content:"Currently working on..."

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" \

conport.log_decision \

summary:"Decision title" \

rationale:"Why this was decided" \

details:"Full decision details" \

tags:'["architecture", "database"]'

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" \

conport.get_decisions tags:'["architecture"]'

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" \

conport.search_decisions_fts query:"authentication"

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" \

conport.log_progress \

status:"in_progress" \

description:"Implementing user authentication"

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" \

conport.get_progress status:"in_progress"

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" \

conport.log_system_pattern \

name:"Repository Pattern" \

description:"Data access abstraction" \

tags:'["architecture", "data-layer"]'

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" \

conport.get_system_patterns

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" \

conport.log_custom_data \

category:"glossary" \

key:"MFA" \

value:'{"definition": "Multi-Factor Authentication", "context": "Security feature"}'

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" \

conport.export_conport_to_markdown output_dir:"./context-export"

1. Check if context_portal/context.db exists

2. If exists:

- get_product_context - understand project goals

- get_active_context - resume from last session

- get_progress status:"in_progress" - see pending tasks

- get_decisions - review recent architectural decisions

3. If not exists: prompt user to run /conport-init

- log_decision - when making architectural choices

- log_progress - when completing tasks

- log_system_pattern - when discovering reusable patterns

- log_custom_data - for project-specific context

1. update_active_context - record current state and next steps

2. log_progress - mark completed items

Link related items to build explicit relationships:

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" \

conport.link_conport_items \

source_type:"decision" source_id:"dec-123" \

target_type:"progress" target_id:"prog-456" \

relationship:"implements"

Retrieve linked items:

npx mcporter call --stdio "uvx --from context-portal-mcp conport-mcp --mode stdio" \

conport.get_linked_items item_type:"decision" item_id:"dec-123"

Product/Active Context:

- get_product_context, update_product_context

- get_active_context, update_active_context

Decisions:

- log_decision, get_decisions, search_decisions_fts, delete_decision_by_id

Progress:

- log_progress, get_progress, update_progress, delete_progress_by_id

Patterns:

- log_system_pattern, get_system_patterns, delete_system_pattern_by_id

Custom Data:

- log_custom_data, get_custom_data, delete_custom_data

- search_project_glossary_fts, search_custom_data_value_fts

Knowledge Graph:

- link_conport_items, get_linked_items

Utility:

- get_item_history, get_recent_activity_summary

- export_conport_to_markdown, import_markdown_to_conport

- batch_log_items, get_conport_schema

More from this repository1

🎯

mcporter🎯Skill

Enables instant CLI access to MCP servers via npx, auto-discovering and calling tools without direct installation.