Provides comprehensive access to OpenAI's Vector Store API, enabling tools for creating, listing, and modifying vector stores, uploading files to OpenAI storage, and managing batch file operations.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Universal OpenAI Vector Store MCP Serverupload 'data.csv' to the 'Analytics' vector store"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Universal OpenAI Vector Store MCP Server
A production-ready Model Context Protocol (MCP) server that provides comprehensive OpenAI Vector Store API access through multiple deployment options. This server enables AI assistants like Claude, Roo, and other MCP clients to manage vector stores, files, and batch operations seamlessly.
π Universal MCP Server - Three Ways to Connect
Choose the deployment option that best fits your needs:
π Option 1: Cloudflare Workers (Production Ready)
Production URL: https://vectorstore.jezweb.com
β Zero setup required
β Global edge distribution
β Sub-100ms response times
β No local dependencies
π¦ Option 2: NPM Package (Local Stdio)
Package: openai-vector-store-mcp
β Direct stdio transport
β No proxy required
β Local execution
β Full control over environment
π§ Option 3: Local Development Server
Local Build: Clone and run locally
β Full source code access
β Customizable implementation
β Development and testing
β Private deployment options
β¨ Features
21 Comprehensive Tools - Complete file-to-vector-store workflow with OpenAI's APIs
File Upload Capabilities - Direct file upload from local filesystem to OpenAI
Production Ready - Deployed on Cloudflare Workers with global edge distribution
Zero Dependencies - Lightweight implementation with no runtime dependencies
Type Safe - Full TypeScript implementation with comprehensive type definitions
Secure Authentication - URL-based API key authentication
Error Handling - Robust error handling with detailed error messages
CORS Support - Ready for web-based MCP clients
Large File Support - Multipart uploads for files up to 512MB
π Current Status
β Phase 2 v1.2.0 Complete - Complete file-to-vector-store workflow with 21 tools β Production Deployment - Live on Cloudflare Workers with global edge distribution β Client Integration - Working with Claude Desktop, Roo, and all MCP clients β End-to-End Workflow - Upload files directly from local filesystem to vector stores β Real-World Ready - Solves the 470 PDF files scenario and similar use cases
π οΈ Available Tools (21 Total)
Core Vector Store Operations
vector-store-create - Create a new vector store with optional expiration and metadata
vector-store-list - List all vector stores with pagination and sorting
vector-store-get - Get detailed information about a specific vector store
vector-store-delete - Delete a vector store permanently
vector-store-modify - Update vector store name, expiration, or metadata
π File Upload & Management Operations (Phase 2)
file-upload - Upload local files directly to OpenAI (CRITICAL - enables end-to-end workflow)
file-list - List all uploaded files with filtering and pagination
file-get - Get detailed information about specific files
file-delete - Remove files from OpenAI storage
file-content - Download and retrieve file content
upload-create - Create multipart uploads for large files (>25MB)
Vector Store File Operations
vector-store-file-add - Add an existing file to a vector store
vector-store-file-list - List all files in a vector store with filtering
vector-store-file-get - Get details of a specific file in a vector store
vector-store-file-content - Retrieve the content of a file in a vector store
vector-store-file-update - Update file metadata
vector-store-file-delete - Remove a file from a vector store
Batch Operations
vector-store-file-batch-create - Create a batch operation for multiple files
vector-store-file-batch-get - Get the status of a batch operation
vector-store-file-batch-cancel - Cancel a running batch operation
vector-store-file-batch-files - List files in a batch operation
π Quick Start - Choose Your Installation Method
Prerequisites
OpenAI API key with Assistants API access
Node.js 18+ (for NPM package or local development)
MCP client (Claude Desktop, Roo, or other MCP-compatible client)
π Getting Started with OpenAI
Before using this MCP server, you'll need to set up your OpenAI account and API access:
1. Get Your OpenAI API Key
Visit the OpenAI API Keys page
Create a new API key or use an existing one
Copy your API key (starts with
sk-proj-orsk-)
2. Check Your Vector Store Dashboard
Monitor your vector stores at OpenAI Storage Dashboard
View usage, file counts, and storage limits
Track vector store expiration dates
3. Verify Assistants API Access
Ensure your account has access to the Assistants API
Check your OpenAI Usage Dashboard for API limits
Review OpenAI Pricing for vector store costs
4. Understand Vector Store Limits
Free Tier: Limited vector store usage
Paid Tier: Higher limits based on your plan
File Limits: Each vector store can contain up to 10,000 files
Storage Limits: Check your account's storage quota
π Helpful OpenAI Resources
π¦ Option 1: NPM Package (Recommended for Most Users)
Installation
π‘ Why use @latest?
Ensures you get the most recent bug fixes and improvements
Bypasses NPM cache issues that can cause outdated versions
Recommended for most reliable experience
Claude Desktop Configuration
Add to your claude_desktop_config.json:
Roo Configuration
Add to your Roo configuration file:
π₯οΈ Claude Code CLI Configuration
For users of Claude Code (CLI), you can add the MCP server using the command line interface:
Basic Setup
Scope Options
--scope local(default): Available only to you in the current project--scope project: Shared with everyone in the project via.mcp.jsonfile--scope user: Available to you across all projects
Managing MCP Servers
Project-Level Configuration (.mcp.json)
When using --scope project, Claude Code creates a .mcp.json file in your project root:
Environment Variable Expansion: Claude Code supports ${VAR} syntax for environment variables in .mcp.json files.
βοΈ Option 2: Cloudflare Workers (Zero Setup)
Claude Desktop Configuration
Install the MCP proxy:
Add to your
claude_desktop_config.json:
Roo Configuration
Install the MCP proxy:
Add to your Roo configuration:
π§ Option 3: Local Development Server
Setup
Clone the repository:
Install dependencies:
Set up environment variables:
Start development server:
Configuration
Use the local server URL in your MCP client configuration, replacing the Cloudflare Workers URL with your local development server URL (typically http://localhost:8787).
π Configuration File Locations
Claude Desktop
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json
Roo
Check your Roo installation documentation for the exact configuration file location
Typically:
~/.config/roo/config.jsonor similar
Important Notes
Replace API Key: Always replace
YOUR_OPENAI_API_KEY_HEREwith your actual OpenAI API keyRestart Client: Restart your MCP client after configuration changes
Roo Users: The
alwaysAllowarray is crucial for Roo to automatically approve tool usageSecurity: Never commit your API key to version control
π Usage Examples
π Complete End-to-End Workflow (Phase 2 v1.2.0)
The Problem Solved: Previously, users had to manually upload files to OpenAI before using vector store tools. Now you can upload files directly from your local filesystem!
Basic Workflow
Real-World Example: Processing 470 PDF Files
Advanced Workflow: Large File Handling
File Upload & Management
Basic Vector Store Management
Vector Store File Operations
Batch Operations
Real-World Use Cases
π Document Processing Pipeline
π» Code Analysis Workflow
π Knowledge Base Creation
π¬ Research and Analysis
π Data Processing Workflows
ποΈ Architecture
Clean Design Principles
Single Worker Pattern - All functionality in one Cloudflare Worker
URL-Based Authentication - Simple
/mcp/{api-key}patternDirect HTTP Transport - No complex proxy layers needed
Minimal Dependencies - Only TypeScript types for development
Type Safety - Comprehensive TypeScript throughout
File Structure
Key Components
Worker - Handles HTTP requests and CORS
MCP Handler - Implements MCP protocol (initialize, tools/list, tools/call)
OpenAI Service - Wraps OpenAI Vector Store API calls
Types - Comprehensive TypeScript definitions
π§ͺ Testing
Manual Testing
Test the server directly with curl:
Client Testing
Use the provided test scripts:
test-mcp-client.js- Node.js MCP client testtest-mcp-http-client.js- Direct HTTP API testdemo-vector-store-mcp.js- Comprehensive demo
π Documentation
Setup Guides
Client Setup Guide - Detailed setup instructions
Vector Store Usage Guide - Usage examples and patterns
Client Integration Guide - Integration patterns
Technical Documentation
Project Brief - Mission and overview
Requirements - Technical requirements
Architecture - System design
API Reference - OpenAI API details
Implementation Guide - Development guide
Testing Guide - Testing strategies
Deployment Guide - Cloudflare deployment
Examples - Code templates
Project Summary - Complete overview
π§ Development
Local Development
Clone the repository:
Install dependencies:
Set up environment variables:
Start development server:
Deployment
Deploy to Cloudflare Workers:
The server will be available at your Cloudflare Workers domain.
π Security
API Key Protection - API keys are passed via URL path, not logged
Input Validation - All inputs validated before processing
Error Handling - Errors don't expose sensitive information
CORS Security - Proper CORS headers for web clients
Rate Limiting - Inherits OpenAI API rate limits
π Performance
Global Edge - Deployed on Cloudflare's global network
Sub-100ms - Typical response times under 100ms
Zero Cold Start - Cloudflare Workers eliminate cold starts
Efficient - Minimal memory footprint and fast execution
π€ Contributing
Fork the repository
Create a feature branch
Make your changes
Add tests if applicable
Submit a pull request
π License
MIT License - see LICENSE for details.
π Troubleshooting & Support
@latest Package Issues
NPM Cache Problems
If you're experiencing issues with outdated versions, use @latest to bypass cache:
Version Conflicts
Client-Specific Troubleshooting
Claude Desktop Issues
Configuration file issues:
Claude Code CLI Issues
Server not connecting:
Scope-related issues:
Project .mcp.json issues:
Common Connection Issues
1. "Server not found" or "Connection failed"
For NPM Package Users:
For Cloudflare Workers Users:
For Local Development:
2. "Authentication failed" or "Invalid API key"
Verify your OpenAI API key is valid and active
Check that your API key has access to the Assistants API
Ensure there are no extra spaces or characters in your API key
Test your API key with OpenAI's official tools
3. "Tools not available" or "No MCP tools found"
Restart your MCP client after configuration changes
Check the configuration file syntax is valid JSON
Verify the configuration file is in the correct location
For NPM package: Ensure Node.js 18+ is installed
4. Roo-Specific Issues
"Permission denied" errors:
Ensure
alwaysAllowis configured for all 21 toolsCheck that tool names in
alwaysAllowmatch exactlyRestart Roo after configuration changes
Tool approval prompts:
Add all tool names to the
alwaysAllowarrayUse the exact tool names as listed in the documentation
Include the new Phase 2 file management tools:
file-upload,file-list,file-get,file-delete,file-content,upload-create
Platform-Specific Setup
macOS
Windows
Linux
Performance Optimization
For High-Volume Usage
Use NPM Package: Direct stdio transport is faster than HTTP proxy
Local Development: Run locally for maximum performance
Batch Operations: Use batch tools for multiple file operations
Rate Limiting: Be aware of OpenAI API rate limits
For Reliability
Cloudflare Workers: Global edge distribution with 99.9% uptime
Error Handling: All implementations include comprehensive error handling
Retry Logic: Built-in retry for transient failures
Debug Mode
NPM Package Debug
Cloudflare Workers Debug
Getting Help
Check Documentation: Review the Universal MCP Server Guide
Test Isolation: Test each component separately (API key, server, client)
Configuration Validation: Use JSON validators for configuration files
Community Support: Check MCP community resources and forums
Migration from Previous Versions
If upgrading from version 1.1.x to 1.2.0:
New File Management Tools: 6 new tools added for complete file-to-vector-store workflow
Update Roo Configuration: Add new tools to
alwaysAllowarray for seamless operationEnhanced Capabilities: Now supports direct file upload from local filesystem
Version Update: Update package references to use version 1.2.0
If upgrading from version 1.0.x:
Update Configuration: New installation options available
Tool Names: All 21 tools now available (was 4 in early versions)
Performance: Significant improvements in response times
Reliability: Enhanced error handling and retry logic
Security Considerations
API Key Protection: Never commit API keys to version control
Environment Variables: Use environment variables for sensitive data
Network Security: All communications use HTTPS/TLS
Access Control: Server inherits your OpenAI API key permissions
π Best Practices
Package Version Management
When to Use @latest
Recommended for most users: Ensures you get the latest bug fixes and improvements
NPM cache issues: Bypasses cache problems that can cause outdated versions
New installations: Always use @latest for fresh setups
Troubleshooting: First step when experiencing issues
When to Pin Versions
Production environments: Consider pinning to specific versions for stability
CI/CD pipelines: Pin versions to ensure reproducible builds
Team coordination: Pin when entire team needs same version
Version Management Commands
Client Configuration Best Practices
Claude Desktop
Always use
@latestin configuration filesRestart Claude Desktop after configuration changes
Use environment variables for API keys
Validate JSON syntax before saving
Claude Code CLI
Use appropriate scope for your needs:
--scope local: Personal development--scope project: Team collaboration--scope user: Cross-project utilities
Leverage environment variable expansion in
.mcp.jsonUse
/mcpcommand to check server status
Roo
Always include complete
alwaysAllowarrayUse exact tool names as documented
Restart Roo after configuration changes
Prefer NPM package over Cloudflare Workers for best performance
Troubleshooting Matrix
Issue | Claude Desktop | Claude Code CLI | Roo |
Outdated Version | Use |
| Use |
Cache Issues |
|
|
|
Permission Denied | Check API key in env | Check | Add tools to |
Server Not Found | Restart client |
| Restart Roo |
Config Syntax | Validate JSON |
| Validate JSON |
Security Best Practices
API Key Management
Never commit API keys to version control
Use environment variables in configuration files
Rotate API keys regularly
Monitor API usage for unusual activity
Configuration Security
Keep configuration files in secure locations
Use appropriate file permissions
Avoid sharing configuration files with embedded keys
Network Security
All communications use HTTPS/TLS
Server inherits your OpenAI API key permissions
Consider firewall rules for local development
π― Roadmap
Version 1.2.0 - Complete File-to-Vector-Store Workflow β COMPLETED
File Upload Capabilities: Direct file upload from local filesystem to OpenAI
Complete End-to-End Workflow: Transform from vector store management to complete pipeline
Large File Support: Multipart uploads for files up to 512MB
File Management Suite: Comprehensive file operations (upload, list, get, delete, content)
Memory Efficiency: Streaming uploads for large files
MIME Type Detection: Automatic content type detection
21 Total Tools: 6 new file management tools + 15 existing vector store tools
Real-World Problem Solved: 470 PDF files scenario and similar bulk processing use cases
Production Ready: Deployed and tested on Cloudflare Workers
Client Integration: Full compatibility with Claude Desktop, Roo, and all MCP clients
Version 1.1.0 - Universal MCP Server β
Three Installation Options: NPM package, Cloudflare Workers, Local development
Enhanced Roo Support: Complete
alwaysAllowconfiguration and troubleshootingComprehensive Documentation: Universal setup guide with platform-specific instructions
Performance Optimization: Direct stdio transport for NPM package
Advanced Troubleshooting: Platform-specific debug guides and migration instructions
Security Enhancements: Environment variable support and improved API key handling
Version 1.0.0 - Core Implementation β
Core vector store operations (create, list, get, delete, modify)
File management operations (add, list, get, content, update, delete)
Batch operations (create, get, cancel, list files)
Production deployment on Cloudflare Workers
Client integration with Claude Desktop and Roo
Comprehensive documentation and testing
Future Enhancements π§
Advanced Search: Vector similarity search and filtering within vector stores
Caching Layer: Redis/KV caching for improved performance
Webhook Support: Async operation notifications for long-running uploads
Multi-Provider Support: Support for other vector store providers (Pinecone, Weaviate)
Web Interface: Optional web UI for vector store and file management
Batch File Processing: Upload and process multiple files in a single operation
File Format Conversion: Automatic conversion between supported file formats
Content Extraction: Enhanced text extraction from PDFs, images, and other formats
Version History
v1.2.0 (Current - January 30, 2025): Complete file-to-vector-store workflow with 21 tools
v1.1.0 (January 29, 2025): Universal MCP Server with three deployment options
v1.0.1 (December 15, 2024): NPM package improvements and bug fixes
v1.0.0 (December 1, 2024): Initial release with Cloudflare Workers deployment
Ready to get started? Choose your preferred installation method from the Quick Start guide above or check out the Universal MCP Server Guide for complete documentation.