Knack MCP Server

You must provide the data as a JSON string where keys are the field keys (e.g., field_1). Ensure you have checked the object schema first to know which fields are required. Create a new record in a Knack object

Use with caution as this action cannot be undone. Delete a record from a Knack object

Returns metadata including the object name, key, and high-level structure. Use this to verify you are working with the correct database table. Get the schema of a specific Knack object

Requires both the object_key and the record_id. Use this for detailed auditing of a specific entry. Get a specific record by ID

Use this to verify access or discover application IDs. List all applications in the account

This is crucial for understanding the data types and identifying the field keys (field_1, field_2, etc.) needed for creating or updating records. List all fields for a specific Knack object

This is the first step to understand the database structure and find the "Object Key" needed for record operations. List all objects in the Knack application

You must provide the object_key. Use this to browse the actual data stored in your database. List records for a specific Knack object

The filters must be provided as a JSON string following the Knack Filter format (e.g., "[{\"field\":\"field_1\", \"operator\":\"is\", \"value\":\"test\"}]"). Search for records using filters

Provide only the fields you wish to change in the JSON string data. This is a partial update. Update an existing record in a Knack object