Read PHP Point of Sale items, sales, customers and 138 reports; manage customers, items, expenses. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"php-point-of-sale": {
"url": "https://php-point-of-sale.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"php-point-of-sale": {
"type": "http",
"url": "https://php-point-of-sale.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Store name and PHP Point of Sale API key.
The store name is the part before .phppointofsale.com in your store address. Create the key in the POS under Store Config → API Settings → Add API Key: choose Read for questions only, Read/Write to let the AI create or change customers, items and expenses. An employee scope limits the key to what that employee may do. Copy the key when it is shown (it appears only once). Your key is used only to call your store's API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Store name and PHP Point of Sale API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the PHP Point of Sale connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
phppos_list_locations | read | List locations List the store's locations (shops/warehouses) with name, address, phone, email, time zone and default tax rates, plus each location's registers (id and name). Use the location ids to filter sales, expenses, customers and reports. Payment-processor credentials and device settings are never returned. GET /locations. |
phppos_list_items | read | List items List or search inventory items with name, item number, category, supplier, prices and reorder level. Search by text, or by one field (name, item_number, product_id, supplier, tag_name...). GET /items. |
phppos_get_item | read | Get item One inventory item by id: prices, tax settings, category, supplier, tags, attributes, variations, tier pricing and per-location settings. GET /items/{id}. |
phppos_list_categories | read | List categories List item categories with their ids. Use the ids to filter items or to file a new item. GET /categories. |
phppos_list_item_kits | read | List item kits List item kits (bundles of items sold together) with their prices. GET /item_kits. |
phppos_list_sales | read | List sales List or search completed sales, by date range, customer (id or email) or location. verbosity: minimal (headline fields), medium (adds customer, totals, profit, location - the default here) or full (every line item, payment and tax). Suspended sales (layaways, estimates) are fetched with suspended_type. GET /sales. |
phppos_get_sale | read | Get sale One sale by id with line items, payments, taxes, customer and employee (verbosity full by default). GET /sales/{id}. |
phppos_list_receivings | read | List receivings List receivings (stock received from suppliers, purchase orders, transfers) with supplier, totals and items, by date range. GET /receivings. |
phppos_get_receiving | read | Get receiving One receiving by id: supplier, items, quantities, costs and payments. GET /receivings/{id}. |
phppos_list_customers | read | List customers List or search customers with contact details, tier, store-account balance, credit limit and loyalty points. Search by text or by one field (email, phone_number, first_name, last_name, account_number). GET /customers. |
phppos_get_customer | read | Get customer One customer by person id: contact details, tier, tax settings, balance, credit limit, points, notes and custom fields. GET /customers/{person_id}. |
phppos_list_suppliers | read | List suppliers List or search suppliers with contact details, company, account number and balance. GET /suppliers. |
phppos_get_supplier | read | Get supplier One supplier by person id. GET /suppliers/{person_id}. |
phppos_list_employees | read | List employees List employees with name, contact details, username, hire date, manager, commission and pay rate settings and assigned locations. Passwords and the permission maps are never returned. GET /employees. |
phppos_list_invoices | read | List invoices List customer invoices (money customers owe) or supplier invoices (money the store owes) with date, due date, status and amount. GET /invoices/customer or /invoices/supplier. |
phppos_list_expenses | read | List expenses List recorded expenses with type, description, date, amount, tax, payment type, category and location. GET /expenses. |
phppos_list_gift_cards | read | List gift cards List gift cards with number, description, remaining value, customer and whether inactive. GET /giftcards. |
phppos_get_gift_card | read | Get gift card One gift card by its card number (or id): remaining value, customer and status. GET /giftcards/{giftcard_number}. |
phppos_list_appointments | read | List appointments List appointments (bookings) with customer, employee, service, start and end time, optionally within a time window. GET /appointments. |
phppos_list_reports | read | List reports The catalog of the store's reports (138 of them: sales summaries, top sellers, inventory low/aging/summary, profit and loss, taxes, payments, employee, customer, supplier and store-account reports) with the inputs each accepts. Without `search` only the report keys are returned; with `search` (for example 'inventory' or 'profit') the matching reports are returned with their inputs. GET /reports. |
phppos_run_report | read | Run report Run one of the store's reports and return it (title, summary, detail rows); `paging.next_offset` is set when more detail rows remain. Report keys and their inputs come from phppos_list_reports (for example summary_sales, top_sellers, inventory_low, summary_profit_and_loss, summary_taxes, closeout). Typical inputs go in `params`: start_date, end_date, sale_type, location_ids (array), category_id, supplier_id, customer_id, employee_id. A scoped key needs the Reports module plus that report's view permission. GET /reports/{report_key}. |
phppos_create_customer | write | Create customer WRITE: create a customer in the store. Store-account balance, credit limit and loyalty points cannot be set here. Needs a Read/Write API key. Retrying creates a duplicate (check phppos_list_customers first). The store's 'new customer' webhook, if configured, fires. POST /customers. |
phppos_update_customer | write | Update customer WRITE: change fields of an existing customer; only the fields you pass are sent. Overwrites the current values. Needs a Read/Write API key. The store's 'edit customer' webhook, if configured, fires. POST /customers/{person_id}. |
phppos_create_item | write | Create item WRITE: create an inventory item (name required). Stock quantities are not set here. Needs a Read/Write API key. Retrying creates a duplicate (search with phppos_list_items first). The store's item webhooks, if configured, fire. POST /items. |
phppos_update_item | write | Update item WRITE: change fields of an existing item (for example its price, category or active state); only the fields you pass are sent. Overwrites the current values, and a price change applies to the next sale. Needs a Read/Write API key. The store's 'edit item' webhook, if configured, fires. POST /items/{item_id}. |
phppos_create_expense | write | Create expense WRITE: record an expense in the store's books (description, amount and date). It affects expense and profit-and-loss reports. Needs a Read/Write API key. Retrying records it twice (check phppos_list_expenses first). POST /expenses. |
phppos_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
phppos_request_feature | Request a missing feature Tell usefulapi that the user needs something the PHP Point of Sale tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
phppos_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on PHP Point of Sale (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. Returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
phppos_cancel_subscription | Cancel the Pro subscription Cancel the caller's PHP Point of Sale Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run phppos_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this PHP Point of Sale server only. Subscribe with phppos_upgrade (it returns a Stripe Checkout link). Cancel any time with phppos_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running phppos_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by PHP Point of Sale. The server calls the PHP Point of Sale API with your own PHP Point of Sale access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Store name and PHP Point of Sale API key. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Store name and PHP Point of Sale API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the PHP Point of Sale API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in PHP Point of Sale.
Yes, if you approve it. 5 of the 26 PHP Point of Sale tools can create or change data. The other 21 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this PHP Point of Sale server only. Cancel any time: Pro then runs to the end of the paid period. Run phppos_usage_status to see how many calls you used.
Ask the AI to run phppos_upgrade: it returns a Stripe Checkout link. To cancel, run phppos_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with phppos_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.