WS.Eng MCP Server
The MCP server for the WS.Eng CLI and Data API. Exposes cross-cutting engineering tools, prompts, and resources.
Version: 1.0.0
Connect to WS.Eng MCP Server
Local (CLI)
Add the following to your ~/.cursor/mcp.json file:
{
"mcpServers": {
"ws-eng-mcp-server": {
"command": "wseng",
"args": [
"mcp"
]
}
}
}
Remote (HTTP)
Add the following to your ~/.cursor/mcp.json file:
{
"mcpServers": {
"ws-eng-mcp-server": {
"type": "http",
"url": "https://pr761.cli.wseng.ai/mcp",
"headers": {
"Authorization": "Bearer <API_KEY>"
}
}
}
}
Local (CLI)
Add the following to your VS Code settings.json:
{
"mcp.servers": {
"ws-eng-mcp-server": {
"type": "stdio",
"command": "wseng",
"args": [
"mcp"
]
}
}
}
Remote (HTTP)
Add the following to your VS Code settings.json:
{
"mcp.servers": {
"ws-eng-mcp-server": {
"type": "http",
"url": "https://pr761.cli.wseng.ai/mcp",
"headers": {
"Authorization": "Bearer <API_KEY>"
}
}
}
}
Local (CLI)
Run the following command:
claude mcp add --transport stdio ws-eng-mcp-server -- wseng mcp
Remote (HTTP)
Run the following command:
claude mcp add --transport http ws-eng-mcp-server https://pr761.cli.wseng.ai/mcp --header "Authorization: Bearer <API_KEY>"
In ChatGPT, go to Settings → Connectors and add the MCP server URL:
https://pr761.cli.wseng.ai/mcp
Tools
The server exposes the following MCP tools:
| Tool | Description |
|---|---|
wseng_get_data_api_metadata |
Get Data API documentation with all available endpoints and their descriptions. The Data API exposes data about the engineers, repositories, products and tickets from our engineering organization. |
wseng_query_data_api |
Query a specific Data API endpoint. Use wseng_get_data_api_metadata first to discover available endpoints. |
wseng_review_work |
Review the work done for a ticket. |
wseng_get_document |
Get the content of a shared document. This includes documents of several types: - Context packs are documents that are scoped to a specific product or subsystem of a product and essentially summarize the functionality, main decisions, background context and so on. - Second brains or brain lifts are documents that encapsulate our principles, best practices, guidelines and approaches. - Quality bars are low-level rules that enforce specific practices within our code. - Playbooks are step-by-step guidelines on how to perform specific types of work. |