mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-02 05:38:12 +00:00
* feat: adopt directory-based docs versioning with Edge channel Switch docs.crewai.com from navigation-only versioning (every version selector entry rendered the same docs/<lang>/* source files) to Mintlify's directory-based versioning so each version selector entry renders its own snapshot. Add an "Edge" channel under docs/edge/<lang>/* that always reflects main HEAD for unreleased work, eliminating pre-release leakage onto frozen release labels. External links to canonical /<lang>/* URLs are preserved via wildcard redirects that always land on the current default version. Layout: - docs/edge/<lang>/* rolling source (you edit here) - docs/edge/enterprise-api.*.yaml - docs/v<X.Y.Z>/<lang>/* frozen, immutable snapshots - docs/v<X.Y.Z>/enterprise-api.*.yaml - docs/images/ shared, append-only - docs/docs.json nav + redirects URLs follow the Mintlify-idiomatic shape: /edge/<lang>/<page> for Edge, /v<X.Y.Z>/<lang>/<page> for every frozen snapshot. The wildcard redirects /<lang>/:slug* -> /<default>/<lang>/:slug* keep stale links working, and every freeze rewrites them (plus all per-section/per-page redirects) so destinations always resolve to the current default without depending on a second redirect hop. Release flow integration (devtools release): - New module crewai_devtools.docs_versioning.freeze() materialises docs/v<X.Y.Z>/ from docs/edge/, rewrites openapi: refs inside the snapshot, inserts the version into every language block in docs.json, and refreshes all redirect destinations. - _update_docs_and_create_pr() in cli.py now calls that freeze during Phase 2 of devtools release. Edge changelogs are updated first (so the snapshot freeze picks them up), then the snapshot is staged alongside docs.json, branched as docs/freeze-v<X.Y.Z>, and the PR is titled [docs-freeze] docs: snapshot and changelog for v<X.Y.Z> — the title prefix the new CI guard reads. - The PR still gates tag, GitHub release, PyPI publish, and the enterprise release as before; no new PRs are added. - Pre-releases (1.X.YaN, 1.X.YbN, ...) skip the snapshot — they ride Edge — and the docs PR title omits the [docs-freeze] prefix. - docs_check (AI-generated docs scaffolding) writes to docs/edge/<lang>/* so newly-generated unreleased docs land in Edge and never accidentally touch a frozen snapshot. Migration scripts (one-shot): - scripts/docs/freeze_historical_versions.py reconstructs all 16 historical snapshots (v1.10.0 .. v1.14.7) from git tags via git archive | tar, rewriting openapi: MDX refs so each snapshot reads its own enterprise-api YAML rather than the live one. - scripts/docs/prefix_version_paths.py one-shot-migrates docs.json: rewrites every page path in 16 versioned blocks to point under docs/v<X.Y.Z>/, inserts a new Edge entry per language, tags v1.14.7 as Latest (default), prunes pages whose target file doesn't exist in the snapshot (e.g. docs/ar/ didn't exist before v1.12.0), and writes the wildcard + per-section redirects. - scripts/docs/freeze_current_edge.py is now a thin CLI wrapper around docs_versioning.freeze for manual one-off freezes (e.g. retroactively snapshotting a forgotten release). CI guards (.github/workflows/docs-snapshots.yml): - Frozen snapshots under docs/v[0-9]*/ are immutable; only PRs whose title contains [docs-freeze] (i.e. release-cut PRs generated by devtools release or the manual wrapper) may modify them. - Images under docs/images/ are append-only since snapshots share a single image directory. Deleting or renaming an image breaks every historical snapshot that still references it. Restored docs/images/crewai-otel-export.png from PR #3673; it was deleted in PR #4908 but v1.10.0 / v1.10.1 snapshots still reference it. Restoring instead of editing the snapshots preserves historical rendering fidelity and validates the new append-only rule retroactively. Tests: - lib/devtools/tests/test_docs_versioning.py covers the freeze: file copy, openapi rewrite, version insertion, default demotion, redirect upserts, per-section redirect rewriting, idempotency, and invalid inputs. Verified locally with mintlify broken-links: 0 broken links across the full site (Edge + 16 frozen versions, 4 locales). AGENTS.md (repo root) is the contributor guide for the new model; RELEASING.md is the release-cut runbook; README's Contribution section links to both. Co-authored-by: Cursor <cursoragent@cursor.com> * style: resolve linter issues --------- Co-authored-by: Cursor <cursoragent@cursor.com>
136 lines
5.9 KiB
Plaintext
136 lines
5.9 KiB
Plaintext
---
|
|
title: Transporte HTTP Streamable
|
|
description: Saiba como conectar o CrewAI a servidores MCP remotos usando o transporte HTTP Streamable flexível.
|
|
icon: globe
|
|
mode: "wide"
|
|
---
|
|
|
|
## Visão Geral
|
|
|
|
O transporte HTTP Streamable oferece uma maneira flexível de se conectar a servidores MCP remotos. Ele é frequentemente baseado em HTTP e pode suportar vários padrões de comunicação, incluindo requisição-resposta e streaming, às vezes utilizando Server-Sent Events (SSE) para fluxos do servidor para o cliente dentro de uma interação HTTP mais ampla.
|
|
|
|
## Conceitos-Chave
|
|
|
|
- **Servidores Remotos**: Projetado para servidores MCP hospedados remotamente.
|
|
- **Flexibilidade**: Pode suportar padrões de interação mais complexos do que SSE puro, potencialmente incluindo comunicação bidirecional se o servidor implementá-la.
|
|
- **Configuração do `MCPServerAdapter`**: Você precisará fornecer a URL base do servidor para comunicação MCP e especificar `"streamable-http"` como o tipo de transporte.
|
|
|
|
## Conectando via HTTP Streamable
|
|
|
|
Você tem dois métodos principais para gerenciar o ciclo de vida da conexão com um servidor MCP HTTP Streamable:
|
|
|
|
### 1. Conexão Totalmente Gerenciada (Recomendado)
|
|
|
|
A abordagem recomendada é usar um gerenciador de contexto Python (`with` statement), que lida automaticamente com a configuração e encerramento da conexão.
|
|
|
|
```python
|
|
from crewai import Agent, Task, Crew, Process
|
|
from crewai_tools import MCPServerAdapter
|
|
|
|
server_params = {
|
|
"url": "http://localhost:8001/mcp", # Replace with your actual Streamable HTTP server URL
|
|
"transport": "streamable-http"
|
|
}
|
|
|
|
try:
|
|
with MCPServerAdapter(server_params) as tools:
|
|
print(f"Available tools from Streamable HTTP MCP server: {[tool.name for tool in tools]}")
|
|
|
|
agente_http = Agent(
|
|
role="Integrador de Serviços HTTP",
|
|
goal="Utilizar ferramentas de um servidor MCP remoto via Streamable HTTP.",
|
|
backstory="Um agente de IA especializado em interagir com serviços web complexos.",
|
|
tools=tools,
|
|
verbose=True,
|
|
)
|
|
|
|
http_task = Task(
|
|
description="Realizar uma consulta de dados complexa usando uma ferramenta do servidor Streamable HTTP.",
|
|
expected_output="O resultado da consulta de dados complexa.",
|
|
agent=agente_http,
|
|
)
|
|
|
|
http_crew = Crew(
|
|
agents=[agente_http],
|
|
tasks=[http_task],
|
|
verbose=True,
|
|
process=Process.sequential
|
|
)
|
|
|
|
result = http_crew.kickoff()
|
|
print("\nCrew Task Result (Streamable HTTP - Managed):\n", result)
|
|
|
|
except Exception as e:
|
|
print(f"Error connecting to or using Streamable HTTP MCP server (Managed): {e}")
|
|
print("Ensure the Streamable HTTP MCP server is running and accessible at the specified URL.")
|
|
|
|
```
|
|
**Nota:** Substitua `"http://localhost:8001/mcp"` pela URL real do seu servidor MCP HTTP Streamable.
|
|
|
|
### 2. Ciclo de Vida da Conexão Manual
|
|
|
|
Para cenários que exigem controle mais explícito, você pode gerenciar a conexão do `MCPServerAdapter` manualmente.
|
|
|
|
<Info>
|
|
É **crítico** chamar `mcp_server_adapter.stop()` quando terminar para fechar a conexão e liberar recursos. Usar um bloco `try...finally` é a forma mais segura de garantir isso.
|
|
</Info>
|
|
|
|
```python
|
|
from crewai import Agent, Task, Crew, Process
|
|
from crewai_tools import MCPServerAdapter
|
|
|
|
server_params = {
|
|
"url": "http://localhost:8001/mcp", # Replace with your actual Streamable HTTP server URL
|
|
"transport": "streamable-http"
|
|
}
|
|
|
|
mcp_server_adapter = None
|
|
try:
|
|
mcp_server_adapter = MCPServerAdapter(server_params)
|
|
mcp_server_adapter.start()
|
|
tools = mcp_server_adapter.tools
|
|
print(f"Available tools (manual Streamable HTTP): {[tool.name for tool in tools]}")
|
|
|
|
manual_http_agent = Agent(
|
|
role="Usuário Avançado de Serviços Web",
|
|
goal="Interagir com um servidor MCP usando conexões HTTP Streamable gerenciadas manualmente.",
|
|
backstory="Um especialista em IA em ajustar integrações baseadas em HTTP.",
|
|
tools=tools,
|
|
verbose=True
|
|
)
|
|
|
|
data_processing_task = Task(
|
|
description="Enviar dados para processamento e recuperar resultados via Streamable HTTP.",
|
|
expected_output="Dados processados ou confirmação.",
|
|
agent=manual_http_agent
|
|
)
|
|
|
|
data_crew = Crew(
|
|
agents=[manual_http_agent],
|
|
tasks=[data_processing_task],
|
|
verbose=True,
|
|
process=Process.sequential
|
|
)
|
|
|
|
result = data_crew.kickoff()
|
|
print("\nCrew Task Result (Streamable HTTP - Manual):\n", result)
|
|
|
|
except Exception as e:
|
|
print(f"An error occurred during manual Streamable HTTP MCP integration: {e}")
|
|
print("Ensure the Streamable HTTP MCP server is running and accessible.")
|
|
finally:
|
|
if mcp_server_adapter and mcp_server_adapter.is_connected:
|
|
print("Stopping Streamable HTTP MCP server connection (manual)...")
|
|
mcp_server_adapter.stop() # **Crucial: Ensure stop is called**
|
|
elif mcp_server_adapter:
|
|
print("Streamable HTTP MCP server adapter was not connected. No stop needed or start failed.")
|
|
```
|
|
|
|
## Considerações de Segurança
|
|
|
|
Ao utilizar o transporte HTTP Streamable, as melhores práticas gerais de segurança web são fundamentais:
|
|
- **Use HTTPS**: Sempre prefira HTTPS (HTTP Seguro) para as URLs do seu servidor MCP para criptografar os dados em trânsito.
|
|
- **Autenticação**: Implemente mecanismos robustos de autenticação se seu servidor MCP expuser ferramentas ou dados sensíveis.
|
|
- **Validação de Entrada**: Garanta que seu servidor MCP valide todas as requisições e parâmetros recebidos.
|
|
|
|
Para um guia abrangente sobre como proteger suas integrações MCP, consulte nossa página de [Considerações de Segurança](./security.mdx) e a documentação oficial de [Segurança em Transportes MCP](https://modelcontextprotocol.io/docs/concepts/transports#security-considerations). |