Skip to main content

Yamify MCP Quickstart (Cursor, Claude, Lovable)

Yamify MCP is a control-plane interface. It lets MCP-enabled tools list your Yamify workspaces/apps and provision supported resources using explicit tools (instead of clicking the UI).

1) Prereqs​

  • A Yamify account
  • Your Yamify base URL: https://yamify.co
  • Your Yamify login (Clerk)

2) Confirm MCP is reachable (browser)​

  1. Sign in: https://yamify.co/auth/sign-in
  2. Open dashboard: https://yamify.co/dashboard
  3. In another tab, open: https://yamify.co/api/v1/mcp

You should see a JSON status response.

Note: MCP clients typically use POST JSON-RPC. The GET response is just a human-friendly status page.

3) Authentication options​

Yamify MCP supports two auth modes:

A) Session (browser only)​

If you are signed in via Clerk in your browser, calling MCP from the browser will authenticate using your session.

This usually does not work for desktop MCP clients like Cursor unless they forward browser cookies (they typically do not).

MCP clients should authenticate using request headers:

  • x-yamify-api-key: <key>
  • x-yamify-user-email: <your_email>

Today this is a team-managed key. If you do not have it, ask the Yamify admin.

4) Add Yamify MCP to Cursor (copy/paste)​

In Cursor:

  1. Open Settings
  2. Find MCP (or Tools → MCP Servers, depending on version)
  3. Add a new MCP server:
    • Name: yamify
    • URL: https://yamify.co/api/v1/mcp
    • Headers:
      • x-yamify-api-key
      • x-yamify-user-email

If Cursor asks for a JSON config, use:

{
  "mcpServers": {
    "yamify": {
      "url": "https://yamify.co/api/v1/mcp",
      "headers": {
        "x-yamify-api-key": "<YOUR_YAMIFY_API_KEY>",
        "x-yamify-user-email": "you@company.com"
      }
    }
  }
}

5) Add Yamify MCP to Claude Desktop (copy/paste)​

Claude Desktop uses an MCP config file (location varies by OS).

Example config:

{
  "mcpServers": {
    "yamify": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "--url",
        "https://yamify.co/api/v1/mcp",
        "--header",
        "x-yamify-api-key: <YOUR_YAMIFY_API_KEY>",
        "--header",
        "x-yamify-user-email: you@company.com"
      ]
    }
  }
}

If you use a different MCP bridge than mcp-remote, keep the same URL + headers.

6) Lovable (and other MCP-enabled tools)​

If the tool supports MCP servers, the setup is the same:

  • URL: https://yamify.co/api/v1/mcp
  • Headers: x-yamify-api-key, x-yamify-user-email

7) Test the connection (what to type)​

In your MCP-enabled chat tool, ask:

  • “List my Yamify workspaces.”
  • “List my deployed apps and URLs.”

8) Raw JSON-RPC examples (for debugging)​

List tools:

curl -sS -XPOST https://yamify.co/api/v1/mcp \
  -H 'content-type: application/json' \
  -H 'x-yamify-api-key: <YOUR_YAMIFY_API_KEY>' \
  -H 'x-yamify-user-email: you@company.com' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Call yamify.list_workspaces:

curl -sS -XPOST https://yamify.co/api/v1/mcp \
  -H 'content-type: application/json' \
  -H 'x-yamify-api-key: <YOUR_YAMIFY_API_KEY>' \
  -H 'x-yamify-user-email: you@company.com' \
  -d '{
    "jsonrpc":"2.0",
    "id":2,
    "method":"tools/call",
    "params":{
      "name":"yamify.list_workspaces",
      "arguments":{}
    }
  }'

What Yamify MCP can do today​

Current MCP tools include:

  • yamify.list_workspaces
  • yamify.list_apps
  • yamify.deploy_inference_api

For app deployments (n8n/OpenClaw/WordPress/etc), use the Yamify dashboard or the Yamify Telegram bot today.