4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
ALESP (Assembleia SP) MCP Server

Bring Legislative Data
to CrewAI

Learn how to connect ALESP (Assembleia SP) to CrewAI and start using 18 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get Agenda EventosGet ComissoesGet Comissoes MembrosGet Comissoes ReunioesGet Comissoes VotacoesGet DeputadosGet Despesas GabinetesGet Documento AndamentoGet Documento Andamento AtualGet Documento AutorGet Funcionarios CargosGet Legislacao NormasGet Legislacao TemasGet Legislacao Tipo NormasGet LotacoesGet PartidosGet Proposituras Zip UrlGet Uas

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
ALESP (Assembleia SP)

What is the ALESP (Assembleia SP) MCP Server?

Connect to the ALESP (Assembleia Legislativa do Estado de São Paulo) open data portal to monitor legislative activities in real-time. This MCP server allows AI agents to query official information about state deputies, cabinet expenses, committee meetings, and the full lifecycle of legislative proposals.

What you can do

  • Deputy Tracking — List all current state deputies and their political affiliations directly from the official registry.
  • Financial Transparency — Query reimbursed cabinet expenses for any deputy, with support for historical data by year.
  • Legislative Progress — Track the status, authors, and full history of proposals, bills, and other documents.
  • Committee Monitoring — Access details about permanent committees, including their members, meetings, and voting records.
  • Administrative Data — Inspect the organizational structure, staff placements, and job history within the assembly.

How it works

  1. Subscribe to this server
  2. No complex API keys are required for this public data source
  3. Start auditing legislative transparency from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Journalists & Researchers — quickly gather data on deputy expenses and voting patterns for reporting.
  • Legal Professionals — monitor the progress of specific bills and legislative norms in real-time.
  • Citizens & Activists — promote transparency by easily accessing public records through natural conversation.

Built-in capabilities (18)

get_agenda_eventos

List upcoming and past events scheduled at the Assembly

get_comissoes

List permanent committees of the assembly

get_comissoes_membros

List members of the permanent committees

get_comissoes_reunioes

List meetings of the permanent committees

get_comissoes_votacoes

List votes of the permanent committees

get_deputados

List all state deputies in the current legislature

get_despesas_gabinetes

Optionally provide a year for historical data. List reimbursed expenses for each deputy cabinet

get_documento_andamento

Get full history and status of proposals

get_documento_andamento_atual

Get current status of proposals

get_documento_autor

List authors and co-signers for each legislative document

get_funcionarios_cargos

List job history of ALESP staff

get_legislacao_normas

List state norms (laws, decrees, resolutions)

get_legislacao_temas

List themes/topics of state norms

get_legislacao_tipo_normas

List types of state norms

get_lotacoes

List current placements (lotações) of ALESP staff

get_partidos

List political parties participating in the legislative process

get_proposituras_zip_url

Get the URL for the comprehensive list of all legislative proposals (ZIP)

get_uas

List Administrative Units (UAs) of ALESP

Why CrewAI?

When paired with CrewAI, ALESP (Assembleia SP) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ALESP (Assembleia SP) 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 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

See it in action

ALESP (Assembleia SP) in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

ALESP (Assembleia SP) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect ALESP (Assembleia SP) 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for ALESP (Assembleia SP) in CrewAI

The ALESP (Assembleia SP) 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 18 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.

ALESP (Assembleia SP)
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

The Vinkius Advantage

How Vinkius secures ALESP (Assembleia SP) for CrewAI

Every tool call from CrewAI to the ALESP (Assembleia SP) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How can I check the reimbursed expenses for a specific deputy's cabinet?

You can use the get_despesas_gabinetes tool. You can also provide a specific year to retrieve historical expense data.

02

Is it possible to track the full history of a legislative proposal?

Yes! Use the get_documento_andamento tool to fetch the XML data tracking the full history and status of proposals.

03

How do I see who are the members of the permanent committees?

Use the get_comissoes_membros tool to list all members currently serving on the assembly's permanent committees.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

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

10

Agent not using tools

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

11

Timeout errors

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

12

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 →