convez.ai
MCP ServerIntegração & APIsAvançado
waaseyaa

Waaseyaa MCP Server

waaseyaa/mcp

Endpoint MCP remoto para integrar ferramentas Waaseyaa em clientes AI

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP remoto em PHP que expõe ferramentas de agente Waaseyaa para clientes externos (Claude Desktop, Cursor, agentes customizados) via protocolo JSON-RPC. Implementa autenticação por token bearer, controle de capabilities por conta e dispatching de tools registradas com decorador `#[AsAgentTool]`, incluindo a família Bimaaji para introspecção e mutação de grafos de aplicação.

Instalação

$npx convez-ai waaseyaa/mcp

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
37%
Último commit
há 4 dias
Versão
—
Issues abertas
0
Contribuidores
2

Casos de uso

  • Expor ferramentas de agente Waaseyaa para Claude Desktop e Cursor
  • Integrar aplicações Waaseyaa com agentes AI customizados via MCP
  • Introspecção e mutação de grafos de aplicação através de agentes (Bimaaji)

Veredito

Solução técnica robusta e bem arquitetada para bridging entre agentes AI e ecossistema Waaseyaa, com modelo de capabilities granular. Requer compreensão profunda de MCP e stack Waaseyaa; não é plug-and-play, exige implementação customizada de autenticação e configuração em produção.

README

A tradução para o português deste README ainda está na fila.

waaseyaa/mcp

Layer 6 — Interfaces

Model Context Protocol (MCP) endpoint for Waaseyaa applications.

Exposes Waaseyaa's #[AsAgentTool]-registered tools to external MCP clients (Claude Code, Cursor, Claude Desktop, custom AI agents) over Streamable HTTP at /mcp. Authenticates requests via McpAuthInterface, then dispatches JSON-RPC payloads against a per-request AgentToolRegistryBridge constructed with the auth-resolved AccountInterface. Per-tool capability gating runs at the AbstractAgentTool::requireCapability boundary against the account's permissions.

Quick reference

  • Endpoint: POST /mcp (JSON-RPC; methods: initialize, ping, tools/list, tools/call).
  • Server card: GET /.well-known/mcp.json (MCP discovery).
  • Authentication: Authorization: Bearer <token> validated by McpAuthInterface::authenticate(). Default binding: BearerTokenAuth(tokens: []) (empty-token map). Production applications override by re-binding McpAuthInterface on the kernel-services bus or in an application provider.
  • Tool surface: every class carrying #[AsAgentTool] and implementing AgentToolInterface becomes a callable MCP tool with no per-tool MCP code.

Bimaaji tool family

The first first-party tool family surfaced through this package is Bimaaji, exposed via five #[AsAgentTool] adapters in packages/ai-agent/src/Tool/Bimaaji/:

Tool nameCapabilityPurpose
bimaaji_introspect_graphbimaaji.readFull application graph (six default sections + version).
bimaaji_introspect_sectionbimaaji.readSingle section (admin, entities, jsonapi, public_surface, routing, sovereignty).
bimaaji_propose_mutationbimaaji.mutateValidate a proposed schema mutation against the application graph.
bimaaji_generate_patchbimaaji.mutateGenerate a PatchSet from a validated mutation. Never writes to disk — the calling MCP client persists.
bimaaji_search_specsbimaaji.readSubstring search over docs/specs/*.md; returns {file, section_title, line_number, snippet} per match.

Capability model. bimaaji.read is intended to be broadly granted to authenticated MCP clients; bimaaji.mutate is opt-in per role/account. The framework does not grant either by default — the integrating application's permission stack does.

Example claude_desktop_config.json fragment (replace <token> with the bearer token your McpAuthInterface implementation expects):

{
  "mcpServers": {
    "waaseyaa": {
      "url": "https://your-host.example/mcp",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

Key classes

  • McpEndpoint — JSON-RPC dispatcher; constructs the per-request bridge with the auth-resolved account.
  • McpServerCard — server-card route controller (/.well-known/mcp.json).
  • McpRouteProvider — registers both routes through the package's McpServiceProvider.
  • McpServiceProvider — binds the McpAuthInterface default (BearerTokenAuth(tokens: [])); production overrides via re-binding.
  • Bridge\AgentToolRegistryBridge — adapts Waaseyaa\AI\Tools\ToolRegistryInterface to the MCP ToolRegistryInterface + ToolExecutorInterface contracts; constructed per-request by McpEndpoint::dispatch().

Canonical spec

See docs/specs/mcp-endpoint.md for the authoritative architecture documentation including the per-request bridge architecture, the Bimaaji MCP bridge section (shipped tool inventory, capability model, M-G → M3 transition rationale), and the post-WP01..WP03 file reference.

Legacy surface

The pre-M3 McpController + Tools/* + Cache/ + Rpc/* files remain in-place from the original entity/discovery/traversal/ editorial tool-class architecture, still test-covered via direct instantiation in tests/Integration/Phase14/AiMcpIntegrationTest.php. They are no longer reachable from HTTP routing (the foundation McpRouter was retired in M3 WP01). A future cleanup mission may delete them.

Ver o original no GitHub

Bom para

Relacionados