WCC Pinecone Integration avatar
WCC Pinecone Integration

Under maintenance

Pricing

Pay per usage

Go to Store
WCC Pinecone Integration

WCC Pinecone Integration

Under maintenance

Developed by

Tri⟁angle

Tri⟁angle

Maintained by Apify

Crawl any website and store its content in your Pinecone vector database. Enhance the accuracy and reliability of your own AI Assistant with facts fetched from external sources or connect this integration to our Pinecone GPT Chatbot assistant available in Apify Store.

3.9 (5)

Pricing

Pay per usage

6

Total users

140

Monthly users

20

Runs succeeded

5.3%

Issues response

14 days

Last modified

4 months ago

You can access the WCC Pinecone Integration programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.

{
"mcpServers": {
"local-actors-mcp-server": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server",
"--actors",
"tri_angle/wcc-pinecone-integration"
],
"env": {
"APIFY_TOKEN": "<YOUR_API_TOKEN>"
}
}
}
}

Configure MCP server with 🌲 WCC Pinecone Integration

You can interact with the MCP server via standard input/output - stdio (as shown above), which is ideal for local integrations and command-line tools such as the Claude desktop client, or you can interact with the server through Server-Sent Events (SSE) to send messages and receive responses, which looks as follows:

{
"mcpServers": {
"remote-actors-mcp-server": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=tri_angle/wcc-pinecone-integration",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other supported MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.