Ext Ops Panel
Open dashboard
Comparison

Base de Conhecimento vs ContextPull

Base de Conhecimento is an MCP server published by mcp-dir. Marketplaces we read that list it: 1 (Official MCP Registry). ContextPull is an MCP server published by mi2arun. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplaceBase de ConhecimentoContextPull
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.2.1
Downloads/month (PyPI): 352
Downloads/week (PyPI): 20
Forks (GitHub): 0
Stars (GitHub): 0
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

Base de Conhecimento vs ContextPull
FactBase de ConhecimentoContextPull
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.mcp.ai/p_kb)On your machine (contextpull)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/mcp-dir/kb-mcpgithub.com/mi2arun/contextpull
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 39 h 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

Base de Conhecimento

In its own words, on Official MCP Registry:

Your private knowledge base: upload documents (.md, .txt, .docx, PDF, images), the platform indexes

ContextPull

In its own words, on Official MCP Registry:

Exact document sections on demand for LLM agents: index in context, search, read, grep, neighbours.

How to run each

Base de Conhecimento As a remote MCP server

Claude Code
claude mcp add --transport http kb-mcp https://api.mcp.ai/p_kb

ContextPull As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio contextpull -- uvx --from "contextpull[mcp]" contextpull serve "<YOUR_CORPUS_OR_STORE>"

Requires: <corpus_or_store>

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

Only Base de Conhecimento 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

Neither one's marketplaces publish the settings it asks for.

What it can do: Base de Conhecimento · What it can do: ContextPull · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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