How do I find the Object Key for a specific table?

Use the `list_objects` tool. It will return all data objects in your application along with their names and unique keys (e.g., `object_1`). Use these keys for all subsequent record operations.

Can I search records using multiple conditions?

Yes. Use the `search_records` tool and provide a JSON array of filter objects. For example: `[{"field":"field_1", "operator":"is", "value":"active"}, {"field":"field_2", "operator":"contains", "value":"premium"}]`.

How do I know which fields to use when creating a record?

Use the `list_object_fields` tool with the target `object_key`. It will list all fields, their types, and their keys (e.g., `field_1`), which you must use as property names in your data JSON.

Knack MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Knack
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Knack through Vinkius, pass the Edge URL in the `mcps` parameter and every Knack tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Knack Specialist",
    goal="Help users interact with Knack effectively",
    backstory=(
        "You are an expert at leveraging Knack tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Knack "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Knack MCP Server

Connect your Knack application to any AI agent and take full control of your no-code database through natural conversation.

When paired with CrewAI, Knack becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Knack tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Database Schema Discovery — List all objects and fields to understand your data structure without leaving the chat
Record Management — Create, retrieve, update, and delete records in any object securely
Advanced Querying — Search for specific records using complex filters based on any field criteria
Data Auditing — Get detailed summaries of specific records to verify information or track changes
Bulk Operations — Effortlessly manage multiple records by providing structured data to your agent

The Knack MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Knack to CrewAI via MCP

Follow these steps to integrate the Knack MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Knack

Why Use CrewAI with the Knack MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Knack through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Knack + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Knack MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Knack for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Knack, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Knack tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Knack against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Knack MCP Tools for CrewAI (10)

These 10 tools become available when you connect Knack to CrewAI via MCP:

create_record

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

delete_record

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

get_object_schema

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

get_record

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

list_account_applications

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

list_object_fields

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

list_objects

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

list_records

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

search_records

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

update_record

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

Example Prompts for Knack in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Knack immediately.

"List all database objects in my Knack app"

"Find all premium customers in 'object_1'"

"Create a new customer in 'object_1' with name 'Sarah' and email 'sarah@example.com'"

Troubleshooting Knack MCP Server with CrewAI

Common issues when connecting Knack to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Knack + CrewAI FAQ

Common questions about integrating Knack MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.