Pinecone logo

Pinecone

Community
AlexAI-MCP
pinecone

Managed vector database for production RAG — serverless and pod-based deployment, hybrid search, namespaces, and metadata filtering.

Overview

PublisherAlexAI-MCP
Repositoryhermes-CCC
Skill namepinecone
Stars
134
Forks
22
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by AlexAI-MCP on GitHub. Read the source before you install it.

Installation

Install the Pinecone AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/AlexAI-MCP/hermes-CCC/tree/master/skills/pinecone
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/AlexAI-MCP/hermes-CCC.git /tmp/hermes-CCC
mkdir -p .claude/skills
cp -r /tmp/hermes-CCC/skills/pinecone .claude/skills/pinecone
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Pinecone in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Pinecone on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Pinecone is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Pinecone — Managed Vector Database

Fully managed vector database for production RAG. Serverless (pay-per-query) or pod-based (dedicated).

Setup

bash
pip install pinecone-client sentence-transformers openai
python
from pinecone import Pinecone, ServerlessSpec

pc = Pinecone(api_key="your-api-key")  # or os.environ["PINECONE_API_KEY"]

Create Index

python
# Serverless (pay-per-query — cheapest to start)
pc.create_index(
    name="my-index",
    dimension=1536,          # match your embedding model
    metric="cosine",         # cosine | euclidean | dotproduct
    spec=ServerlessSpec(
        cloud="aws",
        region="us-east-1"
    )
)

# Connect to index
index = pc.Index("my-index")

Upsert Vectors

python
from sentence_transformers import SentenceTransformer

model = SentenceTransformer("all-MiniLM-L6-v2")  # dim=384

documents = [
    {"id": "doc1", "text": "Python async programming guide"},
    {"id": "doc2", "text": "Machine learning with PyTorch"},
]

vectors = []
for doc in documents:
    embedding = model.encode(doc["text"]).tolist()
    vectors.append({
        "id": doc["id"],
        "values": embedding,
        "metadata": {"text": doc["text"], "source": "manual"}
    })

# Batch upsert (max 100 per call)
index.upsert(vectors=vectors, namespace="docs")

Query

python
query_text = "how to write async Python?"
query_vector = model.encode(query_text).tolist()

results = index.query(
    vector=query_vector,
    top_k=5,
    namespace="docs",
    include_metadata=True,
)

for match in results["matches"]:
    print(f"Score: {match['score']:.3f} | {match['metadata']['text']}")

Metadata Filtering

python
results = index.query(
    vector=query_vector,
    top_k=5,
    filter={"source": {"$eq": "manual"}},
    include_metadata=True,
)

# Operators: $eq, $ne, $gt, $gte, $lt, $lte, $in, $nin, $and, $or
results = index.query(
    vector=query_vector,
    top_k=5,
    filter={
        "$and": [
            {"category": {"$in": ["tech", "science"]}},
            {"year": {"$gte": 2023}},
        ]
    },
    include_metadata=True,
)

Namespaces

python
# Different namespaces = separate vector spaces (free, no extra cost)
index.upsert(vectors=vectors, namespace="user-123")
index.upsert(vectors=vectors, namespace="user-456")

# Query specific namespace
results = index.query(vector=query_vector, top_k=5, namespace="user-123")

# Delete namespace
index.delete(delete_all=True, namespace="user-123")

Fetch / Delete / Update

python
# Fetch specific vectors
fetched = index.fetch(ids=["doc1", "doc2"], namespace="docs")

# Delete vectors
index.delete(ids=["doc1"], namespace="docs")

# Update metadata (re-upsert with same id)
index.upsert(vectors=[{"id": "doc1", "values": embedding, "metadata": {"updated": True}}])

Index Stats

python
stats = index.describe_index_stats()
print(f"Total vectors: {stats['total_vector_count']}")
print(f"Namespaces: {stats['namespaces']}")

When to Use Pinecone vs Alternatives

PineconeQdrantChroma
HostingManaged cloudSelf/cloudSelf/cloud
CostPay-per-useSelf-hosted freeFree
ScaleBillionsMillions+Millions
SetupMinutesMinutesSeconds
Best forProduction SaaSProduction self-hostedLocal dev/RAG

Frequently asked questions

What does the Pinecone AI skill do?

Managed vector database for production RAG — serverless and pod-based deployment, hybrid search, namespaces, and metadata filtering.

Why use Pinecone on TypingMind?

Because you install it once and use it with any model. Pinecone is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Pinecone in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/AlexAI-MCP/hermes-CCC/tree/master/skills/pinecone. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Pinecone?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Pinecone?

As many as you like. As long as a model supports skills, you can use Pinecone with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Pinecone AI skill free?

Yes. It is published on GitHub by AlexAI-MCP under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇