Azure Wiki Search + Klavis AI: Complete MCP Integration
Azure Wiki Search is a MCP server that An MCP server that enables AI to query and search Azure DevOps Wiki content with intelligent search capabilities..
When integrated with Klavis AI, you can:
- Search Azure DevOps Wiki content with AI-powered queries
- Retrieve specific wiki pages by path or identifier
This guide provides step-by-step instructions to set up Azure Wiki Search in Klavis AI, including configuration, examples, and troubleshooting.
What You'll Achieve
After completing this setup:
- Azure Wiki Search will be fully integrated and operational
- You can use Azure Wiki Search tools directly in Klavis AI
- All Azure Wiki Search capabilities will be available for your workflows
- Access to 2 different tools
Prerequisites
Before starting, ensure you have:
- Azure DevOps organization name
- Azure DevOps project name
- Klavis AI installed and configured
- Compatible operating system (Cloud (klavis.ai), Self-Hosted (Docker), Python SDK, TypeScript SDK)
Installation
Step 1: Install Azure Wiki Search
Configuration
Step 2: Configure Klavis AI
- Open Klavis AI settings
- Navigate to MCP server configuration
- Add Azure Wiki Search server with appropriate settings
- Save and restart if needed
Examples
Once configured, you can use Azure Wiki Search in Klavis AI:
Search Technical Documentation
Find relevant technical documentation in Azure Wiki
Ask Klavis AI: "Search for API authentication documentation in the Edge project"
Expected Result: Relevant wiki pages containing authentication setup and API documentation
Retrieve Specific Wiki Page
Get content from a known wiki page path
Ask Klavis AI: "Get the content from /docs/setup/installation.md"
Expected Result: Full content of the installation documentation page
Find Troubleshooting Guides
Search for problem-solving documentation
Ask Klavis AI: "Find troubleshooting guides for deployment issues"
Expected Result: Wiki pages containing deployment troubleshooting information
Testing Your Setup
- Launch Klavis AI
- Verify Azure Wiki Search is available in the tools list
- Test basic Azure Wiki Search functionality
Troubleshooting
Common Issues
Authentication Failed
Symptoms: Access denied to wiki, Unauthorized errors, PAT token rejected
Cause: Missing or invalid Azure DevOps Personal Access Token
Solution:
- Generate PAT in Azure DevOps with Wiki read permissions
- Set AZURE_DEVOPS_PAT environment variable
- Verify PAT has access to specified organization/project
- Check PAT expiration date
Organization/Project Not Found
Symptoms: Project not found errors, Organization does not exist
Cause: Invalid ORG or PROJECT configuration
Solution:
- Verify organization name matches Azure DevOps URL
- Confirm project exists and is accessible
- Check spelling and case sensitivity
- Use --org and --project parameters to override defaults
Wiki Content Not Found
Symptoms: No search results, Wiki path not found, Empty responses
Cause: Wiki not configured or content not available
Solution:
- Verify project has Wiki enabled
- Check wiki content exists in specified project
- Confirm search terms match available content
- Try broader search queries initially
uv Environment Issues
Symptoms: Command not found, Package installation fails, Virtual env errors
Cause: uv not installed or virtual environment not activated
Solution:
- Install uv: curl -LsSf https://astral.sh/uv/install.sh | sh
- Activate virtual environment before running
- Ensure Python 3.10+ is available
- Reinstall dependencies if corruption occurred
API Authentication Failed
Symptoms: 401 Unauthorized errors, Invalid API key message
Cause: Missing or incorrect API key
Solution:
- Verify API key is correctly copied from klavis.ai dashboard
- Check API key is set in environment variable or code
- Ensure API key has not expired
- Regenerate API key if necessary
OAuth Authorization Errors
Symptoms: OAuth redirect failures, Authentication loop, Token refresh errors
Cause: OAuth credentials not configured or expired
Solution:
- Complete OAuth authorization flow for required services
- Check redirect URLs are correctly configured
- Verify OAuth app credentials in service provider settings
- Contact Klavis support for OAuth troubleshooting
Tool Call Failures
Symptoms: Tool not found errors, Execution timeouts, Rate limit errors
Cause: Tool not properly configured or service rate limits exceeded
Solution:
- Verify tool name matches available tools list
- Check service-specific rate limits and quotas
- Ensure required parameters are provided correctly
- Review Klavis API logs for detailed error messages
Context Window Overload
Symptoms: Too many tools error, Context length exceeded, Slow responses
Cause: Too many tools exposed to AI agent at once
Solution:
- Use Strata Progressive Discovery to expose tools hierarchically
- Reduce number of simultaneous MCP servers in Strata configuration
- Filter tools based on current task context
- Enable intelligent tool filtering in Strata settings
Docker Deployment Issues
Symptoms: Container fails to start, Port conflicts, Connection refused
Cause: Docker configuration or port binding errors
Solution:
- Ensure Docker is installed and running
- Check port 5000 is not already in use (or change port mapping)
- Verify Docker image pulled successfully
- Check container logs: docker logs <container-id>
Azure Wiki Search not appearing in Klavis AI
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check Azure Wiki Search installation
- Restart Klavis AI
- Check logs for error messages
Next Steps
Now that Azure Wiki Search is integrated with Klavis AI:
- Explore all Azure Wiki Search capabilities through Klavis AI
- Check out other MCP servers that work with Klavis AI
- Join the MCP community for tips and support
- Consider contributing to Azure Wiki Search development
Need Help?
- Search for Azure Wiki Search documentation
- Check the Klavis AI MCP guide
- Join the MCP community discussions