Contextforge MCP

Activate or deactivate a connected repository webhook after setup

List commits stored in memory from connected repositories

Connect a GitHub repository to automatically sync commits and PRs to memory

Disconnect a GitHub repository and stop syncing

List all connected GitHub repositories

List pull requests stored in memory from connected repositories

Sync existing commits and PRs from a connected GitHub repository into memory

Show help and usage instructions for ContextForge memory commands

Import items from JSON, Markdown, Notion, or Obsidian format into a space

**Save important context to persistent memory — be proactive.** Call this WHENEVER you learn information that would be valuable in a future conversation: project decisions ('we chose Postgres because X'), architectural choices, user preferences, debugging insights, recurring patterns, deadlines, stakeholder context, or any 'remember this' / 'save this' / 'note that' style request from the user. Heuristic: if you would be sad to lose this fact when the conversation ends, ingest it. Better to over-save than to under-save — the memory_query semantic search will surface what's relevant later. Alwa…

Add multiple items to memory in a single operation. More efficient than multiple single ingests.

Link the current directory to a ContextForge project. When linked, all queries will be automatically filtered to only search within that project's spaces. This creates a .contextforge file in the current directory.

List all items stored in memory. Shows titles, previews, tags, and creation dates.

List all projects. Projects contain multiple spaces for organizing knowledge by project.

List all relationships for a knowledge item, showing both incoming and outgoing connections with related item details

List knowledge spaces (workspaces). By default shows only knowledge spaces. Use space_type "git" for GitHub repos, or "all" to see everything.

Move a knowledge item to a different space (organizes memory by topic). Identify the item by id or a title substring, and give the target space by name or UUID. Cross-project moves within your org are allowed.

Move a space to a different project

**Search persistent memory BEFORE answering any project-specific question.** You MUST call this tool: (a) at the start of any conversation that touches the user's codebase, work, or decisions, BEFORE generating any response; (b) whenever the user references prior context ('did we', 'we decided', 'remember', 'what did I save', 'last time'); (c) before making architectural or design recommendations — the user's prior decisions live here. Returns semantically relevant stored content. Skipping this when relevant context exists makes you appear to have amnesia and is the #1 reason users abandon per…

Create a relationship between two knowledge items

Create a snapshot (backup) of the current memory state

Delete a snapshot

List all available snapshots

Restore memory to a previous snapshot state

Get statistics about memory usage

Remove the project link from the current directory. This deletes the .contextforge file and queries will no longer be filtered by project.

Edit any saved memory's content (and optionally its title) by id — for general corrections, not tied to a freshness check. Regenerates the item's embedding so semantic search reflects the new content. Get the id from memory_query or memory_list_items. (For a memory flagged by memory_check_freshness after related code changed, use memory_correct instead.)

Share a project with a collaborator by email. Creates an invitation and returns the invite URL. An email notification may also be sent.

Create a new Routine. Schedules a Skill to run on a cron expression. Pass either schedule_preset (hourly/daily/weekly/monthly) OR a custom cron_expression. timezone defaults to UTC.

Permanently delete a Routine. Execution history rows are retained.

Get a single Routine by ID, including its cron expression, input_params, and last/next run.

List all Routines in a project. Returns routines with their schedule, last/next run, and enabled flag.

Fire a Routine immediately, ahead of its schedule. Creates a skill_executions row with trigger_type=scheduled and routine_id set, just like the cron tick would.

Enable or disable a Routine without deleting it. Pass enabled=false to pause.

Update an existing Routine (name, schedule, timezone, input_params).

End THIS session's live presence explicitly (it also ends automatically when the process exits or after the heartbeat TTL).

List OTHER live Claude Code sessions working on the same project right now, and what each is focused on. By default it is scoped to THIS session's project (the one linked in the current directory) — that's where work actually collides. If the current directory isn't linked to a project, it falls back to the whole organization. Use it at conversation start and before big changes to avoid stepping on parallel sessions. Pass a specific `project` to scope elsewhere, or `all_projects: true` to see every session across the organization. Sessions expire automatically ~10 minutes after their last hear…

Declare or update what THIS Claude Code session is currently working on (live presence). Call it when you start or switch tasks so parallel sessions can avoid stepping on your work. Example focus: 'working on the auth module'.

Create a new Skill in a project. The 'body' is a markdown prompt template that may use {{variable}} placeholders for input_params at run time.

Delete a Skill.

Get a single Skill by ID with full body.

List all Skills in a project. Returns skills with their name, description, model, and prompt body.

Execute a Skill on the configured LLM, optionally storing the output as a knowledge_item, and returns the result. Available to all project members.

Update an existing Skill.

Add a comment to a task. Accepts any task identifier: UUID, short_id, or task title. The response includes the task dashboard URL — always show it to the user.

Assign a task to a collaborator by their email address. Accepts any task identifier: UUID, short_id, or task title. The response includes a dashboard URL — always show it to the user.

Create a new task in a project. Optionally assign it to a collaborator by their email. The response includes a dashboard URL — always show it to the user.

Permanently delete a task. Accepts any identifier: UUID, short_id, or task title. Also deletes related comments, activity, and notifications.

**Call this at the start of any conversation about work, planning, or status — and any time the user asks about pending/open/in-progress tasks.** Shows pending tasks by default (sort by due date, urgent first). Use status "all" for everything, "resolved" for completed, "in_progress" for active work. IMPORTANT: Every task includes a dashboard URL (🔗). You MUST include these clickable links when presenting tasks to the user. If you see overdue tasks (past due date), surface them at the top of your response.

List comments on a task. Accepts any identifier: UUID, short_id, or task title.

Mark a task as "resolved". Use this when you finish working on a task. Accepts any identifier: UUID, short_id, or task title. The response includes a dashboard URL — always show it to the user.

Resolve a task by searching for it by title, short_id, or UUID. Use this when you have any identifier for the task. The response includes a dashboard URL — always show it to the user.

Mark a task as "in_progress". Use this when you start working on a task. Accepts any identifier: UUID, short_id, or task title. The response includes a dashboard URL — always show it to the user.

Update a task's title, description, status, priority, tags, due date, or assignee. Accepts any identifier: UUID, short_id, or task title. The response includes a dashboard URL — always show it to the user.

**Call this whenever the user asks what they should work on, what's next, what's pending, or how to start the day.** Trigger phrases include: 'what should I do', 'where do I start', 'qué hago hoy', 'next task', 'I have time, what's open'. Returns the highest-priority unresolved task assigned to the user, with due date and priority. Always include the dashboard URL (🔗) in your reply so the user can click through. Prefer this over generic answers when the user seems unsure about priorities — it gives a concrete next action.