Back to MCP Directory
Connections & Capabilities
Connects To
Docker
Capabilities
read
Quickstart
Install
npx @modelcontextprotocol/inspectorConfig
{
"mcpServers": {
"pinecone-assistant": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PINECONE_API_KEY",
"-e",
"PINECONE_ASSISTANT_HOST",
"pinecone/assistant-mcp"
],
"env": {
"PINECONE_API_KEY": "<YOUR_PINECONE_API_KEY_HERE>",
"PINECONE_ASSISTANT_HOST": "<YOUR_PINECONE_ASSISTANT_HOST_HERE>"
}
}
}
}Exposed MCP Tools (1)
safe
retrieve_informationRetrieves information from the Pinecone Assistant.
Read-only operation, no data modification.
Safety Assessment
This MCP server is relatively safe for retrieving information from Pinecone Assistant. The main risk is exposure of the Pinecone API key and potential information leakage. Ensure the API key is stored securely and the Pinecone Assistant does not contain overly sensitive data.
- Read-only access to Pinecone Assistant data.
- Requires API key for authentication.
- Runs in a Docker container, providing some isolation.
- No direct filesystem access.
- API key is passed as an environment variable, which could be exposed.
- Potential for information leakage if the Pinecone Assistant contains sensitive data.
- No built-in rate limiting; could potentially exhaust API quota.
- Vulnerable to supply chain attacks if the Docker image is compromised.
