Pinecone Developer MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PINECONE_API_KEY | No | Your Pinecone API key generated from the console at https://app.pinecone.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-docsB | Search Pinecone documentation for relevant information |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined as searching Pinecone documentation.
With only one tool, naming consistency is trivially satisfied. The name 'search-docs' follows a clear verb_noun pattern.
A single search tool for a developer MCP server is far too limited. Pinecone developers typically need operations for managing indexes, vectors, and configurations, making 1 tool insufficient for the apparent scope.
The server is severely incomplete. A Pinecone Developer MCP should include tools for creating, listing, updating, and deleting indexes, as well as vector operations. Only a documentation search tool leaves major gaps.