Connect any MCP client & manage servers

Cursor, Cline, Windsurf, Kiro, Augment — anything that speaks MCP can use Wingman. Copy the hosted URL, add it as an HTTP server, approve one browser sign-in. Then use the Wingman MCP card in dashboard Settings to check the connection whenever something looks off.

Every MCP-compatible client connects to the same hosted endpoint. The transport is HTTP (streamable-http) — SSE transport is deprecated, so pick HTTP wherever your client asks. On the first tool call the client opens a browser and signs you in with Wingman using the standard MCP authorization flow (authorization code with PKCE). No shared secrets, no config file editing.

Endpoint

https://mcp.wingman.axelera.ai/mcp

Cursor

# In Cursor settings, add an MCP server:
#   Type: HTTP
#   URL:  https://mcp.wingman.axelera.ai/mcp
# First tool call opens a browser to sign you in with Wingman.

Generic client

# Any MCP client:
#   Transport: HTTP (streamable-http; SSE is deprecated)
#   URL:       https://mcp.wingman.axelera.ai/mcp
#   Auth:      MCP OAuth (authorization_code + PKCE) — approved in your browser on first tool call

Add Wingman to your client

  1. Copy the MCP URL from the app

    In the desktop app, open the AI Tools menu from the Wingman sidebar and choose Manual MCP setup. Pick Copy Wingman MCP URL — this copies the validated current endpoint, which matters if your deployment uses a non-default URL. The same menu offers Connect installed CLI tools to auto-configure Claude, Codex, and Gemini, Open MCP settings to review wingman.mcp configuration, and Open MCP docs for the architecture notes.

  2. Add the server in your client

    Paste the URL into your client wherever it takes an MCP server. Choose the HTTP transport. Name the server wingman so tool names read naturally in the session.

  3. Approve the sign-in

    Run any Wingman tool. The client opens your browser, you approve once with your existing Wingman session, and the connection stays authorized. If nothing happens, check that your client supports MCP OAuth — clients without it cannot use the hosted endpoint, and Wingman does not support token-pasting as a fallback.

  4. Verify with a first search

    Ask your assistant to run the Wingman knowledge search — for example search the wingman knowledge base for model compilation. A result list means the connection, sign-in, and tools all work.

The Wingman MCP card in Settings

Dashboard Settings carries a Wingman MCP group, and the Home tile of the same name opens it directly. It is the check-first view for this connection: the health of the services behind it, the exact endpoint with a copy button, and per-client setup under IDE configuration. Open it whenever a client stops seeing tools, before you touch any client config.

In the Wingman MCP cardWhat it tells you
Service chipsLive health for the API, MCP, chat, and database services. Red here means no client will connect, whatever the client config says.
MCP endpointThe exact URL your clients should use, with a copy button — the one to trust if your deployment uses a non-default address.
IDE configurationReady-made setup for Claude Code, Codex, and Gemini, expanded in place.

Hosted versus local MCP