Azure AI Search MCP Server
Enables AI assistants to manage Azure AI Search services, including indexes, documents, indexers, and skillsets, via the Model Context Protocol.
README
Azure AI Search MCP Server
A powerful Model Context Protocol (MCP) server that enables AI assistants to manage Azure AI Search services. Deploy on Cloudflare Workers for global edge performance or run locally for development.
🚀 Quick Start
Fastest Setup: Connect to Deployed Server
# For Claude Code
claude mcp add --transport sse azure-search https://azure-search-mcp.lfd.workers.dev/sse \
--header "X-Azure-Search-Endpoint: https://your-service.search.windows.net" \
--header "X-Azure-Search-Api-Key: your-api-key"
# For Claude Desktop - add to config file
{
"mcpServers": {
"azure-search": {
"command": "npx",
"args": ["mcp-remote", "https://azure-search-mcp.lfd.workers.dev/sse"]
}
}
}
That's it! Start using Azure Search in your AI assistant immediately.
📋 Table of Contents
- Features
- Prerequisites
- Installation
- Usage Guide
- Available Operations
- Examples
- Troubleshooting
- Development
- Architecture
✨ Features
- 🔍 Complete Azure Search Management - Full control over indexes, documents, data sources, indexers, and skillsets
- 🤖 Intelligent Response Handling - Automatic summarization of large responses using GPT-4o-mini
- 📄 Smart Pagination - Efficient handling of large result sets with cursor-based pagination
- 🚀 Edge Deployment - Fast, globally distributed via Cloudflare Workers
- 🔌 Multiple Transports - SSE (Server-Sent Events) and HTTP support
- ⚡ Direct API Access - No OAuth complexity, uses Azure Search API keys
- 🛡️ Built-in Safety - Confirmation prompts for destructive operations
- 📊 Real-time Resources - Live monitoring of indexes, indexers, and service stats
📦 Prerequisites
Required
- Azure AI Search Service with:
- Endpoint URL (e.g.,
https://your-service.search.windows.net) - Admin API key (found in Azure Portal → Your Search Service → Keys)
- Endpoint URL (e.g.,
Optional
- Azure OpenAI (for intelligent summarization):
- Endpoint, API key, and deployment name (e.g.,
gpt-4o-mini)
- Endpoint, API key, and deployment name (e.g.,
- Cloudflare Account (for custom deployment)
- Node.js 18+ (for local development)
🔧 Installation
Option 1: Use the Deployed Server (Recommended)
The server is already deployed and ready to use at:
- Base URL:
https://azure-search-mcp.lfd.workers.dev - SSE Endpoint:
https://azure-search-mcp.lfd.workers.dev/sse - HTTP Endpoint:
https://azure-search-mcp.lfd.workers.dev/mcp
Connect with Claude Code
# SSE Transport (recommended)
claude mcp add --transport sse azure-search https://azure-search-mcp.lfd.workers.dev/sse \
--header "X-Azure-Search-Endpoint: https://your-service.search.windows.net" \
--header "X-Azure-Search-Api-Key: your-api-key"
# HTTP Transport
claude mcp add --transport http azure-search https://azure-search-mcp.lfd.workers.dev/mcp \
--header "X-Azure-Search-Endpoint: https://your-service.search.windows.net" \
--header "X-Azure-Search-Api-Key: your-api-key"
Connect with Claude Desktop
Add to your configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/claude/claude_desktop_config.json
{
"mcpServers": {
"azure-search": {
"command": "npx",
"args": ["mcp-remote", "https://azure-search-mcp.lfd.workers.dev/sse"],
"env": {
"AZURE_SEARCH_ENDPOINT": "https://your-service.search.windows.net",
"AZURE_SEARCH_API_KEY": "your-api-key"
}
}
}
}
Option 2: Deploy Your Own Instance
# Clone repository
git clone https://github.com/henryperkins/my-mcp-github.git
cd my-mcp-github
# Install dependencies
npm install
# Configure secrets
wrangler secret put AZURE_SEARCH_ENDPOINT
wrangler secret put AZURE_SEARCH_API_KEY
wrangler secret put AZURE_OPENAI_ENDPOINT # Optional
wrangler secret put AZURE_OPENAI_API_KEY # Optional
# Deploy to Cloudflare
npm run deploy
Option 3: Run Locally
# Clone and install
git clone https://github.com/henryperkins/my-mcp-github.git
cd my-mcp-github
npm install
# Create .dev.vars file
cat > .dev.vars << EOF
AZURE_SEARCH_ENDPOINT=https://your-service.search.windows.net
AZURE_SEARCH_API_KEY=your-api-key
AZURE_OPENAI_ENDPOINT=https://your-openai.openai.azure.com/ # Optional
AZURE_OPENAI_API_KEY=your-openai-key # Optional
EOF
# Run development server
npm run dev # Available at http://localhost:8788
# Or run with mock data (no Azure required)
npm run dev:mock
📖 Usage Guide
How to Interact with the Server
Once connected, you can interact naturally with your AI assistant. The server handles all the complexity behind the scenes.
Example Conversations
You: Show me all search indexes with their document counts
Claude: I'll list all the search indexes with their statistics.
[Lists indexes with document counts, storage sizes, and features]
You: Search for "laptop" in the products index with price under $1000
Claude: I'll search for laptops under $1000 in your products index.
[Returns filtered search results with relevant products]
You: Create an indexer to sync data from blob storage every hour
Claude: I'll create an indexer with hourly synchronization from your blob storage.
[Sets up the indexer with the specified schedule]
Verifying Connection
After adding the server, verify it's working:
# In Claude Code
/mcp
# Check specific server
claude mcp get azure-search
# List all servers
claude mcp list
🛠️ Available Operations
The server provides comprehensive Azure Search management through these tools:
📚 Index Management (IndexManagement)
| Operation | Description | Key Parameters |
|---|---|---|
list |
List all indexes with stats | includeStats, verbose, pageSize |
get |
Get index definition | indexName |
create |
Create new index | indexName, template, indexDefinition |
update |
Update index schema | indexName, indexDefinition |
delete |
Delete index | indexName (with confirmation) |
stats |
Get index statistics | indexName |
Templates available: documentSearch, productCatalog, hybridSearch, knowledgeBase
📄 Document Operations (DocumentOperations)
| Operation | Description | Key Parameters |
|---|---|---|
search |
Search documents | indexName, search, filter, orderBy |
get |
Get document by ID | indexName, key |
count |
Count documents | indexName, filter |
upload |
Upload new documents | indexName, documents |
merge |
Update existing documents | indexName, documents |
delete |
Delete documents | indexName, keys |
🔌 Data Source Management (DataSourceManagement)
| Operation | Description | Key Parameters |
|---|---|---|
list |
List data sources | - |
get |
Get data source details | name |
createBlob |
Create blob storage source | name, connectionString, container |
delete |
Delete data source | name |
test |
Test connection | name |
⚙️ Indexer Management (IndexerManagement)
| Operation | Description | Key Parameters |
|---|---|---|
list |
List all indexers | - |
get |
Get indexer config | name |
create |
Create new indexer | name, dataSource, targetIndex |
run |
Run indexer now | name |
reset |
Reset change tracking | name |
getStatus |
Get execution history | name, historyLimit |
🧠 Skillset Management (SkillsetManagement)
| Operation | Description | Key Parameters |
|---|---|---|
list |
List AI enrichment skillsets | - |
get |
Get skillset definition | name |
create |
Create skillset | name, skills |
validate |
Validate configuration | skillsetDefinition |
🔧 Service Utilities (ServiceUtilities)
| Operation | Description | Key Parameters |
|---|---|---|
serviceStats |
Get service quotas/usage | - |
analyzeText |
Test text analyzers | text, analyzer |
listSynonymMaps |
List synonym maps | - |
createOrUpdateSynonymMap |
Manage synonyms | name, synonyms |
💡 Examples
Creating a Product Catalog Index
You: Create a product catalog index named "products-v2" with English language support
Claude: I'll create a product catalog index with English language support for you.
[Creates index with appropriate fields for product data including name, description,
price, category, with proper analyzers for English text]
Complex Search with Filters
You: Search the orders index for pending orders from last week, sorted by amount
Claude: I'll search for pending orders from the last week, sorted by amount.
[Executes search with date filter, status filter, and ordering]
Setting Up Data Sync
You: Set up a complete data pipeline from my blob storage to a new search index
Claude: I'll help you set up a complete data pipeline. This will involve:
1. Creating a data source connection to your blob storage
2. Creating a target index with appropriate schema
3. Setting up an indexer to sync data
[Proceeds with step-by-step setup]
🔍 Troubleshooting
Common Issues and Solutions
"Connection closed" or "Not connected" Error
# Remove and re-add the server
claude mcp remove azure-search
claude mcp add --transport sse azure-search https://azure-search-mcp.lfd.workers.dev/sse \
--header "X-Azure-Search-Endpoint: https://your-service.search.windows.net" \
--header "X-Azure-Search-Api-Key: your-api-key"
Authentication Failures
- ✅ Verify API key has admin permissions
- ✅ Check endpoint URL format (should end with
.search.windows.net) - ✅ Ensure no extra spaces in credentials
- ✅ Confirm service is not in free tier (some operations require paid tiers)
Large Response Issues
- Responses >20KB are automatically summarized
- Configure Azure OpenAI for best results:
wrangler secret put AZURE_OPENAI_ENDPOINT wrangler secret put AZURE_OPENAI_API_KEY - Use pagination:
pageSizeandcursorparameters - Use
selectto limit returned fields
Rate Limiting (429 Errors)
- Implement exponential backoff
- Reduce request frequency
- Consider upgrading service tier
Windows-Specific Issues
For native Windows (not WSL), use cmd wrapper:
claude mcp add my-server -- cmd /c npx -y @azure/search-mcp
Debugging Tips
-
Enable verbose logging:
You: Set logging level to debug -
Check server status:
/mcp -
Test with mock data:
AZURE_SEARCH_MOCK=true npm run dev -
Inspect raw responses:
curl -X POST https://azure-search-mcp.lfd.workers.dev/mcp \ -H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'
🧪 Development
Local Development Setup
# Install dependencies
npm install
# Type checking
npm run type-check
# Run tests
npm test
# Generate Cloudflare types
npm run cf-typegen
# Watch logs
wrangler tail
Project Structure
azure-search-mcp/
├── src/
│ ├── index-dynamic.ts # Main MCP server with dynamic tools
│ ├── dynamic-tools/ # Tool implementations
│ │ ├── base/ # Base classes and interfaces
│ │ ├── IndexTool.ts # Index management operations
│ │ ├── DocumentTool.ts # Document operations
│ │ └── ... # Other tools
│ ├── azure-search-client.ts # Azure Search REST client
│ ├── azure-openai-client.ts # OpenAI integration
│ ├── resources.ts # MCP resource definitions
│ └── utils/ # Helper functions
├── docs/ # Documentation
├── test/ # Test files
└── wrangler.toml # Cloudflare configuration
Environment Variables
| Variable | Required | Description |
|---|---|---|
AZURE_SEARCH_ENDPOINT |
Yes | Your Azure Search service URL |
AZURE_SEARCH_API_KEY |
Yes | Admin API key |
AZURE_OPENAI_ENDPOINT |
No | Azure OpenAI endpoint for summarization |
AZURE_OPENAI_API_KEY |
No | Azure OpenAI API key |
AZURE_OPENAI_DEPLOYMENT |
No | Deployment name (default: gpt-4o-mini) |
🏗️ Architecture
Technical Stack
- Runtime: Cloudflare Workers with Durable Objects
- Protocol: Model Context Protocol (MCP) v2.0
- Language: TypeScript
- APIs:
- Azure Search REST API (2025-08-01-preview)
- Azure OpenAI API (2024-08-01-preview)
Key Design Decisions
- Dynamic Tool System: Multi-operation tools reduce overhead and improve performance
- Response Management: Automatic summarization/truncation for large payloads
- Direct API Access: Uses REST API instead of SDK for Workers compatibility
- Edge Deployment: Global distribution via Cloudflare's network
- No OAuth: Simplified authentication using API keys
Performance Optimizations
- Concurrent operations with controlled parallelism
- Response caching for frequently accessed data
- Streaming support for large result sets
- Automatic pagination (max 50 items default)
- Intelligent field selection to reduce payload size
🤝 Contributing
Contributions are welcome! Please:
- Fork the repository
- Create a feature branch
- Add tests for new functionality
- Ensure all tests pass
- Submit a pull request
📄 License
MIT License - See LICENSE file for details
🆘 Support
- Issues: GitHub Issues
- Discussions: GitHub Discussions
- MCP Documentation: modelcontextprotocol.io
- Azure Search Docs: docs.microsoft.com
🙏 Acknowledgments
- Built on the Model Context Protocol by Anthropic
- Powered by Cloudflare Workers
- Integrates with Azure AI Search and Azure OpenAI
Version: 2.0.0 | Last Updated: December 2024
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。