Skip to main content

Pinecone API MCP server

Workflow preview

Workflow preview
100%
Pinecone API MCP server preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator? [Join the community](https://www.skool.com/beyond nodes automation lab 2006/a...

Best for

  • Engineering automation workflows
  • AI RAG automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, @n8n/n8n-nodes-langchain.mcptrigger, n8n-nodes-base.httprequesttool

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by David Ashby.

Original n8n.io source

1.1 Workflow description

Title
Pinecone API MCP server
Workflow name
Pinecone API MCP server

Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator?

Join the community

Complete MCP server exposing 15 Pinecone API operations to AI agents.

⚡ Quick Setup

  1. Import this workflow into your n8n instance
  2. Credentials Add Pinecone API credentials
  3. Activate the workflow to start your MCP server
  4. Copy the webhook URL from the MCP trigger node
  5. Connect AI agents using the MCP URL

🔧 How it Works

This workflow converts the Pinecone API into an MCP-compatible interface for AI agents.

MCP Trigger: Serves as your server endpoint for AI agent requests • HTTP Request Nodes: Handle API calls to https://controller.{environment}.pinecone.ioAI Expressions: Automatically populate parameters via $fromAI() placeholders • Native Integration: Returns responses directly to the AI agent

📋 Available Operations (15 total)

🔧 Collections (4 endpoints)

GET /collections: Describe Collection • POST /collections: Create collection • DELETE /collections/{collectionName}: Delete Collection • GET /collections/{collectionName}: Describe collection

🔧 Describe_Index_Stats (1 endpoints)

POST /describe_index_stats: Retrieve Index Stats

🔧 Indexes (5 endpoints)

GET /indexes: Configure Index • POST /indexes: Create index • DELETE /indexes/{indexName}: Delete Index • GET /indexes/{indexName}: Describe index • PATCH /indexes/{indexName}: Configure index

🔧 Query (1 endpoints)

POST /query: Execute Query

🔧 Vectors (4 endpoints)

POST /vectors/delete: Delete Vectors • POST /vectors/fetch: Fetch Vectors • POST /vectors/update: Update Vectors • POST /vectors/upsert: Upsert Vectors

🤖 AI Integration

Parameter Handling: AI agents automatically provide values for: • Path parameters and identifiers • Query parameters and filters • Request body data • Headers and authentication

Response Format: Native Pinecone API responses with full data structure

Error Handling: Built-in n8n HTTP request error management

💡 Usage Examples

Connect this MCP server to any AI agent or workflow:

Claude Desktop: Add MCP server URL to configuration • Cursor: Add MCP server SSE URL to configuration • Custom AI Apps: Use MCP URL as tool endpoint • API Integration: Direct HTTP calls to MCP endpoints

✨ Benefits

Zero Setup: No parameter mapping or configuration needed • AI-Ready: Built-in $fromAI() expressions for all parameters • Production Ready: Native n8n HTTP request handling and logging • Extensible: Easily modify or add custom logic

> 🆓 Free for community use! Ready to deploy in under 2 minutes.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Setup Instructions

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Workflow Overview

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Pinecone MCP Server

Type / Role
@n8n/n8n-nodes-langchain.mcpTrigger - mcpTrigger
Config choices
Version 1

Block 4 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 5 - List Collections

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 6 - Create Collection 1

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 7 - Delete Collection 1

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 8 - Describe Collection

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 9 - List Indexes

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 10 - Create Index

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 11 - Delete Index

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 12 - Describe Index

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 13 - Configure Index

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 14 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 15 - Retrieve Index Stats

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 16 - Execute Query

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 17 - Delete Vectors

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 18 - Fetch Vectors

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 19 - Update Vectors

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 20 - Upsert Vectors

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

3. Summary Table

Workflow Pinecone API MCP server
Complexity advanced
Nodes 20
Categories Engineering, AI RAG
Author David Ashby
Published 03 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/5642/5642.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Pinecone API MCP server do?

Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator? [Join the community](https://www.skool.com/beyond nodes automation lab 2006/a...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Engineering, AI RAG use case.