Heyo, I simply wanted to show you guys the directory-mcp I built. Here’s the GitHub repo: https://github.com/ePaint/directory-mcp In my company, we’ve been suggested more and more to connect MCPs to our Claude instances to speed up communication, which has been great, but I’ve noticed a common pattern that got really tedious really quickly for me: I had to explain to Claude each time what each project was, who was working on it, and why it mattered. directory-mcp is simply a graph of people and projects; each node can hold link information like (but not limited to) their Slack ID, Outlook email, or Jira account ID, making other MCP calls much more direct. If you add enough process information to it, you can even just tell it “check [project_name] news” and it will know which identities to query across your other MCPs. There’s even a recency-bias algorithm in case project names repeat or are very similar. There are a few skills added, like /directory-enroll for adding new people and /directory-graph to get an HTML view of your graph nodes. This is 100% local on a single SQLite DB, and no external connections ever happen. It’s around 3k lines of code, so it fits in any model’s context for quick analysis. You can find more details in the repo. Have a nice day! submitted by /u/ePaint
Originally posted by u/ePaint on r/ClaudeCode