Connect an agent

Connect Claude, ChatGPT, Cursor or your own agent to Wantly. The agent can search and edit the catalog, prepare proposals from your templates and manage client contacts. Share this page with customers.

1. What you need

2. claude.ai, Claude Desktop / mobile and ChatGPT (sign in, no API key)

1. Claude: Settings → Connectors → Add custom connector. ChatGPT: Settings → Connectors → Create (developer mode may need to be on).
2. Name: Wantly. URL: https://YOUR-TENANT.wantly.eu/api/mcp. Leave the OAuth client ID / secret empty.
3. Click Connect. A Wantly page opens: log in (and pass 2FA), tick what the AI may do, click Allow.

The AI then works as you: proposals it creates have you as the author. Administrators can grant every permission; other users can read the catalog and prepare proposals and contacts. The sign-in renews itself; it ends after 60 days without use. See or disconnect apps at /oauth/connections.

A connector is added once per person. In a Claude Team / Enterprise organisation an owner can add it for everyone; each person still signs in with their own Wantly account.

3. Claude Code, Cursor and scripts (API key)

Use the main key from Settings → API → Generate API key (full access), or ask your administrator for a limited key (scopes such as catalog.read, proposals.write, contacts.write). Send it as Authorization: Bearer YOUR_API_KEY.

Claude Code

claude mcp add --transport http wantly https://YOUR-TENANT.wantly.eu/api/mcp --header "Authorization: Bearer YOUR_API_KEY"

Without --header, Claude Code signs in with your Wantly account instead: run /mcp and choose Authenticate.

Cursor and other clients that accept a URL with headers

{
  "mcpServers": {
    "wantly": {
      "url": "https://YOUR-TENANT.wantly.eu/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Cursor: .cursor/mcp.json (project) or ~/.cursor/mcp.json (user).

Clients that only run local (stdio) servers

npx -y mcp-remote https://YOUR-TENANT.wantly.eu/api/mcp --header "Authorization: Bearer YOUR_API_KEY"

OpenAI Agents SDK (Python)

from agents.mcp import MCPServerStreamableHttp

async with MCPServerStreamableHttp(
    name="wantly",
    params={
        "url": "https://YOUR-TENANT.wantly.eu/api/mcp",
        "headers": {"Authorization": "Bearer YOUR_API_KEY"},
    },
) as wantly:
    # pass mcp_servers=[wantly] into your Agent
    ...

Plain JSON API (no MCP)

Every tool is also POST /api/v2/<tool> with a JSON body; spec at /api/v2/openapi.json (usable as ChatGPT GPT Actions with Bearer auth). Details: API v2 and MCP.

curl -X POST https://YOUR-TENANT.wantly.eu/api/v2/proposals_templates \
  -H "Authorization: Bearer YOUR_API_KEY" -H "Content-Type: application/json" -d '{}'

4. What the agent can do

• Catalog: search and read products and variations, edit products and prices, merge products into variable products, categories, attributes, tags, images.
• Proposals: list templates, create a proposal from a template with catalog or custom lines, groups, sub-lines and attribute values; edit lines and header; search; delete / restore; link to Hanna CRM opportunities.
• Contacts: search, read, create and update clients.
• Every change can be previewed first with "dry_run": true.

Give the agent the guides before it starts (MCP clients get them as the guide_read tool and as resources):

• Proposals guide — how to prepare a proposal; the agent asks which template to use.
• Catalog guide — products, variations, attributes and safe bulk changes.

Example prompt: "Prepare a proposal for Example UAB with 10 pcs of SKU ABC-1 and installation; ask me which template to use."

5. Older setup (still works)

Before the remote MCP server, agents used a local Node script with a smaller tool set over the v1 API. Existing setups keep working; for new ones use sections 2–3.

• wantly-mcp.js (Node 18+, stdio) with WANTLY_BASE_URL and WANTLY_API_KEY; config: wantly-mcp.json.
• openapi-agent.yaml — v1 endpoints getproducts, getcontacts, createcontact, getproposals, createproposalfromtemplate, createproposalfromcatalog.

An API key is an admin secret (it can change the catalog and proposals). Do not paste it into prompts or public chats; prefer the sign-in connector or a limited key.