Connect AI tools: overview
Wingman plugs into the AI tools you already use. One hosted MCP endpoint, one browser sign-in, and Claude Code, Codex, Gemini CLI, or any MCP client can search Voyager knowledge, manage projects, and run Axelera-aware skills.
Wingman exposes its tools over the Model Context Protocol (MCP) at one hosted endpoint: https://mcp.wingman.axelera.ai/mcp. Your AI CLI or IDE agent registers that URL once. On the first tool call it opens your browser, you approve the sign-in with your existing Wingman session, and the connection stays authorized. That is the whole setup — no Docker, no config file editing, no shared tokens.
Connect AI tools in one click
The fastest path is the Connect AI tools button on the Wingman Home account card in the desktop app. Click it once and Wingman configures every AI CLI installed on your machine — Claude Code, Codex, Gemini — to use the hosted endpoint. Each tool then authenticates with its own native MCP OAuth flow; Wingman never hands your credentials to the CLI. The Local AI tools panel on the same screen shows which CLIs are installed, and any missing tool shows a ready-to-copy install command.
Choose your setup path
- Launch AI CLIs with Wingman: Start Claude Code, Codex CLI, or Gemini CLI from inside the desktop app with the MCP connection pre-wired. The one-click way in.
- Connect any MCP client: Cursor, Cline, Windsurf, Kiro, Augment, or anything else that speaks MCP. Copy the URL, add it as an HTTP server, approve the sign-in.
- Run Wingman skills: Sixteen packaged Axelera skills — launch, deploy, benchmark, debug, model zoo — that turn one prompt into an end-to-end result.
- Install the plugins: Generated plugin bundles for Claude Code, Codex, and Gemini that install the MCP config and the skill packs together. The bundles are coming soon; today, connect through hosted MCP.
- Zendesk triage mode: The third startup mode: Claude Code connected to your Zendesk instance for AI-assisted support triage.
- MCP tools reference: Every tool Wingman exposes to connected clients — names, arguments, access levels, and where each one is available.
| You use | Read this page | What you get |
|---|---|---|
| Claude Code, Codex CLI, or Gemini CLI | Launch AI CLIs with Wingman | 16 hosted MCP tools, launched from the desktop app with setup handled for you. |
| Cursor, Cline, Windsurf, Kiro, Augment, or another MCP client | Connect any MCP client & manage servers | The same 16 tools via manual HTTP setup, on the same hosted endpoint. |
| A CLI and you want one-shot hardware workflows | Run Wingman skills | Packaged skills like wingman-launch and wingman-deploy for end-to-end results. |
| A CLI and you want skills installed permanently | Wingman plugins for Claude Code, Codex & Gemini | Version-matched plugin bundles with MCP config and all 19 skills. The bundles are coming soon; today, connect through hosted MCP. |
| Zendesk for customer support | Zendesk support triage mode | Claude Code wired to your Zendesk instance with ticket and Help Center tools. |
| Anything, and want the exact tool list | Wingman MCP tools reference | The complete tool catalog with arguments and access levels. |
How the connection is secured
Security in one paragraph: the hosted endpoint uses the standard MCP authorization flow (authorization code with PKCE). There are no shared bearer tokens, no static authorization headers, and nothing secret to paste into a config file. Access rides on your Wingman account — sign out of Wingman and the CLI connections lose access too. If your assistant cannot see Wingman tools, confirm the hosted MCP server is registered in Claude, Codex, or Gemini, then complete the browser authorization prompt.