Advertise
MCP.so
Sign In

Afterpaths MCP Server

@burnssa

Repository

Basic information

Category

Developer Tools

Transports

stdio

Author

burnssa

Submitted by

Scott

About Afterpaths MCP Server

Make your AI coding agents smarter with every session

Afterpaths MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "afterpaths": {
      "command": "uvx",
      "args": [
        "--from",
        "afterpaths[mcp]",
        "afterpaths-mcp"
      ]
    }
  }
}

Afterpaths MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is Afterpaths?

Afterpaths captures sessions across AI coding tools (Claude Code, Cursor, Codex CLI), summarizes them, and automatically extracts rules—so your agents learn from every session and you retain rich context. It includes a Model Context Protocol (MCP) server that exposes session history, summaries, and rules as native tools for AI assistants.

How to use Afterpaths?

Install with pip install afterpaths (or pip install afterpaths[mcp] for MCP support). Navigate to your project and run ap audit to see an overview. Recommended flow: ap log to browse sessions, ap summarize <ref> (requires ANTHROPIC_API_KEY), ap rules to extract rules into .claude/rules/, ap search <query> to find past discussions, and ap stats to track performance. For the MCP server, configure it with claude mcp add afterpaths -- afterpaths-mcp or run python -m afterpaths.mcp_server. Both afterpaths and ap work identically.

Key features of Afterpaths

  • Unified session view across all AI coding tools
  • LLM-generated session summaries (discoveries, dead ends, decisions)
  • Automatic rule extraction into .claude/rules/ and .cursor/rules/
  • Cross-session search (ap search) with optional deep search
  • Session analytics: tokens, errors, daily trends
  • MCP server with 6 native tools (list, show, search, summarize, artifacts, rules)

Use cases of Afterpaths

  • Compare model performance across tools to pick the best model for your stack
  • Capture and reuse discoveries as rules to prevent repeated mistakes
  • Search past sessions for context when resuming work after days or weeks
  • Track ongoing session metrics to identify expensive or ineffective approaches
  • Retain session history that would otherwise be auto-deleted after 30 days

Frequently asked questions

1

What does Afterpaths do that my IDE doesn't?

Afterpaths gives a single view across Claude Code, Cursor, and Codex CLI—something no single IDE provides. It automatically extracts rules from sessions and surfaces comparative model performance.

2

What dependencies or API keys are required?

Audit, log, and search commands work without any API key. Summarization requires an `ANTHROPIC_API_KEY`. The MCP server uses local files only.

3

Where do summaries and rules live?

Summaries are stored in `.afterpaths/` (gitignored). Rules are written to `.claude/rules/` and `.cursor/rules/` (these should be committed). Everything stays in your project; no data leaves your machine except when sending session text to the LLM for summarization.

4

Does Afterpaths support all Cursor sessions?

Cursor support is partial—the adapter reads several known formats from `state.vscdb`, but Cursor changes its storage schema often. Some sessions may show `Entries: 0`. In that case, `ap show <ref> --raw` emits a warning; you can still access the raw file directly with `sqlite3`. Tool provenance features only cover sessions whose entries the adapter can read.

5

How are manually written rules preserved?

Each rule file has `<!-- afterpaths:manual:start -->` and `<!-- afterpaths:manual:end -->` markers. Content between those markers survives every `ap rules` run. Auto-generated content is regenerated. Content outside markers (other than boilerplate) blocks the run unless `--force` is used.

Comments

More Developer Tools MCP servers

Cronwatch

cronwatchdev

CronWatch records every run of your scheduled jobs in your own database, and speaks up when one is missed, fails, gets stuck, runs slow or costs too much. CronWatch is free and open-source.

31

Agent Trust (mnki-mcp)

MNKIAgentOS

Agent Trust — open profile + reference implementation for proving what an autonomous AI agent is authorized to do: identity, delegation with attenuation, proof-of-possession, attestations, tamper-evident provenance. Buil

ArtiBot Cloud MCP - Zhijiangyun 智匠云

bofob

ArtiBot Cloud MCP (Zhijiangyun 智匠云) — cloud MCP server for robot manipulation data & GPU workloads. 15 tools: robot fleet management, data collection & video recording, post-processing pipelines, and benchmark evaluation

1

FARPY

mangomunchr

Verified distributed compute for humans, applications, and agents. Submit Blender, Octane, and video workloads, route them across qualified GPUs, track asynchronous execution, download finished artifacts, and verify FARP

1

LastPing

LastPing

Know when your AI agents, cron jobs and CI pipelines fail, stall or go quiet. Your agent sets up monitors from a plain description, tells you what is broken and why, reads run history and traces, and writes notes on inci

Advertise