Introduction

Deemwar MCP turns your REST API, your API docs and your users’ login into three things:

• a hosted MCP endpoint at https://<name>-mcp.deemwar.com/mcp, which works in Claude (web, desktop, mobile), ChatGPT, Claude Code, Codex, Cursor and VS Code;
• a branded CLI with an agent skill and a Claude Code plugin;
• a chat widget for your site.

Your users sign in with your login, act within their role, and their tokens never reach the AI.

Invite-only

Publisher sign-up is by invitation for now. To request access, use the request form (work email required). Once approved, sign in at mcpconsole.deemwar.com/signin with your work email; we email you a one-time sign-in link. End users of a published endpoint need no invite: see Connect an AI app.

Concepts

Publisher	You: the company that owns the API. You set up a project in the console at mcpconsole.deemwar.com.
Project	One API published as one endpoint. Each project gets its own host, like acme-mcp.deemwar.com.
Operation	One API call from your OpenAPI spec. Operations are grouped (at most 15 groups) and can be enabled, renamed, or marked read-only, destructive or needs-confirmation.
End user	One of your users who connects an AI app, the CLI or the widget and signs in with your login.
Draft and version	You edit a draft. Approving publishes it as a new version; the endpoint, CLI and widget all serve the latest approved version.

Where to go next

• Publishing an API? Start with Getting started.
• Connecting an AI app to a product that uses Deemwar MCP? Go to Connect an AI app.
• Automating the console? See the Control plane API.