Log In 
The Knack MCP Server is here, and we think it’s one of our most transformational launches in years. Here’s why.
Over the past couple of years, the tools available to non-technical builders have changed in ways that would have been hard to predict. Platforms like Lovable, Claude, and Base44 have made it possible for someone without a development background to describe what they want to build and have a working application interface in hours. That shift has been real, and we’ve been paying close attention to it at Knack.
What we kept hearing from builders in those communities was a different version of the same story: they’d built something genuinely useful, and then they’d run into a wall when they tried to take it somewhere serious. A healthcare organization, an enterprise client, a regulated business — any of those buyers has a set of requirements around data security, access control, and auditability that most AI-generated apps don’t come close to meeting. The frontend was done. The backend governance was the problem.
That’s the gap we built this for.
What we’re launching
Starting today, any AI coding tool that supports MCP configuration — Claude, Lovable, ChatGPT, Bolt, Base44, and Replit to start — can connect directly to Knack as its backend. Simply add Knack’s MCP Server URL to your AI coding tool’s configuration, sign in with your Knack credentials, and from that point forward, your AI coding agent knows what Knack can do and how to call it. Behind your frontend, you now have a hosted relational database, role-based access controls, record change logs, automated workflows, and 700+ native integrations.
For builders who’ve been hitting that wall, this is the way through.
What MCP actually is
If you haven’t worked with MCP before, the idea is easier to grasp than the acronym. Think of how USB works: when you plug a device into a computer, there’s a handshake. The device tells the computer what it is, what it can do, and what protocols to use. The computer configures itself accordingly. No manual setup, no documentation required. The protocol handles the introduction and the two systems work together from there.
MCP (Model Context Protocol) works the same way for AI agents and external services. When you connect Knack to your AI coding tool via MCP, the tool learns what Knack is, what data it holds, and what operations it can perform. You can describe what you want to build in plain language and your AI coding agent handles the integration. The technical setup happens in the background.
The reason this matters for compliance is straightforward. Once your AI coding tool has access to a compliant backend, the apps it helps you build are actually ready for production. The frontend and the backend are working from the same context from day one.
What Knack gives your AI coding tool
When your AI coding agent connects to Knack via MCP, here’s what it has access to:
A hosted relational database with 20+ field types
Record change logs and role-based access controls with permission settings at the field and record level
Built-in workflows, automations, and 700+ integrations
All of it is hosted and maintained by Knack with no server configuration on your end.
For healthcare organizations, Knack Health adds HIPAA-compliant infrastructure with Business Associate Agreements available for covered entities. More on that below.
Getting started in three steps
Connecting Knack to your AI coding tool takes a few minutes and doesn’t require any technical setup beyond the MCP configuration your tool already supports.
Step 1: Create or log in to your Knack account. If you already have a Knack account, you’re ready to move to Step 2. If not, sign up at knack.com — no credit card required.
Step 2: Add Knack to your tool’s MCP configuration. Each AI coding tool handles MCP configuration a little differently, but in all cases you’re entering Knack’s MCP Server URL and signing in with your Knack Builder credentials through a standard OAuth consent screen — no API keys or tokens to copy. Knack’s MCP Server URL is https://mcp.knack.com/mcp. (For government cloud environments, use https://knack-mcp-server.us-gov-west-1.gprd.knack.com/mcp instead.) Knack’s MCP Server documentation walks through the exact steps for Claude Code, Lovable, and the other supported tools.
Step 3: Start building. Once the connection is established, your AI coding agent understands your Knack environment — what data it holds and what operations it can perform. Describe what you need (e.g., a customer portal, intake form, or operations tracker) and your tool handles the integration while Knack handles the data.
For healthcare and other regulated industries
Healthcare organizations face specific, well-defined requirements around any application that handles patient data. HIPAA-compliant hosting, PHI-safe data architecture, and a signed Business Associate Agreement are required infrastructure, not optional features to add later.
Knack Health is purpose-built for exactly this. Every Knack Health environment runs on HIPAA-compliant hosting with PHI-ready database architecture, BAA availability for covered entities, role-based access controls, and full record change logs. The same MCP setup described above applies — connect your AI coding tool, sign in with your Knack credentials, and build on infrastructure that meets healthcare’s requirements from day one. Before going live with any patient data, our team works with you to execute your BAA and confirm your compliance posture.
Healthcare is where the compliance requirements are most explicit, but the same underlying infrastructure serves legal, fintech, HR, and other regulated industries where data accountability matters. Knack Health is the deepest expression of what Knack offers in those environments.
Learn more at knack.com/health/hipaa-backend.
Available today
Knack’s MCP Server is available to all new and existing customers today. If you don’t already have an account, you can start with a free trial (no credit card required) and connect your first AI coding tool in minutes. If you’re interested in setting up a HIPAA-compliant backend, book a free demo today.
FAQ
What is Knack's MCP Server?
Knack’s MCP Server is a connection layer that lets AI coding tools — including Lovable, Claude Code, Base44, and Replit — connect directly to Knack’s hosted backend. Once connected, your AI coding agent can read your data schema, create and modify tables and fields, and generate frontend components that map to your actual data model. It works through the Model Context Protocol (MCP), an open standard for connecting AI tools to external services. The server URL is https://mcp.knack.com/mcp and authentication uses OAuth with your existing Knack credentials.
What AI coding tools work with Knack's MCP Server?
Any AI coding tool that supports MCP configuration can connect to Knack. Knack’s documentation includes step-by-step setup guides for Lovable, Claude Code, Base44, and Replit. For the full list and setup instructions, visit docs.knack.com/docs/mcp.
Do I need an existing Knack account to get started?
Yes, but setup is straightforward. If you don’t have a Knack account, sign up at knack.com — no credit card required. Your Knack account is the environment your AI coding tool connects to. It’s where your data schema lives and where all record operations run.
How does authentication work — do I need an API key?
No API key required. Knack’s MCP Server uses OAuth. When you add https://mcp.knack.com/mcp as the server URL in your AI coding tool’s MCP configuration and select OAuth as the authentication method, your tool will open a browser window to complete the authentication flow using your Knack Dashboard credentials. You won’t need to copy or manage any tokens.
Is Knack's MCP Server available on all plans?
Yes. The MCP server is available to all Knack customers, including free trial accounts. For healthcare teams that need HIPAA-compliant infrastructure, Knack Health plans are required — the MCP server setup is the same, but your data runs on HIPAA-compliant hosting and includes a signed BAA.
Does my AI coding tool store or process PHI when connected to Knack?
No. PHI flows directly between the user’s browser and Knack’s backend via Knack’s runtime API. Your AI coding tool handles the frontend interface — it never stores or processes patient data. The compliance boundary sits at the Knack layer, which is where the BAA applies.
Can I connect Knack to an app I've already built in Lovable or Base44?
Yes. If you have an existing frontend in Lovable or Base44, you can connect Knack as the backend without rebuilding your frontend. In Lovable, you can migrate an existing project by telling the AI to migrate the backend tables and user roles to Knack via the MCP server. Base44 follows a similar process. Your frontend stays intact — you’re reconfiguring the data layer to run through Knack.
Where can I find setup instructions?
Full setup documentation for Lovable, Claude Code, Base44, Replit, and other MCP-compatible tools is at docs.knack.com/docs/mcp. For healthcare-specific setup, visit knack.com/health/hipaa-backend.
