Weave Code
Mcp Laravel Package
aureuserp/mcp
AureusERP MCP connects your ERP to AI assistants through the Model Context Protocol, exposing modules, records, and actions as tools Claude and other MCP clients can query and use—streamlining automation and natural-language access to your business data from a single Laravel package.
Aureus ERP MCP provides a Model Context Protocol server for Aureus ERP, letting AI assistants and MCP-compatible clients securely access ERP workflows, data, and actions through a standardized interface. Built for Laravel, it bridges your ERP backend with AI tooling using clean, extensible integrations.
- Exposes ERP capabilities as MCP tools and resources
- Seamless Laravel service provider and configuration
- Works with MCP-compatible clients such as AI assistants and IDEs
- Extensible architecture for custom tools and permissions
- Enables AI-driven ERP querying and automation
Frequently asked questions about Mcp
- How do I install aureuserp/mcp in a Laravel application?
- Install the package with Composer, register its service provider if auto-discovery is not enabled, and publish any provided configuration files. Run migrations or lifecycle commands only if the package documentation includes them. Then confirm how plugin installation is detected before activating ERP tools.
- What Laravel and PHP versions does aureuserp/mcp support?
- The provided context does not list exact Laravel and PHP version constraints, so check the package composer.json and Packagist metadata before installing. Because the package is at v1.0.3, test against your exact Laravel, PHP, and Composer dependency set. Pay particular attention to conflicts with your existing plugin registry or ERP modules.
- Why are my MCP tools not activating after upgrading to aureuserp/mcp v1.0.3?
- Version 1.0.3 introduces a behavioral gate where tools are activated only when their corresponding plugin is installed. Inventory existing tool activations and confirm that each related plugin is detected by the package. Test activation in staging before rolling the upgrade out to production.
- Does aureuserp/mcp v1.0.3 automatically deactivate existing active tools if their plugin is missing?
- The context indicates that tool activation now requires plugin installation but does not clearly state whether existing active tools are automatically revalidated or only blocked from new activation. Confirm this behavior in a non-production environment with representative data. If automatic reconciliation is not provided, plan an internal audit or script for existing activation records.
- How does aureuserp/mcp detect that an AureusERP plugin is installed?
- The package may rely on Composer package presence, a database record, a filesystem artifact, service registration, or a combination of these. The provided context does not specify the exact detection method, so review the implementation and test it against each plugin type you use. Unreliable detection can cause tools to be blocked or unexpectedly unavailable.
- How should I sequence plugin installation and MCP tool activation during deployment?
- Install or upgrade the relevant ERP plugins before activating their MCP tools. Reconcile existing tool activation records after deployment and update runbooks so plugin installation is always completed first. Add smoke tests that verify activation gating and plugin removal behavior.
- Can I connect Claude, Cursor, or custom AI agents to my Laravel ERP with aureuserp/mcp?
- Yes, the package is intended to expose ERP modules, data, and actions as MCP tools and resources for AI assistants and MCP-compatible clients such as Claude, Cursor, or custom agents. You should still review authentication, authorization, and network exposure before connecting production ERP data. Test each client against a staging ERP instance first.
- How do I test aureuserp/mcp tool activation and plugin removal in staging?
- Test activation, deactivation, plugin removal, and reinstall flows in a staging environment that mirrors production. Include checks for cached configuration, queued jobs, and multi-server deployments where plugin state may differ temporarily. Add smoke tests specifically for activation gating and blocked tools.
- What are the production risks of adopting aureuserp/mcp at v1.0.3?
- The main risk is that a patch release changed activation semantics by requiring plugin installation, which can break workflows where tools were activated independently. Other risks include unreliable plugin detection, stale activation state, deployment-order issues, and unclear behavior during plugin uninstall or deactivation. Pin versions, review release notes, and monitor for blocked or unexpectedly deactivated tools.
- What alternatives should I consider to aureuserp/mcp for exposing Laravel ERP data to MCP clients?
- Compare general-purpose Laravel MCP server packages, a custom MCP service provider, or direct API integrations against aureuserp/mcp. The AureusERP-specific package is most relevant if you need ERP module awareness and plugin-gated tool activation. Evaluate authentication, plugin detection, maintenance activity, and Laravel version support before choosing an alternative.
Weaver
How can I help you explore Laravel packages today?