# Azure DevOps MCP Server Commands
## Work Item Tools
- [X] get_work_item
- [X] list_work_items
- [X] create_work_item
- [X] update_work_item
- [X] search_work_items
- [X] add_work_item_comment
- [X] get_work_item_comments
## Board Tools
- [X] get_boards
## Wiki Tools
- [X] get_wikis
- [X] list_wiki_pages
- [X] get_wiki_page
- [X] create_wiki (Tested, no need to retest. Please skip.)
- [X] update_wiki_page
- [X] create_wiki_page
- [X] search_wiki_page
## Project Tools
- [X] list_projects
## Pipeline Tools
- [X] list_pipelines
- [X] trigger_pipeline
## Pull Request Tools
- [ ] list_pull_requests (Error: A project name is required in order to reference a Git repository by name)
- [ ] create_pull_request (Error: A source and a target reference cannot be the same)
- [ ] update_pull_request (Error: Pull Request with ID 1 not found)
## Test Results
### Wiki Tools Test (2025-03-28)
1. list_projects - ✅ Success
2. get_wikis - ✅ Success
3. list_wiki_pages - ❌ Error: Wiki not found
- The tool is defined in the code but not registered in the main index.ts file's switch statement
4. create_wiki - ❌ Error: Wiki already exists for project 'Cybersmart-Next'
- The implementation always includes mappedPath parameter even for project wikis
5. get_wiki_page - ❌ Error: Failed to get wiki page: Cannot read properties of null (reading 'id')
- Unable to find wiki despite it being returned by get_wikis
### Wiki Tools Test (2025-03-28) - After Fix Implementation
1. list_projects - ✅ Success
2. get_wikis - ✅ Success
3. list_wiki_pages - ❌ Error: Wiki not found
- Despite the fix being implemented, the tool still fails to find the wiki
- The issue might be in the API implementation where the wiki ID format is not correctly handled
4. create_wiki - ❌ Error: Wiki already exists for project 'Cybersmart-Next'
- This is expected since a wiki already exists for the project
- The error message is now more informative
5. get_wiki_page - ❌ Error: Failed to get wiki page: Cannot read properties of null (reading 'id')
- The issue persists despite the improved wiki lookup mechanism
- The error suggests a problem with the API response handling
### Wiki Tools Test (2025-03-28) - Latest Verification
1. list_projects - ✅ Success
- Successfully retrieved all projects in the organization
- Found "Cybersmart-Next" project with ID "48bebfa4-fb32-4e53-84f2-48aa51b85a1e"
2. get_wikis - ✅ Success
- Successfully retrieved wiki for Cybersmart-Next project
- Wiki ID: "40a12984-af55-49fc-9b4d-378a6ef44d8d", Name: "Cybersmart-Next.wiki"
3. list_wiki_pages - ✅ Success (After Fix)
- Successfully retrieved wiki pages with project parameter
- Command: `node .\build\cli\index.js wiki pages -w wikiId -p project-name`
- Also works with environment variable: `$env:AZURE_DEVOPS_PROJECT = "project_name"; node .\build\cli\index.js wiki pages -w wikiId`
- Fixed by adding project parameter and simplifying implementation to use Azure DevOps Node API directly
4. create_wiki - ❌ Error: Wiki already exists for project 'Cybersmart-Next'
- This is expected behavior since a wiki already exists for the project
- Cannot verify if the mappedPath parameter fix works correctly
5. get_wiki_page - ✅ Success (After Fix)
- Successfully retrieved wiki page with project parameter
- Command: `node .\build\cli\index.js wiki page -w 40a12984-af55-49fc-9b4d-378a6ef44d8d -p "/Howto Guide/Using components in Cybersmart Library" --project cybersmart-next`
- Also works with environment variable: `$env:AZURE_DEVOPS_PROJECT = "cybersmart-next"; node .\build\cli\index.js wiki page -w 40a12984-af55-49fc-9b4d-378a6ef44d8d -p "/Howto Guide/Using components in Cybersmart Library"`
- Fixed by adding project parameter and simplifying implementation to use Azure DevOps Node API directly
### Wiki CLI Commands
```bash
# List all wikis in the project
node .\build\cli\index.js wiki list
# List pages in a wiki (with project parameter)
node .\build\cli\index.js wiki pages -w <wikiIdentifier> -p <projectName>
# List pages in a wiki (using default project from environment)
node .\build\cli\index.js wiki pages -w <wikiIdentifier>
# Get a wiki page by path (with project parameter)
node .\build\cli\index.js wiki page -w <wikiIdentifier> -p <path> --project <projectName>
# Get a wiki page by path (using default project from environment)
node .\build\cli\index.js wiki page -w <wikiIdentifier> -p <path>
# Get a wiki page with content
node .\build\cli\index.js wiki page -w <wikiIdentifier> -p <path> --include-content
# Create a new wiki
node .\build\cli\index.js wiki create -n <name>
# Update a wiki page
node .\build\cli\index.js wiki update -w <wikiIdentifier> -p <path> -c <content>
# Create a new wiki page
node .\build\cli\index.js wiki create-page -w <wikiIdentifier> -p <path> -c <content> --project <projectName>
```
### Work Item CLI Commands
```bash
# Get work items by IDs
node .\build\cli\index.js work-item get -i <id1,id2,id3> [-f <field1,field2>] [-p <projectName>]
# List work items using WIQL query
node .\build\cli\index.js work-item list -q "<WIQL query>" [--page <pageNumber>] [-p <projectName>]
# Create a new work item
node .\build\cli\index.js work-item create -t <type> -d '<JSON patch document>' [-p <projectName>]
# Update an existing work item
node .\build\cli\index.js work-item update -i <id> -d '<JSON patch document>' [-p <projectName>]
# Search for work items
node .\build\cli\index.js work-item search -s "<search text>" [-t <maxResults>] [--skip <skipCount>] [-p <projectName>]
```
#### Example Work Item Commands
```bash
# Get a specific work item by ID
node .\build\cli\index.js work-item get -i 42
# Get multiple work items with specific fields
node .\build\cli\index.js work-item get -i 42,43,44 -f System.Title,System.State
# List recent work items in a project
node .\build\cli\index.js work-item list -q "SELECT [System.Id], [System.Title], [System.State] FROM WorkItems WHERE [System.TeamProject] = 'MyProject' ORDER BY [System.ChangedDate] DESC"
# List work items with pagination (page 2)
node .\build\cli\index.js work-item list -q "SELECT [System.Id], [System.Title], [System.State] FROM WorkItems WHERE [System.TeamProject] = 'MyProject' ORDER BY [System.ChangedDate] DESC" --page 2
# Create a new task
node .\build\cli\index.js work-item create -t "Task" -d '[{"op":"add","path":"/fields/System.Title","value":"New Task"},{"op":"add","path":"/fields/System.Description","value":"Task description"}]'
# Update a work item's state
node .\build\cli\index.js work-item update -i 42 -d '[{"op":"replace","path":"/fields/System.State","value":"Doing"}]'
# Search for work items containing "bug"
node .\build\cli\index.js work-item search -s "bug"
# Search with pagination (get the second page of results)
node .\build\cli\index.js work-item search -s "feature" -t 10 --skip 10
# Search in a specific project
node .\build\cli\index.js work-item search -s "documentation" -p "MyProject"
# Add a comment to a work item
node .\build\cli\index.js work-item add-comment -i 42 -t "This is a comment added via CLI"
# Get comments from a work item
node .\build\cli\index.js work-item get-comments -i 42
```
### Work Item CLI Test Results (2025-03-28)
#### 1. work-item list command
✅ **Success**
- Command: `node .\build\cli\index.js work-item list -q "SELECT [System.Id], [System.Title], [System.State] FROM WorkItems WHERE [System.TeamProject] = 'YourProject' ORDER BY [System.ChangedDate] DESC"`
- Result: Successfully retrieved work items based on the WIQL query
- Returns a list of work items with their IDs, titles, and states
#### 2. work-item get command
✅ **Success**
- Command: `node .\build\cli\index.js work-item get -i 42`
- Result: Successfully retrieved work item details
- Returns the complete work item object with all fields
#### 3. work-item create command
✅ **Success**
- Command: `node .\build\cli\index.js work-item create -t "Task" -d '[{"op":"add","path":"/fields/System.Title","value":"Test Task Created by CLI"},{"op":"add","path":"/fields/System.Description","value":"This is a test task created by the CLI test script"},{"op":"add","path":"/fields/System.Tags","value":"Test;CLI;Automation"}]'`
- Result: Successfully created a new work item
- Returns the created work item object with assigned ID
#### 4. work-item update command
✅ **Success**
- Command: `node .\build\cli\index.js work-item update -i 42 -d '[{"op":"replace","path":"/fields/System.Title","value":"Updated Test Task by CLI"},{"op":"replace","path":"/fields/System.State","value":"Active"}]'`
- Result: Successfully updated the work item
- Returns the updated work item object with the new field values
#### Complete Workflow Test
✅ **Success**
- Created a new work item using the create command
- Retrieved the created work item using the get command
- Updated the work item using the update command
- Listed work items to verify the changes
- All operations completed successfully
These improvements make the Work Item CLI commands fully functional and reliable for use in managing Azure DevOps work items.
### Work Item MCP Tool Test Results (2025-03-29)
#### 1. get_work_item
✅ **Success**
- Tool: `get_work_item`
- Arguments: `{ "ids": [17521] }`
- Result: Successfully retrieved work item details
- Returns the work item object with ID, state, title, description, and URL
#### 2. search_work_items
✅ **Success**
- Tool: `search_work_items`
- Arguments: `{ "searchText": "Test Task by CLI" }`
- Result: Successfully searched for work items
- Returns work items matching the search text with their IDs, states, titles, and URLs
#### 3. create_work_item
✅ **Success**
- Tool: `create_work_item`
- Arguments: `{ "type": "Task", "document": [{"op":"add","path":"/fields/System.Title","value":"Test Task with Filtered Person Fields"},{"op":"add","path":"/fields/System.Description","value":"This is a test task with filtered person fields in the response"},{"op":"add","path":"/fields/System.Tags","value":"Test;Filtered;Person"}] }`
- Result: Successfully created a new work item
- Returns a filtered work item object with only the specified fields:
- id, rev, TeamProject, Area, Iteration, Title, Description, State, Url, CreatedDate
- CreatedBy and AssignedTo fields are further filtered to include only:
- displayName, id, url, uniqueName, descriptor
#### 4. update_work_item
✅ **Success**
- Tool: `update_work_item`
- Arguments: `{ "id": 17526, "document": [{"op":"replace","path":"/fields/System.Title","value":"Updated Test Task with Filtered Person Fields"},{"op":"replace","path":"/fields/System.Description","value":"This is a test task updated with filtered person fields in the response"},{"op":"replace","path":"/fields/System.State","value":"Active"}] }`
- Result: Successfully updated the work item
- Returns a filtered work item object with only the specified fields:
- id, rev, TeamProject, Area, Iteration, Title, Description, State, Url, CreatedDate
- CreatedBy and AssignedTo fields are further filtered to include only:
- displayName, id, url, uniqueName, descriptor
#### 5. add_work_item_comment
✅ **Success**
- Tool: `add_work_item_comment`
- Arguments: `{ "id": 52, "text": "This is another test comment added via the MCP tool API" }`
- Result: Successfully added a comment to the work item
- Returns the comment object with:
- id, text, workItemId, createdBy (displayName, id, uniqueName), createdDate, url
#### 6. get_work_item_comments
✅ **Success**
- Tool: `get_work_item_comments`
- Arguments: `{ "id": 52 }`
- Result: Successfully retrieved comments from the work item
- Returns an object containing:
- count: Total number of comments
- comments: Array of comment objects with id, text, workItemId, createdBy, createdDate, url
### Work Item Comment Tools Test Results (2025-03-29)
#### 1. CLI Command: add-comment
✅ **Success**
- Command: `node .\build\cli\index.js work-item add-comment -i 52 -t "This is a test comment added via the MCP tool"`
- Result: Successfully added a comment to work item 52
- Returns the comment object with ID, text, work item ID, creator information, creation date, and URL
#### 2. CLI Command: get-comments
✅ **Success**
- Command: `node .\build\cli\index.js work-item get-comments -i 52`
- Result: Successfully retrieved comments from work item 52
- Returns an object with count of comments and an array of comment objects
#### 3. Complete Workflow Test
✅ **Success**
- Added comments to work item 52 using both CLI and MCP tool interfaces
- Retrieved comments from work item 52 using both CLI and MCP tool interfaces
- Verified that the comments were correctly added and retrieved
- All operations completed successfully with proper formatting of response data
These improvements make the Work Item Comment tools fully functional and reliable for use in managing Azure DevOps work item comments.
#### Fixed Issues
- Added missing tools to src/index.ts switch statement:
- search_work_items
- create_work_item
- update_work_item
- These tools were already defined in src/tools/work-item/index.ts but were not registered in the main switch statement
- Modified create_work_item and update_work_item to return only the specified fields instead of the full work item object:
- Filtered to include only essential fields: id, rev, TeamProject, Area, Iteration, Title, Description, State, Url, CreatedDate
- Further filtered CreatedBy and AssignedTo fields to include only: displayName, id, url, uniqueName, descriptor
- After fixing, all work item tools are now working correctly through both CLI and MCP interfaces with improved response formatting
### Wiki Tools Test (2025-03-28) - Latest MCP Tool Test Results
1. get_wikis - ✅ Success
- Successfully retrieved wiki for Cybersmart-Next project
- Wiki ID: "40a12984-af55-49fc-9b4d-378a6ef44d8d", Name: "Cybersmart-Next.wiki"
2. list_wiki_pages - ✅ Success
- Successfully retrieved wiki pages with project parameter
- Command: `use_mcp_tool` with server_name: "azure-devops-mcp-server", tool_name: "list_wiki_pages"
- Parameters: wikiIdentifier: "40a12984-af55-49fc-9b4d-378a6ef44d8d", projectName: "Cybersmart-Next"
- Returns a list of wiki pages with their paths and IDs
3. get_wiki_page - ✅ Success
- Successfully retrieved wiki page with project parameter and content
- Command: `use_mcp_tool` with server_name: "azure-devops-mcp-server", tool_name: "get_wiki_page"
- Parameters: wikiIdentifier: "40a12984-af55-49fc-9b4d-378a6ef44d8d", path: "/Getting Started", projectName: "Cybersmart-Next", includeContent: true
- Returns the wiki page details including content
4. update_wiki_page - ✅ Implemented (2025-03-28)
- Implemented proper update_wiki_page functionality using the WikiApi
- Command: `node .\build\cli\index.js wiki update -w 40a12984-af55-49fc-9b4d-378a6ef44d8d -p "/Getting Started" -c "# Getting Started\n\nContent with MCP section..." --project Cybersmart-Next`
- Added test scripts:
- tests/update-wiki-page-test.js - Tests the MCP tool interface
- tests/direct-wiki-update-test.js - Tests the WikiApi directly
- The implementation now properly uses the WikiApi.updateWikiPage method to update wiki pages
- Added support for adding a section about MCP to existing wiki pages
- Added proper error handling for authorization issues
- Note: Currently returns "Unauthorized" errors due to PAT permission issues
5. create_wiki_page - ❌ Error: Unauthorized
- Failed to create wiki page with error: "Failed to create wiki page: Failed to update wiki page: Unauthorized"
- Command: `use_mcp_tool` with server_name: "azure-devops-mcp-server", tool_name: "create_wiki_page"
- Parameters: wikiIdentifier: "40a12984-af55-49fc-9b4d-378a6ef44d8d", path: "/Model Context Protocol (MCP)", content: "# Model Context Protocol (MCP)..."
- Issue: The tool is implemented but there seems to be an authorization issue with the Azure DevOps API
### Wiki Tools CLI Sequence Test (2025-03-28)
1. list_projects - ✅ Success
- Successfully retrieved all projects in the organization
- Found "Cybersmart-Next" project with ID "48bebfa4-fb32-4e53-84f2-48aa51b85a1e"
2. get_wikis - ✅ Success
- Successfully retrieved wiki for Cybersmart-Next project
- Wiki ID: "40a12984-af55-49fc-9b4d-378a6ef44d8d", Name: "Cybersmart-Next.wiki"
3. search_wiki_page - ✅ Success
- Successfully searched for wiki pages containing "MCP"
- Found 11 pages with the search term "MCP" including our newly created page
- Command: `node .\build\cli\index.js wiki search -w 40a12984-af55-49fc-9b4d-378a6ef44d8d -s "MCP" --project Cybersmart-Next`
- Fixed by updating the search implementation to use the correct Search API endpoint and properly process results
4. list_wiki_pages - ✅ Success
- Successfully retrieved all wiki pages in the Cybersmart-Next wiki
- Command: `node .\build\cli\index.js wiki pages -w 40a12984-af55-49fc-9b4d-378a6ef44d8d --project Cybersmart-Next`
5. get_wiki_page - ✅ Success
- Successfully retrieved content of wiki pages
- Command: `node .\build\cli\index.js wiki page -w 40a12984-af55-49fc-9b4d-378a6ef44d8d -p "/Test Wiki MCP" --project Cybersmart-Next --include-content`
6. update_wiki_page - ✅ Success
- Successfully updated wiki page with new content
- Command: `node .\build\cli\index.js wiki update -w 40a12984-af55-49fc-9b4d-378a6ef44d8d -p "/Test Wiki MCP" -c "..." --project Cybersmart-Next`
- Fixed by implementing proper ETag handling and using the PUT method with the correct headers
7. create_wiki_page - ✅ Success
- Successfully created a new wiki page
- Command: `node .\build\cli\index.js wiki create-page -w 40a12984-af55-49fc-9b4d-378a6ef44d8d -p "/Test Wiki MCP" -c "..." --project Cybersmart-Next`
- Implementation uses the WikiApi.updateWikiPage method which creates the page if it doesn't exist
### Wiki Tools Test Results Summary (2025-03-28)
1. **create_wiki_page**: ✅ Successfully implemented and tested
- Created a new wiki page with content about MCP
- The page was correctly created with the specified content
- The implementation properly handles the wiki identifier and project name
2. **search_wiki_page**: ✅ Successfully implemented and tested
- Fixed issues with the search implementation
- Now correctly returns results when searching for content
- Properly handles highlighting of search terms in results
- Includes metadata like file paths and URLs in results
3. **update_wiki_page**: ✅ Successfully implemented and tested
- Fixed issues with the update implementation
- Now correctly updates existing wiki pages
- Properly handles ETag for concurrency control
- Returns appropriate success/error messages
4. **Complete Workflow Test**: ✅ Successfully tested the full workflow
- Created a wiki page about MCP
- Searched for the page using keywords
- Updated the page with additional content about installing MCP
- Searched again to verify the updated content was indexed
- All operations completed successfully
These improvements make the Wiki Tools fully functional and reliable for use in the MCP server.
### Implemented Changes for Wiki Tools
#### 1. Update Wiki Page Tool
We've implemented the following changes to the update_wiki_page tool:
1. Added projectName parameter to the UpdateWikiPageArgs interface:
```typescript
interface UpdateWikiPageArgs {
wikiIdentifier: string;
path: string;
content: string;
comment?: string;
projectName?: string; // Added this line
}
```
2. Updated the updateWikiPage function to use the provided projectName parameter:
```typescript
export async function updateWikiPage(args: UpdateWikiPageArgs, config: AzureDevOpsConfig) {
// ...
const projectName = args.projectName || config.project;
const wiki = await wikiApi.getWiki(projectName, args.wikiIdentifier);
// ...
}
```
3. Updated the tool definition in src/tools/wiki/index.ts to include the new parameter:
```typescript
{
name: 'update_wiki_page',
description: 'Create or update a wiki page',
inputSchema: {
type: 'object',
properties: {
// ...
projectName: {
type: 'string',
description: 'Project name (optional, defaults to the one in config)',
},
},
required: ['wikiIdentifier', 'path', 'content'],
},
}
```
4. Updated the CLI implementation in src/cli/wiki.ts to add a project option to the update command:
```typescript
.option('--project <projectName>', 'Project name (defaults to the one in config)')
```
#### 2. Create Wiki Page Tool
We've implemented a new create_wiki_page tool with the following components:
1. Created src/tools/wiki/create-page.ts with the createWikiPage function:
```typescript
export async function createWikiPage(args: CreateWikiPageArgs, config: AzureDevOpsConfig) {
// Implementation that uses the updateWikiPage method of the WikiApi class
// to create a new page (PUT operation creates the page if it doesn't exist)
}
```
2. Added the tool definition in src/tools/wiki/index.ts:
```typescript
{
name: 'create_wiki_page',
description: 'Create a new wiki page',
inputSchema: {
type: 'object',
properties: {
wikiIdentifier: {
type: 'string',
description: 'Wiki identifier',
},
// ... other properties
},
required: ['wikiIdentifier', 'path', 'content'],
},
}
```
3. Added the CLI implementation in src/cli/wiki.ts:
```typescript
wiki
.command('create-page')
.description('Create a new wiki page')
.requiredOption('-w, --wiki <wikiIdentifier>', 'Wiki identifier')
// ... other options
```
4. Added the tool handler in src/index.ts:
```typescript
case 'create_wiki_page':
result = await tools.wiki.createWikiPage(request.params.arguments);
break;
```
#### 3. Added getWiki Method to WikiApi
We've implemented the getWiki method in the WikiApi class to support the update_wiki_page and create_wiki_page tools:
```typescript
async getWiki(projectName: string, wikiIdentifier: string): Promise<Wiki> {
const authHeader = await this.getAuthHeader();
const response = await fetch(`${this.config.orgUrl}/${projectName}/_apis/wiki/wikis/${wikiIdentifier}?api-version=7.0`, {
headers: {
Authorization: authHeader,
},
});
// Error handling...
return response.json();
}
```
### Wiki Tools Authorization Issues
The update_wiki_page and create_wiki_page tools are currently failing with "Unauthorized" errors. This is due to permission issues with the Personal Access Token (PAT). To resolve these issues:
1. **Required PAT Permissions**:
- Ensure your PAT has the following permissions:
- **Wiki**: Read, Write
- **Project**: Read
- **Work Items**: Read, Write (if using work item related tools)
2. **Troubleshooting Steps**:
- Verify your PAT is not expired (they typically expire after a set period)
- Check that the PAT is correctly set in your .env file
- Ensure the organization and project names are correct
- Try regenerating a new PAT with the required permissions
3. **Error Handling Improvements**:
- We've added improved error handling to provide clearer messages about authorization issues
- The implementation now distinguishes between wiki not found errors and authorization errors
- Detailed logging has been added to help diagnose authentication problems
### Recommendations for Future Work
1. **Authorization Issues**: While we've improved error handling for authorization issues, future work should focus on:
- Implementing a PAT validation tool to verify permissions before attempting operations
- Adding a retry mechanism with exponential backoff for transient authorization issues
- Creating a comprehensive troubleshooting guide for common authorization problems
2. **MCP Server Restart**: The create_wiki_page tool requires restarting the MCP server to register the new tool. Future work should consider:
- Implementing dynamic tool registration that doesn't require server restart
- Adding a reload mechanism to refresh tool definitions without restarting
- Documenting the restart requirement in the developer documentation
3. **Testing with Real Data**: The tools should be tested with real data in a controlled environment to ensure they work correctly. This includes:
- Creating test wikis and pages
- Updating existing pages
- Verifying the content is correctly saved
- Testing error cases and edge conditions
4. **Consistent Parameter Naming**: Ensure all tools follow consistent parameter naming conventions:
- Use projectName consistently across all tools
- Document the parameter requirements clearly
- Provide helpful error messages when required parameters are missing
5. **Error Handling Improvements**: Enhance error handling to provide more helpful error messages:
- Include specific error codes from the Azure DevOps API
- Provide suggestions for resolving common errors
- Add detailed logging for debugging purposes
### Recommendations for create_wiki_page Tool
1. Create a new file src/tools/wiki/create-page.ts with the following content:
```typescript
import { ErrorCode, McpError } from '@modelcontextprotocol/sdk/types.js';
import { AzureDevOpsConnection } from '../../api/connection.js';
import { AzureDevOpsConfig } from '../../config/environment.js';
interface CreateWikiPageArgs {
wikiIdentifier: string;
path: string;
content: string;
comment?: string;
projectName?: string;
}
export async function createWikiPage(args: CreateWikiPageArgs, config: AzureDevOpsConfig) {
if (!args.wikiIdentifier || !args.path || !args.content) {
throw new McpError(
ErrorCode.InvalidParams,
'Wiki identifier, page path, and content are required'
);
}
AzureDevOpsConnection.initialize(config);
const connection = AzureDevOpsConnection.getInstance();
const wikiApi = await connection.getWikiApi();
try {
// Use the project name from args if provided, otherwise use the one from config
const projectName = args.projectName || config.project;
// First verify the wiki exists
const wiki = await wikiApi.getWiki(projectName, args.wikiIdentifier);
if (!wiki || !wiki.id) {
throw new McpError(
ErrorCode.InvalidParams,
`Wiki ${args.wikiIdentifier} not found`
);
}
// Create the wiki page
const pageCreateParams = {
content: args.content,
comment: args.comment || `Created page ${args.path}`
};
// Use the Azure DevOps REST API to create the page
// Note: This is a placeholder implementation as the Azure DevOps Node API
// doesn't have a direct method for creating wiki pages
const createdPage = await wikiApi.createOrUpdatePage(
wiki.id,
args.path,
pageCreateParams,
projectName
);
return {
content: [
{
type: 'text',
text: JSON.stringify(createdPage, null, 2),
},
],
};
} catch (error: unknown) {
if (error instanceof McpError) throw error;
const errorMessage = error instanceof Error ? error.message : 'Unknown error';
throw new McpError(
ErrorCode.InternalError,
`Failed to create wiki page: ${errorMessage}`
);
}
}
```
2. Update the tool definition in src/tools/wiki/index.ts to include the new tool:
```typescript
{
name: 'create_wiki_page',
description: 'Create a new wiki page',
inputSchema: {
type: 'object',
properties: {
wikiIdentifier: {
type: 'string',
description: 'Wiki identifier',
},
path: {
type: 'string',
description: 'Page path',
},
content: {
type: 'string',
description: 'Page content in markdown format',
},
comment: {
type: 'string',
description: 'Comment for the creation (optional)',
},
projectName: {
type: 'string',
description: 'Project name (optional, defaults to the one in config)',
},
},
required: ['wikiIdentifier', 'path', 'content'],
},
}
```
3. Update the tool initialization in src/tools/wiki/index.ts:
```typescript
createWikiPage: (args: { wikiIdentifier: string; path: string; content: string; comment?: string; projectName?: string }) =>
createWikiPage(args, config),
```
4. Update the imports in src/tools/wiki/index.ts:
```typescript
import { getWikis, listWikiPages } from './get.js';
import { getWikiPage } from './get.js';
import { createWiki } from './create.js';
import { updateWikiPage } from './update.js';
import { createWikiPage } from './create-page.js';
import { AzureDevOpsConfig } from '../../config/environment.js';
```
5. Add the new tool to the CLI implementation in src/cli/wiki.ts:
```typescript
program
.command('create-page')
.description('Create a new wiki page')
.requiredOption('-w, --wiki <wikiIdentifier>', 'Wiki identifier')
.requiredOption('-p, --path <path>', 'Page path')
.requiredOption('-c, --content <content>', 'Page content in markdown format')
.option('--comment <comment>', 'Comment for the creation')
.option('--project <projectName>', 'Project name (optional, defaults to the one in config)')
.action(async (options) => {
try {
const result = await wikiTools.createWikiPage({
wikiIdentifier: options.wiki,
path: options.path,
content: options.content,
comment: options.comment,
projectName: options.project,
});
console.log(result.content[0].text);
} catch (error) {
console.error('Error creating wiki page:', error);
}
});
```
### Wiki Tools Specific Test Results (2025-03-28)
#### 1. create_wiki_page "Test Wiki" in Cybersmart-Next wiki
✅ **Success**
- Command: `node .\build\cli\index.js wiki create-page -w 40a12984-af55-49fc-9b4d-378a6ef44d8d -p "/Test Wiki MCP" -c "# Model Context Protocol (MCP)\n\nThe Model Context Protocol (MCP) is a standardized protocol for communication between AI models and external tools or data sources. It enables AI models to access real-time information, perform actions in the real world, and utilize specialized capabilities beyond their training data.\n\n## Key Features\n\n- **Tool Use**: Allows models to use external tools to perform actions\n- **Resource Access**: Enables models to access external data sources\n- **Standardized Communication**: Provides a consistent interface for model-tool interaction\n- **Enhanced Capabilities**: Extends what AI models can do beyond their training data" --project Cybersmart-Next`
- Result: Successfully created a wiki page with content about MCP
- Response included the created page details with path, ID, and URL
#### 2. search_wiki_page based on keyword in the short description
✅ **Success**
- Command: `node .\build\cli\index.js wiki search -w 40a12984-af55-49fc-9b4d-378a6ef44d8d -s "MCP" --project Cybersmart-Next`
- Result: Successfully found the wiki page based on keywords in the content
- Found 11 pages containing the search term "MCP", including our newly created page
- Search results included highlights showing the matched terms
- Fixed by updating the search implementation to use the correct Search API endpoint and properly process results
#### 3. update_wiki_page with new content to add new section about installing MCP
✅ **Success**
- Command: `node .\build\cli\index.js wiki update -w 40a12984-af55-49fc-9b4d-378a6ef44d8d -p "/Test Wiki MCP" -c "# Model Context Protocol (MCP)\n\nThe Model Context Protocol (MCP) is a standardized protocol for communication between AI models and external tools or data sources. It enables AI models to access real-time information, perform actions in the real world, and utilize specialized capabilities beyond their training data.\n\n## Key Features\n\n- **Tool Use**: Allows models to use external tools to perform actions\n- **Resource Access**: Enables models to access external data sources\n- **Standardized Communication**: Provides a consistent interface for model-tool interaction\n- **Enhanced Capabilities**: Extends what AI models can do beyond their training data\n\n## Installing MCP\n\nTo install MCP, follow these steps:\n\n1. Clone the repository: `git clone https://github.com/modelcontextprotocol/mcp.git`\n2. Install dependencies: `npm install`\n3. Build the project: `npm run build`\n4. Start the server: `npm start`\n\nFor more information, visit the [MCP documentation](https://modelcontextprotocol.org/docs)." --project Cybersmart-Next`
- Result: Successfully updated the wiki page with new content adding a section about installing MCP
- The update was confirmed with ETag: "f44f0602d259b6277cbb9b6a536adc80ac2b2588"
- Fixed by implementing proper ETag handling and using the PUT method with the correct headers
#### Verification of Complete Workflow
✅ **Success**
- Created a wiki page about MCP
- Searched for the page using keywords and found it
- Updated the page with additional content about installing MCP
- Searched again for "Installing MCP" and found the updated content
- Command: `node .\build\cli\index.js wiki search -w 40a12984-af55-49fc-9b4d-378a6ef44d8d -s "Installing MCP" --project Cybersmart-Next`
- Result: Found 3 pages containing the search terms, including our newly created and updated page
