com.mcparmory/pinecone vs pgvector
com.mcparmory/pinecone is an MCP server published by mcparmory.com. Marketplaces we read that list it: 1 (Official MCP Registry). pgvector is an MCP server published by mittalpk. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
| Marketplace |  com.mcparmory/pinecone |  pgvector |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Downloads/month (PyPI): 823 Downloads/week (PyPI): 175 Forks (GitHub): 4 Stars (GitHub): 32 Not marked · First seen |
Listed Version: 0.1.0 Downloads/month (PyPI): 67 Downloads/week (PyPI): 23 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
| Fact | com.mcparmory/pinecone | pgvector |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 32 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 4 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcparmory-pinecone) | On your machine (mcp-server-pgvector) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mcparmory/registry | github.com/mittalpk/mcp-server-pgvector |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
com.mcparmory/pinecone
Create and manage vector database indexes, backups, and collections
pgvector
Similarity search, hybrid search, and index management for pgvector-backed PostgreSQL tables
How to run each
com.mcparmory/pinecone As a local MCP server: PyPI package
claude mcp add --transport stdio pinecone -- uvx mcparmory-pineconepgvector As a local MCP server: PyPI package
claude mcp add --env "DATABASE_URL=<YOUR_DATABASE_URL>" --transport stdio pgvector -- uvx mcp-server-pgvectorRequires: DATABASE_URL (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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 com.mcparmory/pinecone publish no settings it asks for, so we do not compare settings.
What it can do: com.mcparmory/pinecone · What it can do: pgvector · 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.