Agent integration

Connect an agent without guesswork.

Use the public MCP endpoint to discover plans and start signup, or connect an account key for private account and team tools. This guide is the human-readable companion to llms.txt.

Quick start

One endpoint, two access levels.

Endpoint: https://apptemplate.integralmedia.com.au/mcp. It uses Streamable HTTP and the MCP protocol version 2026-07-28.

  1. For public discovery, call get_plans with no credentials.
  2. For signup, call sign_up with an email and plan ID such as starter. It creates a free passwordless account, emails an out-of-band fragment verification link carrying the selected plan, and returns verification_sent plus checkout_after_verification—never a Checkout URL or token. After email proof, the browser lands on pricing and the human explicitly starts Stripe Checkout.
  3. For private tools, sign in to the website, open Account, and create a personal or team API key.

Payment remains an explicit human action after email verification; do not claim that an agent completed Stripe Checkout.

Authentication

Create a key, then copy it once.

API keys are created at /account. Choose a label and optional expiry. Team scope is available only to eligible team, admin, or super users. The raw key is shown only in the immediate response after creation and cannot be recovered later; store it in the client secret store.

Bearer header only: send Authorization: Bearer <your-key>. Never put a key in a URL, query string, HTML, prompt, issue, or log.

Use a personal key for account tools. A team key includes the account tools plus team tools, subject to the owner's current role and scope checks.

Claude

Copy-ready placeholder configuration

Paste this JSON into your Claude Code MCP configuration, then replace the placeholder locally with the key you copied once.

{
    "mcpServers": {
        "IM SaaS": {
            "url": "https://apptemplate.integralmedia.com.au/mcp",
            "headers": {
                "Authorization": "Bearer imk_REPLACE_WITH_API_KEY"
            }
        }
    }
}

Cursor

Copy-ready placeholder configuration

Paste this JSON into Cursor's MCP settings, then replace the placeholder locally. Keep the Authorization value out of source control.

{
    "mcpServers": {
        "im-saas": {
            "url": "https://apptemplate.integralmedia.com.au/mcp",
            "headers": {
                "Authorization": "Bearer imk_REPLACE_WITH_API_KEY"
            }
        }
    }
}

Tool inventory

Public discovery and signup

Public MCP tools
ToolAccessPurpose
get_plansPublicLists available subscription plans and included credits.
sign_upPublicCreates a free passwordless account, emails an out-of-band fragment verification link carrying the selected plan, and returns verification_sent plus checkout_after_verification; no Checkout URL or token. Required arguments: email, plan.

User tools

User MCP tools
ToolPurpose
get_accountReturns the authenticated account without password material.
get_credit_balanceReturns the authenticated account credit balance.
get_usageReturns authenticated account credit-ledger usage.
use_featureSpends credits atomically on a named feature.
create_browser_login_linkEmails a one-time browser handoff and returns sent=true; no capability URL is returned.

Team tools

Team MCP tools
ToolPurpose
list_usersLists users for an authorized team account.
user_detailReturns one user for an authorized team account.
adjust_creditsApplies an attributed credit grant or spend as an administrator.
metrics_summaryReturns aggregate account, credit, and webhook metrics.
recent_webhook_eventsReturns safe metadata for recent webhook events.

Browser WebMCP

Progressive enhancement, not a new auth path.

WebMCP is a client-side browser capability. Supporting browsers can expose page actions through document.modelContext (the older navigator.modelContext path is deprecated) and declarative forms can use toolname and tooldescription. Treat this as an optional enhancement: the normal labelled HTML forms and server-side authorization remain the source of truth, and unsupported browsers keep working without JavaScript.

WebMCP does not replace the remote /mcp endpoint or grant credentials. Do not place an API key in browser markup or client-side JavaScript.

Compatibility note

ChatGPT connectors are not supported.

ChatGPT connectors require an OAuth 2.1 authorization flow. This service currently offers static bearer API keys for Claude and Cursor only; it does not implement connector OAuth, and you must not present it as ChatGPT-compatible.

Open connection details · Create an account · Read machine-readable discovery