Compatible with every major AI agent and IDE
What is the Glob Pattern Tester MCP Server?
When a DevOps agent writes .gitignore rules or CI pipeline includes, it cannot guess whether src/**/*.ts matches src/utils/helper.ts. This MCP provides the definitive answer.
The Superpowers
- Exact Match: Uses minimatch, the same engine behind npm, to evaluate glob patterns deterministically.
- All Patterns: Supports
*,**,?,[abc],{a,b}, and negation!.
Built-in capabilities (1)
gitignore rules, CI include/exclude patterns, or deploy filters. Pass the glob pattern (e.g. "src/**/*.ts") and the file path to test (e.g. "src/utils/helper.ts"). The engine returns a boolean match result using the exact same algorithm used by npm and git. Tests whether a file path matches a glob pattern using minimatch (130M+ weekly downloads). Essential for .gitignore, CI pipeline, and deploy rule validation
Why CrewAI?
When paired with CrewAI, Glob Pattern Tester becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Glob Pattern Tester tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
mcpsparameter 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
Glob Pattern Tester in CrewAI
Glob Pattern Tester and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Glob Pattern Tester to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Glob Pattern Tester in CrewAI
The Glob Pattern Tester 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. All 1 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* 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
How Vinkius secures
Glob Pattern Tester for CrewAI
Every tool call from CrewAI to the Glob Pattern Tester MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Is this the same algorithm git uses?
Yes. minimatch is the glob engine used by npm itself and follows the same POSIX glob specification that git uses for .gitignore.
Does it support double-star recursive patterns?
Yes. The ** pattern matches any number of directories recursively. For example, src/**/*.ts matches files at any depth inside src/.
Can I test negation patterns?
Yes. Prefix any pattern with ! to negate it. For example, !node_modules/** will NOT match any path inside node_modules.
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.
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.
Explore More MCP Servers
View all →
Ortto (formerly Autopilot)
10 toolsManage your CDP, customer data, and marketing automations via Ortto — orchestrate journeys natively via AI.

The Odds API
3 toolsUniversal sports betting intelligence — get real-time odds, scores, and sports data via AI.

GamerPower Gaming Giveaways
11 toolsFind and track free gaming giveaways — get Steam keys, Epic Games Store offers, and in-game loot via AI.

Everfit Coaching
10 toolsEquip your AI agent to manage coaching clients, track workout plans, and monitor performance via the Everfit API.
