Knack
No-code database and business application platform for building custom web apps without coding.
Verdict
Common use cases
- Add customer inquiries to CRM from chat
- Update inventory counts after receiving shipments
- Pull project status for weekly reports
- Log support tickets into tracking database
- Query order history during customer calls
Integration
- Vendor
- Knack
- Category
- other
- Auth
- API_KEY
- Tools
- 10
- Composio slug
knack
Tools
- Create object record
Tool to create a new record in a specific Knack object. Use when you need to add new data to a Knack database object. Requires object-based API key authentication.
- Create View Record
Tool to create a new record through a form view in Knack. Use when you need to add a record to a Knack object using a form view interface. Only fields that exist in the form will be used, and any record rules configured on the form will be
- Delete Object Recorddestructive
Tool to delete a single record from a specific Knack object by its ID. Use when you need to permanently remove a record from an object. This action is permanent and cannot be undone. Requires API key authentication (X-Knack-Application-Id a
- Delete View Recorddestructive
Tool to delete a record through a view that contains a delete link. Works with tables, lists, searches, calendars, and details views. This operation is permanent and cannot be undone. Use only after confirming the correct scene_key, view_ke
- Get Object Record
Tool to retrieve a single record by its ID from a specific Knack object. Returns the complete record with all field values in both formatted and raw formats. Use this for object-based access which requires API key authentication.
- List Object Records
Tool to retrieve multiple records from a specific Knack object (table). Returns up to 1000 records per page with pagination support. Use this for object-based access which requires API key authentication and provides full access to all fiel
- List View Records
Tool to retrieve multiple records from a specific Knack view (tables, lists, searches, calendars). Use when you need to fetch data from a view with pagination support. Returns only fields included in the view configuration.
- Update object record
Tool to update an existing record in a specific Knack object. Use when you need to modify field values in an existing record. Only fields provided in the request will be updated; all other fields remain unchanged.
- Upload File
Tool to upload a file to a Knack application. This is step 1 of a two-step process - after uploading, use the returned file ID when creating or updating a record with a file field.
- Upload Image
Tool to upload an image to a Knack application. This is the first step in a two-step process - after uploading, use the returned file ID when creating or updating a record with an image field. Use when you need to attach images to Knack rec
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Search for Knack in the MCP directory and click Connect. 3. You'll be prompted to enter your Knack Application ID and API Key — find these in your Knack app's Settings under API & Code. 4. Grant the API key read and write access to the objects you want Switchy to interact with. 5. Click Save to establish the connection. 6. Open any Space and type '@Knack list records from [object name]' to test — the AI should return a sample of records from that object. 7. If you see data, the connection is live; if you get an error, verify your API key has the correct object permissions in Knack. 8. To invoke Knack tools, always start your prompt with '@Knack' followed by the action you need, like creating a record or updating a field.
What teammates see: by default, memories from Knack are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Add New Lead
@Knack create a new record in the Contacts object with name 'Jane Doe', email 'jane@example.com', company 'Acme Corp', and status 'New Lead'.Open in a Space →
Check Inventory Levels
@Knack list all records from the Inventory object where quantity is less than 10, and show me the product name and current stock level.Open in a Space →
Update Project Status
@Knack update the record with ID abc123 in the Projects object, setting the status field to 'In Review' and the last_updated field to today's date.Open in a Space →
Log Support Ticket
@Knack create a record in the Support Tickets object with subject 'Login issue', priority 'High', customer_email 'user@domain.com', and description 'User cannot access account after password reset'.Open in a Space →
Pull Recent Orders
@Knack list the most recent 20 records from the Orders object, sorted by order_date descending, and show me the order number, customer name, and fulfillment status.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Knack list all customer records from the Customers object where status is 'Active', sorted by last contact date
Retrieved 47 active customer records from your Knack Customers object. The most recently contacted customers include: Acme Corp (last contact: 2024-01-15, account value: $45,000), TechStart Inc (last contact: 2024-01-14, account value: $32,500), and Global Solutions LLC (last contact: 2024-01-12, account value: $28,000). Each record includes contact details, account status, and custom fields you've configured. Results are paginated with up to 1000 records per page.
This example demonstrates read access to Knack's object-based API. Requires an API key with read permissions for the specific object. The MCP returns both formatted and raw field values, making it useful for data analysis. Be aware of the 1000-record pagination limit for large datasets.
@Knack create a new project record with name 'Q1 Website Redesign', status 'Planning', and assigned team member ID field_123
Successfully created a new project record in your Knack Projects object. Record ID: 65a3f2b8c9d4e1f2a3b4c5d6. The record was created with: Project Name = 'Q1 Website Redesign', Status = 'Planning', Assigned Team Member = field_123. All required fields were populated, and the record is now visible in your Knack application. Any connected records or automation rules configured in Knack have been triggered.
This example shows how to add structured data to your Knack database. The MCP requires you to know your object's field keys (like field_123) rather than human-readable names. Creating records can trigger Knack's built-in automation rules and email notifications, so test carefully in a development environment first.
@Knack pull all support tickets from the last 7 days and summarize the top 3 recurring issues by category
Retrieved 89 support tickets from your Knack system created between January 8-15, 2024. After analyzing the data, the top recurring issues are: 1) Login/Authentication Problems (23 tickets, 26%) - primarily password reset requests and SSO errors; 2) Billing Questions (18 tickets, 20%) - invoice discrepancies and subscription changes; 3) Feature Requests (15 tickets, 17%) - mostly requests for mobile app improvements and API enhancements. The remaining 33 tickets span bug reports, general inquiries, and account management.
This example combines Knack's data retrieval with AI analysis to surface patterns your team might miss. The MCP fetches raw ticket data, then the AI performs categorization and summarization. Useful for weekly team reviews, but remember the 1000-record limit means very high-volume periods may require multiple queries or date-range filtering.
Use-case deep-dives
When Knack MCP works for daily dispatch updates
A 6-person HVAC company runs their dispatch board in Knack and wants AI to update job statuses during morning standup. The Knack MCP is the right call here because the team already has their workflow locked into Knack's object model, and the 10 tools cover the full CRUD cycle they need. The AI can pull today's jobs with List View Records, update completion status with Update Object Record, and log new service calls with Create Object Record—all without leaving the chat. The API key auth is simple enough for a single admin to set up once. This breaks down if your dispatch logic involves more than basic field updates (like triggering Knack's own automation rules), because the MCP can't interact with Knack's workflow engine. If your team just needs to read and write structured records in an existing Knack app, this MCP closes the loop.
Why this MCP fits one-time data hygiene projects
A nonprofit with 800 member records in Knack needs to dedupe contacts and flag expired memberships before their annual fundraiser. The Knack MCP is a solid pick for this kind of sprint work because the AI can List Object Records to pull the full member table, identify duplicates by email or phone, then use Delete Object Record to remove the extras and Update Object Record to mark expiration dates. The 1000-record-per-page limit means the AI can handle the entire dataset in one or two calls. This approach works when your cleanup rules are straightforward (exact-match deduping, date comparisons). It falls apart if you need fuzzy matching or complex merge logic, because the MCP doesn't expose Knack's native deduplication tools. For a one-week cleanup sprint on a mid-sized database, this MCP saves you from exporting to CSV and re-importing.
When Knack MCP handles inbound ticket creation
A 3-person SaaS support team uses Knack to track customer issues and wants AI to log new tickets from Slack threads. The Knack MCP is the right tool if your ticket schema is simple (customer name, issue description, priority, status). The AI can call Create View Record to submit a new ticket through Knack's form view, which respects any field validation or default values you've set up in the form. The view-based approach is safer than direct object writes because it enforces the same rules your team follows when they manually log tickets. This stops working if your ticket workflow requires attachments or multi-step forms, because the MCP doesn't handle file uploads or form navigation. If your support process is just text fields and dropdowns, this MCP turns Slack messages into Knack records without a Zapier middleman.
Frequently asked
What does the Knack MCP let me do in Switchy?
It connects your Knack no-code database to Switchy so AI can read, create, update, and delete records across your objects and views. You can ask questions about your data, automate record creation from conversations, or bulk-update fields without opening the Knack builder. It works with both object-level operations (full database access) and view-level operations (form-based workflows).
Do I need admin access to connect Knack?
You need an API key from your Knack account, which typically requires builder or admin permissions. Knack uses object-based API keys for direct database access and view-based keys for form interactions. If your Knack admin has restricted API access, you won't be able to connect. Check your account settings under API & Code before attempting setup.
Can the MCP handle Knack's field rules and validations?
When creating or updating records through views, Knack's form-level validations apply—required fields, format rules, conditional logic. When working directly with objects via API key, you bypass some view-layer rules but still hit database-level constraints like unique fields or required values. Deletes are permanent and ignore any soft-delete workflows you've built in views.
Why use this instead of Knack's built-in automations?
Knack's native automations trigger on record events (create, update, schedule). This MCP lets AI decide when to act based on conversation context—like creating a record only if certain conditions are mentioned, or pulling data to answer a question mid-thread. It's reactive to human input, not pre-programmed triggers. Use Knack automations for scheduled tasks; use this for conversational workflows.
Who on my team should connect the Knack integration?
Whoever owns your Knack builder account and understands your object schema. They'll need to generate the API key and know which objects/views the team should access. Once connected, any Switchy workspace member can interact with Knack data through AI—no need for everyone to have Knack logins. One connection serves the whole workspace.