pfx

Provides access to Forterro Proffix Px5 data and actions via MCP for AI assistants.
  • other

2

GitHub Stars

other

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

You can securely connect AI assistants to Forterro Proffix Px5 using the Model Context Protocol (MCP). This MCP Server acts as a bridge that exposes Proffix data and actions to AI agents via a standardized, safe, JSON-RPC transport, enabling natural language queries, cross-system workflows, and automated reporting without exporting data manually.

How to use

You interact with the MCP Server through your AI client. Use natural language requests like asking for open invoices, retrieving customer lists, or generating sales reports. The MCP Server translates your requests into Proffix operations, executes them securely, and returns structured results or AI-optimized descriptions. You authenticate with an API key and your Proffix credentials, and the server handles the protocol handshakes and operation calls.

How to install

Prerequisites you need before installation: Node.js (for local bridge usage) and internet access. You will establish either a remote MCP URL or a local bridge script depending on your preferred setup.

Option 1: One-Click Installation (recommended for Claude Desktop users) ensures the fastest setup with minimal manual steps.

Option 2: Manual Installation (for advanced users or other MCP clients) provides a bridge-based approach that you host locally.

Additional setup notes

You will use a remote MCP server URL to connect to the pfx MCP service and provide your API key. When using a local bridge, you run a node-based bridge script that connects to the same MCP endpoint and passes your Proffix credentials securely.

Configuration and security

Use HTTPS for all communications. Store credentials securely and do not hard-code them in your client. The MCP server supports parameter-based authentication and does not keep long-lived sessions. Monitor API usage and enforce proper access control on the Proffix account used by the bridge.

Troubleshooting and examples

If you cannot see results, verify that the API key and Proffix credentials are correct, the MCP server URL is reachable, and the bridge script is running. For typical queries, start with simple requests like listing endpoints or retrieving addresses, then expand to more complex reports.

Available tools

initialize

Handshake between client and MCP server to exchange capabilities and protocol version.

tools/list

List all available Proffix operations exposed via MCP; requires authentication.

tools/call

Execute a Proffix operation with provided arguments and return the result.

proffix_search_endpoints

Fuzzy-search over 120+ Proffix endpoints to discover available actions.

proffix_call_endpoint

Call a specific Proffix API endpoint directly.

proffix_describe_endpoint

Retrieve documentation for a specified endpoint.

proffix_endpoints

Access all Proffix API endpoints such as addresses, items, orders, etc.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational