A Model Context Protocol (MCP) server that enables Claude Desktop to search your content using Azure AI services. Choose between Azure AI Agent
Azure Ai Search MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A Model Context Protocol (MCP) server that enables Claude Desktop to search your content using Azure AI services. Choose between Azure AI Agent Service (with both document search and web search) or direct Azure AI Search integration.
This project provides two MCP server implementations to connect Claude Desktop with Azure search capabilities:
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Once Azure Ai Search is connected, these are the calls the assistant has available:
Customizable — Easy to extend or modify search behaviorYou will need 8 environment variables: PROJECT_CONNECTION_STRING, MODEL_DEPLOYMENT_NAME, AI_SEARCH_CONNECTION_NAME, BING_CONNECTION_NAME, AI_SEARCH_INDEX_NAME, AZURE_SEARCH_SERVICE_ENDPOINT, AZURE_SEARCH_INDEX_NAME, AZURE_SEARCH_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Azure Ai Search's toolset — Customizable — is a fair guide to whether it matches your workflow. It is maintained by farzad528; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Customizable | Easy to extend or modify search behavior |
### Configuring Claude Desktop
```json
{
"mcpServers": {
"azure-ai-agent": {
"command": "C:\\path\\to\\.venv\\Scripts\\python.exe",
"args": ["C:\\path\\to\\azure_ai_agent_service_server.py"],
"env": {
"PROJECT_CONNECTION_STRING": "your-project-connection-string",
"MODEL_DEPLOYMENT_NAME": "your-model-deployment-name",
"AI_SEARCH_CONNECTION_NAME": "your-search-connection-name",
"BING_CONNECTION_NAME": "your-bing-connection-name",
"AI_SEARCH_INDEX_NAME": "your-index-name"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PROJECT_CONNECTION_STRING | Configuration value read at startup. | Optional |
| MODEL_DEPLOYMENT_NAME | Configuration value read at startup. | Optional |
| AI_SEARCH_CONNECTION_NAME | Configuration value read at startup. | Optional |
| BING_CONNECTION_NAME | Configuration value read at startup. | Optional |
| AI_SEARCH_INDEX_NAME | Configuration value read at startup. | Optional |
| AZURE_SEARCH_SERVICE_ENDPOINT | Configuration value read at startup. | Optional |
| AZURE_SEARCH_INDEX_NAME | Configuration value read at startup. | Optional |
| AZURE_SEARCH_API_KEY | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.