2,500+ MCP servers ready to use
Vinkius

PHC GO MCP Server for CrewAI 16 tools — connect in under 2 minutes

Built by Vinkius GDPR 16 Tools Framework

Connect your CrewAI agents to PHC GO through Vinkius, pass the Edge URL in the `mcps` parameter and every PHC GO tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="PHC GO Specialist",
    goal="Help users interact with PHC GO effectively",
    backstory=(
        "You are an expert at leveraging PHC GO tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in PHC GO "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 16 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
PHC GO
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

About PHC GO MCP Server

Connect your PHC GO enterprise ecosystem to your AI agent and manage operations, invoicing, and logistics through natural language commands natively.

When paired with CrewAI, PHC GO becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call PHC GO tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

  • Entity Management — Retrieve master data such as list_customers and natively create_customer directly from your chat context.
  • Inventory & Logistics — Pull active article sheets with list_products, or audit material counts instantly using list_stocks and list_warehouses.
  • Billing & Finance — Dynamically execute the create_document endpoint to issue invoices/estimates, and reconcile using list_current_accounts and list_taxes.
  • Sales Ecosystem — Quickly fetch configuration records like list_series and list_payment_methods to standardize business logic via intelligent agents.

The PHC GO MCP Server exposes 16 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect PHC GO to CrewAI via MCP

Follow these steps to integrate the PHC GO MCP Server with CrewAI.

01

Install CrewAI

Run pip install crewai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

03

Customize the agent

Adjust the role, goal, and backstory to fit your use case

04

Run the crew

Run python crew.py. CrewAI auto-discovers 16 tools from PHC GO

Why Use CrewAI with the PHC GO MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with PHC GO through the Model Context Protocol.

01

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

02

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

03

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

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

PHC GO + CrewAI Use Cases

Practical scenarios where CrewAI combined with the PHC GO MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries PHC GO for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries PHC GO, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain PHC GO tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries PHC GO against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

PHC GO MCP Tools for CrewAI (16)

These 16 tools become available when you connect PHC GO to CrewAI via MCP:

01

create_customer

Criar um novo cliente/entidade no PHC GO

02

create_document

Criar um novo documento comercial no PHC GO (fatura, orçamento, encomenda, etc)

03

create_product

Criar um novo artigo ou serviço no PHC GO

04

get_customer_details

Obter detalhes completos de um cliente/entidade pelo ID

05

get_document_details

Obter detalhes completos de um documento comercial (fatura, nota crédito, recibo, etc) incluindo linhas

06

get_product_details

Obter detalhes de um artigo/serviço pelo ID

07

list_current_accounts

Consultar a conta corrente de clientes (saldos e movimentos pendentes)

08

list_customers

Listar todas as entidades/clientes registados no PHC GO

09

list_documents

Listar documentos comerciais do PHC GO por tipo (FT=Fatura, NC=Nota Crédito, RC=Recibo, ORC=Orçamento, ECL=Encomenda, GR=Guia Remessa)

10

list_payment_methods

Listar métodos de pagamento configurados (Transferência, MB, MBWay, Cheque)

11

list_products

Listar todos os artigos e serviços registados no PHC GO

12

list_series

Listar séries de numeração de documentos (FT 2026/, NC 2026/, etc)

13

list_stocks

Consultar movimentos de stock. Opcionalmente filtrar por artigo

14

list_taxes

Listar taxas de IVA e impostos configurados no PHC GO

15

list_warehouses

Listar armazéns configurados para gestão de stock

16

search_customers

Pesquisar clientes por nome, NIF ou código

Example Prompts for PHC GO in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with PHC GO immediately.

01

"Check the available stock for 'Macbook Pro M3' across all warehouses."

02

"Create a new customer profile for 'Acme Corp' and fetch their assigned customer ID."

03

"Examine our outstanding current accounts from January to spot pending vendor debts."

Troubleshooting PHC GO MCP Server with CrewAI

Common issues when connecting PHC GO to CrewAI through the Vinkius, and how to resolve them.

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

PHC GO + CrewAI FAQ

Common questions about integrating PHC GO MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect PHC GO to CrewAI

Get your token, paste the configuration, and start using 16 tools in under 2 minutes. No API key management needed.