Follow these steps to run the MCP Pinecone tool and chatbot inside a Meshagent Room in the cloud for quick testing. When the room closes (e.g., due to inactivity), the MCP server and chatbot are removed automatically.
PINECONE_ASSISTANT_HOST
: Your Pinecone Assistant host.PINECONE_API_KEY
: Your Pinecone API key.Install Meshagent:
Sign Up & Authenticate: Follow the Meshagent CLI getting started guide.
Start Pinecone MCP Service in a Room:
This command will start a Meshagent Room named “test”, running the Pinecone MCP server. The room and its services will close if inactive.
Join a Chatbot with the Toolkit in the Room:
Test the Integration:
To make the MCP server tools and a chatbot persistently available in every room of a Meshagent project (ideal for production), deploy as project-level services:
Create Persistent MCP Pinecone Service:
Create Persistent Chatbot Service with Toolkit:
These services will join every new room created within your Meshagent project, so your tools and chatbot are always available—no need to run them manually!
assistant_context
Retrieves relevant document snippets from your Pinecone Assistant knowledge base.
Short Description:
assistant_context
| Retrieves relevant document snippets from your Pinecone Assistant knowledge base.
assistant_context
Retrieves relevant document snippets from your Pinecone Assistant knowledge base.
Returns an array of text snippets from the most relevant documents.
assistant_name
(string
): Name of an existing Pinecone assistantquery
(string
): The query to retrieve context for.top_k
(integer
, optional): Number of context snippets to retrieve. Defaults to 15. Recommended: 5-8 for simple/narrow queries, 10-20 for complex/broad topics.For more details about MCP servers and Pinecone’s Assistant integration, see Pinecone Assistant MCP Server Repository and this Docker image.
Follow these steps to run the MCP Pinecone tool and chatbot inside a Meshagent Room in the cloud for quick testing. When the room closes (e.g., due to inactivity), the MCP server and chatbot are removed automatically.
PINECONE_ASSISTANT_HOST
: Your Pinecone Assistant host.PINECONE_API_KEY
: Your Pinecone API key.Install Meshagent:
Sign Up & Authenticate: Follow the Meshagent CLI getting started guide.
Start Pinecone MCP Service in a Room:
This command will start a Meshagent Room named “test”, running the Pinecone MCP server. The room and its services will close if inactive.
Join a Chatbot with the Toolkit in the Room:
Test the Integration:
To make the MCP server tools and a chatbot persistently available in every room of a Meshagent project (ideal for production), deploy as project-level services:
Create Persistent MCP Pinecone Service:
Create Persistent Chatbot Service with Toolkit:
These services will join every new room created within your Meshagent project, so your tools and chatbot are always available—no need to run them manually!
assistant_context
Retrieves relevant document snippets from your Pinecone Assistant knowledge base.
Short Description:
assistant_context
| Retrieves relevant document snippets from your Pinecone Assistant knowledge base.
assistant_context
Retrieves relevant document snippets from your Pinecone Assistant knowledge base.
Returns an array of text snippets from the most relevant documents.
assistant_name
(string
): Name of an existing Pinecone assistantquery
(string
): The query to retrieve context for.top_k
(integer
, optional): Number of context snippets to retrieve. Defaults to 15. Recommended: 5-8 for simple/narrow queries, 10-20 for complex/broad topics.For more details about MCP servers and Pinecone’s Assistant integration, see Pinecone Assistant MCP Server Repository and this Docker image.