Wingman MCP tools reference
Every tool the hosted Wingman MCP exposes to connected clients: 16 working tools for knowledge search, projects, documents, and diagnostics, plus 9 retired names that answer with a notice and do nothing — and the separate Zendesk-mode tools.
Access levels and arguments
All 25 tool names are offered to every connected client — Claude Code, Codex CLI, Gemini CLI, Cursor, and any other MCP client on https://mcp.wingman.axelera.ai/mcp. Access levels below mean: Read-only tools never change data; Write tools create new records; Destructive tools modify or delete existing data, so agents typically ask before running them; Retired tools read and change nothing at all, and return a plain notice instead. Optional arguments are marked with ? and defaults are shown where they matter.
| Tool | Arguments | Access | What it does |
|---|---|---|---|
health_check | none | Read-only | Check the MCP server and its dependencies. |
session_info | none | Read-only | Report active session count and server uptime. |
rag_get_available_sources | none | Read-only | List the indexed knowledge sources with their source_id values — call this before filtered searches. |
rag_search_knowledge_base | query, source_id?, match_count? (5) | Read-only | Semantic search over indexed Voyager and project knowledge. Keep queries short and focused: 2-5 keywords. |
rag_search_code_examples | query, source_id?, match_count? (5) | Read-only | Search indexed code examples. Pass a source_id from rag_get_available_sources verbatim to scope to one repo. |
create_project | title, description?, github_repo? | Write | Create a project to collect the documents for one effort. |
list_projects | none | Read-only | List your projects. |
get_project | project_id | Read-only | Fetch one project. |
update_project | project_id, title?, description?, github_repo? | Destructive | Update project fields. |
delete_project | project_id | Destructive | Delete a project. |
get_project_features | project_id | Read-only | List the features defined for a project. |
create_document | project_id, title, document_type, content?, tags?, author? | Write | Create a project document. Title it like a path — apps/pipeline.py — and it files itself into a folder. |
list_documents | project_id | Read-only | List a project’s documents. |
get_document | project_id, doc_id | Read-only | Fetch one document. |
update_document | project_id, doc_id, title?, content?, tags?, author? | Destructive | Update a document. |
delete_document | project_id, doc_id | Destructive | Delete a document. |
create_task | project_id, title, description?, assignee?, … | Retired | Creates nothing. Track work in your client’s own plan or TODO view. |
list_tasks | filter_by?, filter_value?, project_id?, … | Retired | Returns no tasks — there is no task store left to list. |
get_task | task_id | Retired | Returns no task. |
update_task | task_id, title?, status?, … | Retired | Changes nothing, including status moves. |
delete_task | task_id | Retired | Deletes nothing. |
create_version | project_id, field_name, content, … | Retired | Snapshots nothing. Document history is no longer served over MCP. |
list_versions | project_id, field_name? | Retired | Returns no history. |
get_version | project_id, field_name, version_number | Retired | Returns no snapshot. |
restore_version | project_id, field_name, version_number, … | Retired | Restores nothing and modifies no document. It used to report a success it had not achieved; it now says so plainly. |
Why the retired names still answer
No code execution tools
Support by client
Client support at a glance: every hosted tool behaves identically in every MCP client — the endpoint does not vary tools by client, and the retired names are retired everywhere. What varies is the layer on top: Claude Code and Codex also run the 16 Wingman skills (via the plugin or repo skill discovery), Gemini gets MCP tools plus GEMINI.md context with skills as reference material, and IDE clients like Cursor and Windsurf get the MCP tools plus converted rules where you have generated them. The Zendesk tools (get_tickets, get_ticket, get_ticket_comments, zendesk_search_knowledge_base, create_ticket, update_ticket, create_ticket_comment, and its own health_check) come from the separate Zendesk MCP server and exist only in Zendesk-mode sessions — see the Zendesk support triage page for arguments and setup.
| Surface | Hosted MCP tools | Wingman skills | Zendesk tools |
|---|---|---|---|
| Claude Code | All 16 working | Yes — 16 via plugin | In Zendesk mode sessions |
| Codex CLI | All 16 working | Yes — auto-discovery | No |
| Gemini CLI | All 16 working | Reference only | No |
| Cursor / Windsurf / other MCP clients | All 16 working | Converted rules where generated | No |
| Agent Dev (desktop app) | All 16 working | Yes — packaged | No |
| Hosted Chat | Knowledge and project tools via the chat backend | No | No |