Ext Ops Panel
Open dashboard
Comparison

PDS Project AI MPP Connector vs LoreDocs

PDS Project AI MPP Connector is an MCP server published by projectdata.ai. Marketplaces we read that list it: 1 (Official MCP Registry). LoreDocs is an MCP server published by labyrinth-analytics. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-23. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacePDS Project AI MPP ConnectorLoreDocs
Official MCP Registry Listed
Version: 0.1.0
No figure published
Not marked · First seen
Listed
Version: 0.1.28
Downloads/month (PyPI): 581
Downloads/week (PyPI): 163
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.1.19
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

PDS Project AI MPP Connector vs LoreDocs
FactPDS Project AI MPP ConnectorLoreDocs
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub4
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.projectdata.ai)On your machine (loredocs)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)Not a bundle3
Licence (differs)Not statedBSL-1.1
Repository (differs)github.com/projectdata-io/mpp-poweautomate-connectorgithub.com/labyrinth-analytics/loredocs
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 2 days agono remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

PDS Project AI MPP Connector

In its own words, on Official MCP Registry:

Read, analyze, and safely edit Microsoft Project MPP files.

LoreDocs

In its own words, on Official MCP Registry:

Local-first knowledge vaults for project docs and specs. Tagged, versioned, full-text searchable.

How to run each

PDS Project AI MPP Connector As a remote MCP server

Claude Code
claude mcp add --transport http mpp-connector https://mcp.projectdata.ai/

LoreDocs As a local MCP server: PyPI package

Claude Code
claude mcp add --env "LOREDOCS_PRO=<YOUR_LOREDOCS_PRO>" --transport stdio loredocs -- uvx loredocs

Requires: LOREDOCS_PRO (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only PDS Project AI MPP Connector has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of PDS Project AI MPP Connector publish no settings it asks for, so we do not compare settings.

What it can do: PDS Project AI MPP Connector · What it can do: LoreDocs · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built