{"format":"verfy.mcp-server/1","page":"https://verfy.dev/servers/pinecone","collectedAt":"2026-11-13","server":{"id":"pinecone","eco":"npm","pkg":"@pinecone-database/mcp","releases":[{"version":"0.1.16","published":"2025-09-15","started":true},{"version":"0.1.17","published":"2025-09-25","started":true},{"version":"0.2.0","published":"2026-01-27","started":true},{"version":"0.2.1","published":"2026-02-05","started":true},{"version":"0.3.0","published":"2026-08-07","started":true},{"version":"0.4.0","published":"2026-10-29","started":true}],"tools":[{"name":"search-docs","pin":"sha256:05858ae9926902e32f26ef486b9abfba273a2213e34768285e5cf0cb50a55f2a","description":"Search the official Pinecone documentation for relevant\ninformation. Use this before writing Pinecone code or explaining Pinecone\nbehavior, rather than relying on assumptions."},{"name":"list-indexes","pin":"sha256:139fcc436aa758519ea29255d78e38ab64147f8190e020dc26ea4c6fa80e5faf","description":"List all Pinecone indexes in the project, including each\nindex's configuration and readiness status. Use this to discover valid index\nnames before calling other tools."},{"name":"describe-index","pin":"sha256:227665ce653d25fbdacfabc4d957fe749c611ba6246f912b7aba022d9c60151d","description":"Describe the configuration of a Pinecone index, including\nits embedding model and the \"fieldMap\" that names the record field holding the\ntext to embed. Call this before upsert-records to learn the required field\nname. Check \"status.ready\" in the response to confirm the index can accept\nupserts and queries."},{"name":"describe-index-stats","pin":"sha256:368a44713b23f5ac6b774b13b7d253016cf77a3aa970ff005f5121656befe40f","description":"Describe the statistics of a Pinecone index, including\nrecord counts per namespace. Use this to discover which namespaces exist in an\nindex. Newly upserted records can take a few seconds\nto be indexed and become visible to search results and index stats; if recent\ndata is missing, wait briefly and retry."},{"name":"create-document-index","pin":"sha256:54c02a9879ee56cda44b46fa9de770b09ea30013c298abdbddd1c7618a8b1b80","description":"Create a Pinecone document index: an index defined by a\nschema of searchable \"string\" fields. Each field can declare \"fullTextSearch\"\n(indexed for keyword search with BM25), \"embed\" (Pinecone embeds the text with a\nhosted dense model for semantic search), \"sparseEmbed\" (a hosted sparse model),\nor a combination. A good default is one field with both, for example\n{\"chunk_text\": {\"fullTextSearch\": {\"language\": \"en\"}, \"embed\": {}}}, which\nsupports search by meaning and by exact terms on the same text. Fields you only\nneed to filter on are not declared here; send them as document metadata.\nUse upsert-documents and search-document-index with the new index. This call blocks\nuntil the index is ready. If an index with the same name already exists, it is\nreturned unchanged instead of erroring."},{"name":"upsert-documents","pin":"sha256:4d4d497da41bbdbb137de3c1dd4393961c271995f20902f1c0078845739bcce7","description":"Insert or update documents in a Pinecone document index\n(one created with create-document-index). Each document needs an \"_id\" and\nplain text in every field the index declares with \"embed\"; Pinecone embeds that\ntext on write, so never send vectors. Call describe-index first to see the\nschema. Fields not in the schema are stored as metadata you can filter on.\nDocuments with an existing \"_id\" are replaced. Newly upserted records can take a few seconds\nto be indexed and become visible to search results and index stats; if recent\ndata is missing, wait briefly and retry."},{"name":"search-document-index","pin":"sha256:7d74be9c17e89d93027217c134aa6599e756afb6e35c546f293776c521493914","description":"Search a Pinecone document index (one created with\ncreate-document-index). Call describe-index first to see which fields declare\n\"embed\", \"sparseEmbed\", or \"fullTextSearch\". Rank with one or more \"scoreBy\"\nclauses:\n- \"embed\": search by meaning on a field with \"embed\". Pass the query as plain\ntext; Pinecone embeds it with the field's model.\n- \"sparse_embed\": search a field with \"sparseEmbed\" the same way.\n- \"text\": keyword (BM25) search on one or more full-text fields. Good for exact\nterms like IDs, error codes, and names.\n- \"query_string\": Lucene-style query syntax. Don't pass \"fields\" (the API\nrejects it); target fields with qualifiers inside the query, for example\n'chunk_text:\"exact phrase\"', or omit qualifiers to search every full-text field.\nAn \"embed\" or \"sparse_embed\" clause must be the only clause; \"text\" and\n\"query_string\" clauses can be combined. To rank by meaning and by exact terms,\nrun two separate searches: their scores are on different scales, so don't\ncompare them across searches. Returns matches with \"_id\", \"_score\", and the\nfields named in \"includeFields\". Newly upserted records can take a few seconds\nto be indexed and become visible to search results and index stats; if recent\ndata is missing, wait briefly and retry."},{"name":"create-index-for-model","pin":"sha256:db70f4c45976d9ed9c8dcb034f15324a3a426ae62101dc761a2a034517b0930c","description":"Create a Pinecone index with integrated inference, which\nautomatically embeds the text field named in \"fieldMap\". Supports AWS, GCP, and\nAzure cloud providers. This call blocks until the index is ready to accept\nupserts and queries, so no readiness polling is needed afterwards. If an index\nwith the same name already exists, it is returned unchanged instead of\nerroring. For a new index, prefer create-document-index, which supports\nfull-text search and integrated embedding on the same field."},{"name":"upsert-records","pin":"sha256:03281f56289ce5d2b78ffbb4840833ef7909a2fd09b32449283b3414c9a456f8","description":"Insert or update records in an integrated Pinecone index.\nFor a document index, use upsert-documents instead.\nText in the field named by the index's \"fieldMap\" is embedded automatically —\ncall describe-index first to confirm that field name. Records with an existing\n\"id\" are overwritten. Newly upserted records can take a few seconds\nto be indexed and become visible to search results and index stats; if recent\ndata is missing, wait briefly and retry."},{"name":"search-records","pin":"sha256:d57e3ca3a38e2cc6d398dd398fe15e31ab9a2c298e830d936fe992b732c50c57","description":"Search an index for records that are semantically similar\nto the query text. Only works with integrated-inference indexes (e.g. created\nwith create-index-for-model), which embed the query automatically; it fails on\nstandard indexes and document indexes (use search-document-index for those) — use\ndescribe-index to check the index type. Returns hits\nwith \"_id\", \"_score\", and the record's stored \"fields\". Newly upserted records can take a few seconds\nto be indexed and become visible to search results and index stats; if recent\ndata is missing, wait briefly and retry."},{"name":"rerank-documents","pin":"sha256:ed730240d7689f394c84fb126973a8c0bc734c886e4c4067dc14a4af0f6e2607","description":"Rerank a set of provided documents by relevance to a\nquery. Use this for documents that did not come from a Pinecone search (e.g.\nexternally sourced text). To rerank the results of a single-index search,\nprefer the \"rerank\" parameter of search-records instead of calling this tool\nseparately."},{"name":"cascading-search","pin":"sha256:377ad43dd3dbf2bbf81bbf2730513baee187368204ace869ce1e3ebdece2f14d","description":"Search across multiple indexes for records that are\nsimilar to the query text, then deduplicate and rerank the combined results.\nReranking is required for this tool. Only works with integrated-inference\nindexes. To search a single index, use search-records instead."}],"updates":[{"from":"0.1.16","to":"0.1.17","published":"2025-09-25","bump":"patch","added":[],"removed":[],"changed":[]},{"from":"0.1.17","to":"0.2.0","published":"2026-01-27","bump":"minor","added":[],"removed":[],"changed":[{"tool":"cascading-search","description":false,"schema":true,"propsAdded":["llm_model","llm_provider"],"propsRemoved":[]},{"tool":"create-index-for-model","description":true,"schema":true,"before":"Create a Pinecone index with integrated inference","after":"Create a Pinecone index with integrated inference. Supports AWS, GCP, and Azure cloud providers.","propsAdded":["cloud","llm_model","llm_provider","region"],"propsRemoved":[]},{"tool":"describe-index","description":false,"schema":true,"propsAdded":["llm_model","llm_provider"],"propsRemoved":[]},{"tool":"describe-index-stats","description":false,"schema":true,"propsAdded":["llm_model","llm_provider"],"propsRemoved":[]},{"tool":"list-indexes","description":false,"schema":true,"propsAdded":["llm_model","llm_provider"],"propsRemoved":[]},{"tool":"rerank-documents","description":false,"schema":true,"propsAdded":["llm_model","llm_provider"],"propsRemoved":[]},{"tool":"search-docs","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"search-records","description":false,"schema":true,"propsAdded":["llm_model","llm_provider"],"propsRemoved":[]},{"tool":"upsert-records","description":false,"schema":true,"propsAdded":["llm_model","llm_provider"],"propsRemoved":[]}]},{"from":"0.2.0","to":"0.2.1","published":"2026-02-05","bump":"patch","added":[],"removed":[],"changed":[]},{"from":"0.2.1","to":"0.3.0","published":"2026-08-07","bump":"minor","added":[],"removed":[],"changed":[{"tool":"cascading-search","description":true,"schema":true,"before":"Search across multiple indexes for records that are\nsimilar to the query text, deduplicate and rerank the results.","after":"Search across multiple indexes for records that are\nsimilar to the query text, then deduplicate and rerank the combined results.\nReranking is required for this tool. Only works with integrated-inference\nindexes. To search a single index, use search-records instead.","propsAdded":[],"propsRemoved":[]},{"tool":"create-index-for-model","description":true,"schema":false,"before":"Create a Pinecone index with integrated inference. Supports AWS, GCP, and Azure cloud providers.","after":"Create a Pinecone index with integrated inference, which\nautomatically embeds the text field named in \"fieldMap\". Supports AWS, GCP, and\nAzure cloud providers. This call blocks until the index is ready to accept\nupserts and queries, so no readiness polling is needed afterwards. If an index\nwith the same name already exists, it is returned unchanged instead of\nerroring."},{"tool":"describe-index","description":true,"schema":false,"before":"Describe the configuration of a Pinecone index","after":"Describe the configuration of a Pinecone index, including\nits embedding model and the \"fieldMap\" that names the record field holding the\ntext to embed. Call this before upsert-records to learn the required field\nname. Check \"status.ready\" in the response to confirm the index can accept\nupserts and queries."},{"tool":"describe-index-stats","description":true,"schema":false,"before":"Describe the statistics of a Pinecone index and its namespaces","after":"Describe the statistics of a Pinecone index, including\nrecord counts per namespace. Use this to discover which namespaces exist in an\nindex. Newly upserted records can take a few seconds\nto be indexed and become visible to search results and index stats; if recent\ndata is missing, wait briefly and retry."},{"tool":"list-indexes","description":true,"schema":false,"before":"List all Pinecone indexes","after":"List all Pinecone indexes in the project, including each\nindex's configuration and readiness status. Use this to discover valid index\nnames before calling other tools."},{"tool":"rerank-documents","description":true,"schema":true,"before":"Rerank a set of documents based on a query","after":"Rerank a set of provided documents by relevance to a\nquery. Use this for documents that did not come from a Pinecone search (e.g.\nexternally sourced text). To rerank the results of a single-index search,\nprefer the \"rerank\" parameter of search-records instead of calling this tool\nseparately.","propsAdded":[],"propsRemoved":[]},{"tool":"search-docs","description":true,"schema":false,"before":"Search Pinecone documentation for relevant information","after":"Search the official Pinecone documentation for relevant\ninformation. Use this before writing Pinecone code or explaining Pinecone\nbehavior, rather than relying on assumptions."},{"tool":"search-records","description":true,"schema":true,"before":"Search an index for records that are similar to the query text","after":"Search an index for records that are semantically similar\nto the query text. Only works with integrated-inference indexes (e.g. created\nwith create-index-for-model), which embed the query automatically; it fails on\nstandard indexes — use describe-index to check the index type. Returns hits\nwith \"_id\", \"_score\", and the record's stored \"fields\". Newly upserted records can take a few seconds\nto be indexed and become visible to search results and index stats; if recent\ndata is missing, wait briefly and retry.","propsAdded":[],"propsRemoved":[]},{"tool":"upsert-records","description":true,"schema":true,"before":"Insert or update records in a Pinecone index","after":"Insert or update records in an integrated Pinecone index.\nText in the field named by the index's \"fieldMap\" is embedded automatically —\ncall describe-index first to confirm that field name. Records with an existing\n\"id\" are overwritten. Newly upserted records can take a few seconds\nto be indexed and become visible to search results and index stats; if recent\ndata is missing, wait briefly and retry.","propsAdded":[],"propsRemoved":[]}]},{"from":"0.3.0","to":"0.4.0","published":"2026-10-29","bump":"minor","added":["create-document-index","search-document-index","upsert-documents"],"removed":[],"changed":[{"tool":"create-index-for-model","description":true,"schema":false,"before":"Create a Pinecone index with integrated inference, which\nautomatically embeds the text field named in \"fieldMap\". Supports AWS, GCP, and\nAzure cloud providers. This call blocks until the index is ready to accept\nupserts and queries, so no readiness polling is needed afterwards. If an index\nwith the same name already exists, it is returned unchanged instead of\nerroring.","after":"Create a Pinecone index with integrated inference, which\nautomatically embeds the text field named in \"fieldMap\". Supports AWS, GCP, and\nAzure cloud providers. This call blocks until the index is ready to accept\nupserts and queries, so no readiness polling is needed afterwards. If an index\nwith the same name already exists, it is returned unchanged instead of\nerroring. For a new index, prefer create-document-index, which supports\nfull-text search and integrated embedding on the same field."},{"tool":"search-records","description":true,"schema":false,"before":"Search an index for records that are semantically similar\nto the query text. Only works with integrated-inference indexes (e.g. created\nwith create-index-for-model), which embed the query automatically; it fails on\nstandard indexes — use describe-index to check the index type. Returns hits\nwith \"_id\", \"_score\", and the record's stored \"fields\". Newly upserted records can take a few seconds\nto be indexed and become visible to search results and index stats; if recent\ndata is missing, wait briefly and retry.","after":"Search an index for records that are semantically similar\nto the query text. Only works with integrated-inference indexes (e.g. created\nwith create-index-for-model), which embed the query automatically; it fails on\nstandard indexes and document indexes (use search-document-index for those) — use\ndescribe-index to check the index type. Returns hits\nwith \"_id\", \"_score\", and the record's stored \"fields\". Newly upserted records can take a few seconds\nto be indexed and become visible to search results and index stats; if recent\ndata is missing, wait briefly and retry."},{"tool":"upsert-records","description":true,"schema":false,"before":"Insert or update records in an integrated Pinecone index.\nText in the field named by the index's \"fieldMap\" is embedded automatically —\ncall describe-index first to confirm that field name. Records with an existing\n\"id\" are overwritten. Newly upserted records can take a few seconds\nto be indexed and become visible to search results and index stats; if recent\ndata is missing, wait briefly and retry.","after":"Insert or update records in an integrated Pinecone index.\nFor a document index, use upsert-documents instead.\nText in the field named by the index's \"fieldMap\" is embedded automatically —\ncall describe-index first to confirm that field name. Records with an existing\n\"id\" are overwritten. Newly upserted records can take a few seconds\nto be indexed and become visible to search results and index stats; if recent\ndata is missing, wait briefly and retry."}]}]}}