Can I use Pinecone as a CLI?

Yes. KosmoKrator exposes a Pinecone CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Pinecone through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Pinecone tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Pinecone credentials stored?

Pinecone credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Pinecone MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

database

Pinecone CLI for Shell Scripts

Use the Pinecone CLI for shell scripts with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 5 read 2 write Bearer token auth

Submit Pinecone feedback View package source

Pinecone CLI for Shell Scripts

Call integration functions from shell scripts with stable JSON input and output.

Use shell scripts for small local automations that need one or more integration calls. The Pinecone CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Pinecone CLI for Shell Scripts
kosmokrator integrations:configure pinecone --set access_token="$PINECONE_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call pinecone.pinecone_list_indexes '{}' --json

Discovery Before Execution

Agents and scripts can inspect Pinecone docs and schemas before choosing a function.

kosmo integrations:docs pinecone --json
kosmo integrations:docs pinecone.pinecone_list_indexes --json
kosmo integrations:schema pinecone.pinecone_list_indexes --json
kosmo integrations:search "Pinecone" --json
kosmo integrations:list --json

Useful Pinecone CLI Functions

Function	Type	Parameters	Description
`pinecone.pinecone_list_indexes`	Read	none	List all vector indexes in your Pinecone project. Returns index names, dimensions, metrics, and status.
`pinecone.pinecone_get_index`	Read	name	Get detailed information about a specific Pinecone vector index, including its dimension, metric, host URL, and status.
`pinecone.pinecone_create_index`	Write	name, dimension, metric	Create a new serverless vector index in Pinecone. Specify the index name, vector dimension, and similarity metric (cosine, euclidean, or dotproduct).
`pinecone.pinecone_upsert_vectors`	Write	index_host, vectors	Upsert vectors into a Pinecone index using an index host URL.
`pinecone.pinecone_query_vectors`	Read	index_host, vector, top_k, filter, include_metadata	Search for similar vectors in a Pinecone index using a query embedding.
`pinecone.pinecone_list_collections`	Read	none	List all collections in your Pinecone project. Collections are static snapshots of indexes used for backups or creating new indexes.
`pinecone.pinecone_get_current_user`	Read	none	Get information about the currently authenticated Pinecone user, including email, name, and project details.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Pinecone CLI Pages

CI Pinecone CLI for CI. Cron Jobs Pinecone CLI for cron jobs. Headless Automation Pinecone CLI for headless automation. Coding Agents Pinecone CLI for coding agents.