Bring Transparency
to CrewAI
Learn how to connect TCE-SP (Audesp) to CrewAI and start using 3 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the TCE-SP (Audesp) MCP Server?
Connect to the TCE-SP Audesp system to audit and analyze public spending across municipalities in the state of São Paulo. This server provides direct access to the official transparency portal data.
What you can do
- Municipality Lookup — List all cities under TCE-SP jurisdiction and retrieve their unique slugs for precise querying
- Expense Analysis — Fetch detailed expense (despesas) records for any municipality, filtered by fiscal year and month
- Revenue Tracking — Access revenue (receitas) data to monitor municipal collections and budget performance
- Fiscal Auditing — Use AI to compare spending patterns and identify fiscal trends across different periods
How it works
- Subscribe to this server
- Enter your API access credentials or token
- Start querying public data from any MCP-compatible client like Claude or Cursor
Who is this for?
- Journalists & Researchers — quickly extract fiscal data for investigative reporting without manual portal navigation
- Public Managers — monitor municipal performance and compare budget execution against historical data
- Citizens & Activists — promote transparency by easily accessing how public resources are being allocated
Built-in capabilities (3)
List expenses for a specific municipality, year, and month
List all municipalities under TCE-SP jurisdiction
List revenues for a specific municipality, year, and month
Why CrewAI?
When paired with CrewAI, TCE-SP (Audesp) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call TCE-SP (Audesp) 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
TCE-SP (Audesp) in CrewAI
TCE-SP (Audesp) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect TCE-SP (Audesp) 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 TCE-SP (Audesp) in CrewAI
The TCE-SP (Audesp) 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 3 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
TCE-SP (Audesp) for CrewAI
Every tool call from CrewAI to the TCE-SP (Audesp) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find the correct name (slug) for a specific city?
Use the list_municipios tool. It returns a complete list of all municipalities under TCE-SP jurisdiction with their respective slugs needed for expense and revenue queries.
Can I query data for any year and month?
Yes, using list_despesas or list_receitas, you can specify the exercicio (year) and mes (month, 1-12) to get precise historical data for a municipality.
What is the difference between list_despesas and list_receitas?
list_despesas focuses on how the municipality spent its budget (expenses), while list_receitas shows the income and collections (revenues) received by the city.
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 →
Fxiaoke
10 toolsLeading sales management and CRM platform in China — manage leads, opportunities, and approvals via AI.
Hunter
12 toolsFind and verify professional email addresses with domain search, email finder, and deliverability verification for sales outreach.
Tray.io
6 toolsEquip your AI agent to orchestrate automations, track active workflows, and monitor data execution flows across Tray.io natively.
Amplenote
12 toolsConnect your Amplenote workspace to your AI agent — search notes, manage tasks, and organize ideas via natural language.