MCP FOR APP BUILDERS

Give your coding agent the complete AppClickPrint integration guide

Connect an MCP-compatible builder to the guides used by AppClickPrint's website. The agent can read the full customer and gateway lifecycle, choose instructions for your platform, and inspect API request contracts while building your app.

Connect your builder

Add a remote MCP server with this URL and select Streamable HTTP if your client asks for a transport:

https://mcp.appclickprint.com

No authentication or AppClickPrint API key is needed. This MCP provides public documentation only. Your application's backend still provisions customers and submits print jobs through the authenticated AppClickPrint API.

Remote MCP configuration varies by client. Use your client's MCP server settings; legacy SSE connections are not supported. Server-to-server connections do not need an Origin header.

Ask for the complete integration

Use the AppClickPrint MCP. Call get_integration_guide with the platform
that matches this project, then read both returned guides completely.
Preserve this app's authentication, tenant model and backend framework.
Implement the full lifecycle and tests, including permanent Add Gateway
and Manage Gateways controls, printer selection, printing and job outcomes.
Keep all AppClickPrint credentials in the trusted backend.

Supported platform values: ai-coding-agents, lovable, base44, replit, bolt, v0, bubble, flutterflow, google-ai-studio and weweb. Use ai-coding-agents for another framework or an existing custom backend.

The guides require a stable tenant external ID, encrypted customer-key storage, gateway-count polling even after initial setup, and refreshed printer IDs and aliases after gateway management. Print acceptance means queued; final outcomes require verified terminal webhooks. No public job-status GET or setup-completed webhook should be invented.

Available tools, resources and prompt

Tool	Purpose
`get_integration_guide`	Read the complete canonical and selected platform guides before editing.
`list_guides`	Discover platform, API, billing and printing use-case guides.
`read_guide`	Read a full guide or the OpenAPI specification.
`search_docs`	Find relevant guide excerpts, then read the full matching guide.
`get_api_endpoint`	Inspect a documented method/path, authentication and request/response schemas.

Clients supporting resources can browse appclickprint://docs/developers and the other listed guides. The integrate_appclickprint prompt includes the canonical guide and your selected platform guide.

Run from a local checkout

Install dependencies with npm install using Node.js 22.5 or newer. Add this stdio configuration to your MCP client, replacing the path with the absolute path to your checkout:

{
  "mcpServers": {
    "appclickprint": {
      "command": "node",
      "args": ["/absolute/path/AppClickPrint/server/mcp/stdio.js"]
    }
  }
}

Local stdio runs without a database or API credentials. Documentation is read at startup; restart the MCP process after updating the checkout. Application credentials belong in your application's secret store, not in this MCP configuration or tool arguments.

Developer guide Platform guides