How to Use the JSON Path Query Engine MCP in CrewAI

Q: Can I limit which agents can use the JSON Path Query Engine with CrewAI?

Yes. When you configure the MCPServerHTTP source in your CrewAI setup, use the toolfilter parameter. This lets you expose the queryjson tool only to the specific agents that should have access to it.

Equip your CrewAI agents to dig through massive JSON. Extract key data points for one agent to pass to the next, making your crew more efficient.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect JSON Path Query Engine MCP to CrewAI

Create your Vinkius account to connect JSON Path Query Engine to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup JSON Path Query Engine with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Specialize Your Agents by Data Task

Use `query_json` to create a dedicated 'Data Extractor' agent in your crew. This agent's only job is to take large JSON sources, run queries to pull out the important bits, and pass a clean, minimal result to the next agent. Your 'Analyst' or 'Writer' agent then gets a small, focused piece of data, not a 100MB file it has to read through. This makes the entire crew faster and more reliable.

Keep Your CrewAI Shared Memory Clean

A bloated shared memory context slows down your whole crew. Instead of stuffing a raw API response into the context for every agent to see, have the first agent use this MCP Server to do the dirty work. It can run `query_json` to get the three key values it needs, then put only those values into the shared context. This keeps communication between your agents lean and focused.

Build Faster Research & Analysis Crews

The `query_json` tool is perfect for research tasks. An agent can hit five different API endpoints, get back five large JSON payloads, and use queries to quickly extract just the names, dates, or stats it's looking for. It then assembles a concise summary for the next agent. This is far more efficient than asking an LLM to read and summarize hundreds of kilobytes of raw JSON from multiple sources.

Setup guide

Set up JSON Path Query Engine MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke JSON Path Query Engine tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="JSON Path Query Engine Analyst",
    goal="Access and analyze JSON Path Query Engine data via MCP.",
    backstory="Expert analyst with direct JSON Path Query Engine access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent JSON Path Query Engine transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

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

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="JSON Path Query Engine Analyst",
        goal="Access and analyze JSON Path Query Engine data via MCP.",
        backstory="Expert analyst with direct JSON Path Query Engine access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent JSON Path Query Engine transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by jsonpath-plus. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect JSON Path Query Engine now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about JSON Path Query Engine MCP in CrewAI

It's a perfect tool for a 'Researcher' or 'Data-Gatherer' agent. That agent processes large JSON files from APIs and passes only the specific, extracted data to other agents in the crew, improving overall efficiency.

Yes. When you configure the `MCPServerHTTP` source in your CrewAI setup, use the `tool_filter` parameter. This lets you expose the `query_json` tool only to the specific agents that should have access to it.

This is about offloading risk and standardizing a task. The MCP Server is optimized for memory usage on huge files, preventing your main Python script from crashing. It also provides a consistent tool interface for any agent.

Yes, it works perfectly for both. In a sequential process, one agent uses it and passes the clean data to the next. In a hierarchical setup, a manager agent could use it to validate the JSON output from its subordinates.

Each query request spins up its own ephemeral container. Your JSON payload is streamed in, processed entirely in-memory to find the matching data, and the whole environment is destroyed once the result is sent back. No part of your payload ever touches a disk or a log file.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript