Skip to content

Invite-only · Works in Claude, ChatGPT, Codex, Cursor

Your API, live inside every AI app. Signed in as your users.

Turn your REST API, your docs and your existing login into a hosted MCP server at<name>-mcp.deemwar.com/mcp, plus a branded CLI, agent skill, Claude plugin and chat widget. All from one spec.

Request access Read the docs
1 · your spec
openapi: 3.1.0
info.title: Acme Tasks
GET /projects
POST /tasks
DELETE /tasks/{id}
✓ 11 operations · 3 groups
2 · your endpoint
MCP endpoint
https://acme-mcp.deemwar.com/mcp
● sign-in: your login
● roles: viewer · member · admin
● validated live
3 · Claude, signed in as bob (member)

Add a task "Ship v2 docs" to Website.

tool call_write_operation
op createTask → 201

Done. "Ship v2 docs" is in Website as task #42.

Illustration using the sample "Acme Tasks" API from our end-to-end demo.

Works in the AI apps your users already have

  • Claude
  • Claude Desktop
  • Claude mobile
  • ChatGPT
  • Claude Code
  • Codex
  • Cursor
  • VS Code

Product names belong to their owners and are listed for compatibility only. How to connect each one.

How it works

Four steps in the console. No SDK, no spec rewriting.

The console walks you through it and resumes where you stopped. Nothing goes out until a test user has called your API live.

  1. 01

    Point at your API

    Paste a base URL or an OpenAPI/Swagger URL, or upload the spec. We probe the usual paths, parse the operations and group them into tools you review.

  2. 02

    Connect your login

    Choose how your users sign in: redirect, username + password relay, token exchange or SSO (Google, Microsoft, Firebase, any OIDC). Map a role claim to the operations each role may call.

  3. 03

    Add your docs

    Your OpenAPI operations are always included; add guide URLs or files. They become a cited wiki that agents query with ask_docs.

  4. 04

    Validate and publish

    Sign in as a test user and we call one operation per group, live. Approve, and you get the endpoint, the CLI, the plugin and the widget tag.

The full walkthrough →

What you get

One approved definition. Every surface your users work in.

The endpoint, the CLI and the widget come from the same tools, the same login and the same role map. Change it once and every output follows.

Hosted MCP server

One URL your users paste into their AI app

Each project gets its own host. Clients sign in by URL alone: OAuth 2.1 with PKCE, protected-resource metadata and client registration are built in.

  • Streamable HTTP on MCP 2026-07-28, also accepting 2025-11-25 and 2025-06-18 clients
  • Search-first: agents see five tools, not hundreds of endpoints
  • No local server for your users to install
$ claude mcp add --transport http acme \
    https://acme-mcp.deemwar.com/mcp
# /mcp → sign in on Acme's own login

tools/list
  overview              what this API can do
  search_tools          find operations by intent
  call_read_operation   run a read, with pagination
  call_write_operation  run a change, with confirmation
  ask_docs              cited passages from your docs

CLI, agent skill and Claude plugin

A branded CLI that agents already know how to use

One binary named after your product for macOS, Linux and Windows, with a generated SKILL.md. Claude Code users can install a plugin that adds the endpoint and the skill in one step.

  • login, search and call, with the same login and roles as the endpoint
  • Checksum-verified install to ~/.local/bin, no sudo
  • Skill for Claude Code and Codex
$ curl -fsSL https://acme-mcp.deemwar.com/cli/install.sh | sh
$ acme login
$ acme search "delete a task"
$ acme call deleteTask --json '{"id":"42"}'
needs confirmation → confirm_token

Chat widget

One script tag, and your app has an agent

End users sign in through the widget with your login, and the agent calls your API for them, within their role.

  • Runs on your own key (OpenRouter or any OpenAI-compatible API) or ours, paid with points
  • Only the origins you allow can load it
  • Your name, logo, colours and theme
<script src="https://acme-mcp.deemwar.com/widget.js"
        async></script>

API docs as a cited wiki

Agents can ask how your API works, not only call it

ask_docs returns numbered passages from your docs, each cited to its source. The same docs back the widget.

  • Built from your OpenAPI operations plus guide URLs and files (.md, .txt, .html, .pdf)
  • Browse what we understood and try questions before you publish
ask_docs("How long does an access token last?")

[1] Guides › Authentication
    "Access tokens expire after one hour..."
[2] POST /auth/token · responses

New · dmcp

Your live coding agent, as a connector.

One command publishes an agent running in herdr at your own deemwar.com address, with sign-in built in. It describes itself in its own words, so Claude, ChatGPT, Codex or your phone knows what to ask it.

Cross-agent terminals →
$ dmcp login
$ dmcp terminal serve ceo --publish
Clients will see: I am the CEO agent of Deemwar…
→ https://deemwar-terminal.deemwar.com/mcp

Security

Built so you can say yes to your security team.

Tokens never reach the AI

Your users' JWTs stay encrypted in our token vault. AI apps, the CLI and the widget hold only tokens we mint.

Your login, unchanged

Users sign in with your login or your identity provider. We verify the JWT by JWKS (or an HS256 shared secret).

Roles enforced

Operations a role can't use never appear in search, and calling one is rejected, on every surface.

Confirmation for risky actions

Operations you mark as needing confirmation run only with a single-use confirm token, after the user agrees.

How sign-in and tokens work →

FAQ

Questions, answered.

Do I need an OpenAPI spec?

It helps. Paste an OpenAPI/Swagger URL or a base URL and we probe the common spec paths (/openapi.json, /swagger.json, /v3/api-docs and more). If none is found, upload the spec file.

Do I have to change my login?

No. Your login page can redirect back with the user's token, we can relay a username and password once to your login API, your site can exchange its token for ours, or users can sign in with Google, Microsoft, Firebase or any OIDC provider.

Can the AI see my users' tokens?

No. Your user's JWT never reaches an MCP client, the CLI, the widget, the browser or the model. Clients get tokens we mint, and we call your API on the user's behalf.

Which AI apps work?

Any client that speaks remote MCP over HTTP with OAuth: Claude (web, desktop, mobile), ChatGPT, Claude Code, Codex, Cursor and VS Code. The docs have step-by-step instructions for each.

How is it priced?

Prepaid points, bought as credit packs in rupees or dollars. Tool calls, hosting, docs building and chat on our AI key use points; bring your own OpenRouter key and the widget uses no model points.

Can I sign up today?

Access is invite-only for publishers. Request access with your work email and once approved you sign in with that email, no password. Your end users need no invite.

Put your API where your users already work.

Access is invite-only while we onboard publishers. Bring a spec URL and your login page.

Request access Read the docs