Skip to main content
Glama
uright

Azure DevOps Wiki MCP Server

by uright

search_wiki

Search Azure DevOps wiki content to find specific pages and information. Optionally filter by project or wiki.

Instructions

Search across wiki content using Azure DevOps Search API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationNoAzure DevOps organization name
projectNoProject name
searchTextYesSearch query string
wikiIdNoOptional specific wiki identifier

Implementation Reference

  • Handler method that parses the search_wiki request args via WikiSearchRequestSchema, resolves organization/project, creates a client, and calls client.searchWiki(request). Returns results as formatted JSON.
    private async handleSearchWiki(args: any) {
      const request = WikiSearchRequestSchema.parse(args);
      const organization = request.organization || this.config.defaultOrganization;
      const project = request.project || this.config.defaultProject;
      
      if (!organization) {
        throw new Error('Organization is required either as parameter or in server configuration');
      }
      if (!project) {
        throw new Error('Project is required either as parameter or in server configuration');
      }
      
      const client = await this.getClient(organization, project);
      const results = await client.searchWiki(request);
      
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(results, null, 2)
        }]
      };
    }
  • Actual implementation of the wiki search logic. Builds a POST request to the Azure DevOps Search API endpoint (almsearch.dev.azure.com), sends the search text and optional wiki filter, and maps the response to WikiSearchResult objects.
    async searchWiki(request: WikiSearchRequest): Promise<WikiSearchResult[]> {
      if (!this.wikiApi || !this.connection) {
        throw new Error('Azure DevOps client not initialized');
      }
    
      try {
        const organization = request.organization || this.config.organization;
        const project = request.project || this.config.project;
        
        if (!organization || !project) {
          throw new Error('Organization and project must be provided');
        }
    
        const searchApiUrl = `https://almsearch.dev.azure.com/${organization}/${project}/_apis/search/wikisearchresults?api-version=7.1`;
        
        interface WikiSearchRequestBody {
          searchText: string;
          $skip: number;
          $top: number;
          includeFacets: boolean;
          filters?: {
            Wiki?: string[];
          };
        }
    
        const requestBody: WikiSearchRequestBody = {
          searchText: request.searchText,
          $skip: 0,
          $top: 100, // Default to 100 results
          includeFacets: false
        };
    
        // Add wiki filter if specified
        if (request.wikiId) {
          requestBody.filters = {
            Wiki: [request.wikiId]
          };
        }
    
        const response = await this.connection.rest.client.post(searchApiUrl, JSON.stringify(requestBody), {
          'Content-Type': 'application/json'
        });
        
        if (!response.message || response.message.statusCode !== 200) {
          throw new Error(`Search failed: HTTP ${response.message?.statusCode || 'Unknown'}`);
        }
    
        const responseBody = await response.readBody();
        if (!responseBody) {
          return [];
        }
    
        const data = JSON.parse(responseBody);
        
        if (!data.results || !Array.isArray(data.results)) {
          return [];
        }
    
        interface WikiSearchResultItem {
          fileName?: string;
          path?: string;
          url?: string;
          matches?: {
            content?: { text: string }[];
          };
          project?: {
            name: string;
          };
          wiki?: {
            name: string;
          };
        }
    
        return data.results.map((result: WikiSearchResultItem) => ({
          title: result.fileName || (result.path ? result.path.split('/').pop() || 'Unknown' : 'Unknown'),
          url: result.url || '',
          content: result.matches && result.matches.content 
            ? result.matches.content.map((match) => match.text).join(' ')
            : '',
          project: result.project?.name || project,
          wiki: result.wiki?.name || request.wikiId || 'Unknown',
          pagePath: this.formatPagePath(result.path || '')
        }));
    
      } catch (error) {
        throw new Error(`Failed to search wiki: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • Zod schema for search_wiki input validation. Defines fields: organization (optional string), project (optional string), searchText (required string), and wikiId (optional string).
    export const WikiSearchRequestSchema = z.object({
      organization: z.string().min(1).optional(),
      project: z.string().min(1).optional(),
      searchText: z.string().min(1),
      wikiId: z.string().optional(),
    });
  • WikiSearchResult TypeScript interface defining the output shape: title, url, content, project, wiki, and pagePath.
    export interface WikiSearchResult {
      title: string;
      url: string;
      content: string;
      project: string;
      wiki: string;
      pagePath: string;
    }
  • src/server.ts:31-55 (registration)
    Registration of the search_wiki tool in the ListToolsRequestSchema handler, including its name, description, and inputSchema.
      name: 'search_wiki',
      description: 'Search across wiki content using Azure DevOps Search API',
      inputSchema: {
        type: 'object',
        properties: {
          organization: {
            type: 'string',
            description: 'Azure DevOps organization name'
          },
          project: {
            type: 'string',
            description: 'Project name'
          },
          searchText: {
            type: 'string',
            description: 'Search query string'
          },
          wikiId: {
            type: 'string',
            description: 'Optional specific wiki identifier'
          }
        },
        required: ['searchText']
      }
    },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states that the tool searches wiki content using an external API, but does not mention pagination, rate limits, authentication requirements, or return format. This is minimal transparency for a search operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no wasted words. It is front-loaded with the action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 4 parameters and no output schema. The description does not explain return values, pagination, or result structure. For a search tool, users need to know what the response contains. The description is incomplete for successful invocation and interpretation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema coverage is 100%, so all parameters are described in the schema. The tool description adds no additional meaning beyond the schema descriptions. Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Search' and resource 'wiki content', and distinguishes from sibling tools like list_wiki and wiki_get_page which focus on listing or retrieving pages rather than content search. The mention of Azure DevOps Search API adds context but is not essential.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus siblings (e.g., when to use search vs list_wiki), nor any conditions or prerequisites. The description only implies usage for searching, with no explicit when-to-use or when-not-to-use information.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/uright/azure-devops-wiki-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server