Precoro MCP integration
Procurement API for purchase orders, invoices, receipts, payments, suppliers, products, custom fields, and webhooks.
Sign in, add Precoro in Apps, then choose the account your AI can use.
Tools
| Name | Description |
|---|---|
list_recordsList Precoro purchase orders, invoices, receipts, payments, suppliers, products, contracts, locations, users, or custom fields. | List Precoro purchase orders, invoices, receipts, payments, suppliers, products, contracts, locations, users, or custom fields. |
get_recordGet one Precoro record. Precoro supports comma-separated document IDNs for full document detail endpoints. | Get one Precoro record. Precoro supports comma-separated document IDNs for full document detail endpoints. |
create_recordCreate Record in Precoro for API-supported resources such as suppliers, products, documents, payments, or custom fields. | Create Record in Precoro for API-supported resources such as suppliers, products, documents, payments, or custom fields. |
update_recordUpdate Record in Precoro for API-supported resources such as suppliers, products, documents, payments, or custom fields. | Update Record in Precoro for API-supported resources such as suppliers, products, documents, payments, or custom fields. |
patch_recordPatch Record in Precoro for API-supported resources such as suppliers, products, documents, payments, or custom fields. | Patch Record in Precoro for API-supported resources such as suppliers, products, documents, payments, or custom fields. |
delete_recordDelete a Precoro record when the selected API resource supports deletion. | Delete a Precoro record when the selected API resource supports deletion. |
submit_document_approval_actionSubmit a Precoro approval or rejection POST for a document waiting for approval. | Submit a Precoro approval or rejection POST for a document waiting for approval. |
Triggers
| Name | Description |
|---|---|
new_or_updated_recordPoll Precoro records using query filters and emit records whose created/modified timestamp advanced since the prior run. | Poll Precoro records using query filters and emit records whose created/modified timestamp advanced since the prior run. |
webhook_eventReceive Precoro webhooks configured in Precoro for supported add/update events. | Receive Precoro webhooks configured in Precoro for supported add/update events. |
Quick Start
import { WeavzClient } from '@weavz-io/sdk'
const weavz = new WeavzClient({ apiKey: 'wvz_...' })
const result = await weavz.actions.execute('precoro', 'list_records', {
workspaceId: '550e8400-e29b-41d4-a716-446655440000',
integrationAlias: 'precoro',
input: { /* ... */ },
})Related Integrations
Works well with
Frequently Asked Questions
Is there a Precoro MCP server through Weavz?
Yes. Add the Precoro integration to a Weavz workspace, enable the actions you need and connect any required account. Weavz provides the workspace MCP endpoint in Tool Mode or Code Mode. The catalog currently lists 7 Precoro actions.
What can an AI agent do with Precoro?
Available actions include List Records, Get Record, Create Record, Update Record, Patch Record, and more. Your workspace exposes only the actions you enable. The agent also needs the intended account access and any required input values.
How do I connect Precoro to Claude or ChatGPT?
Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add Precoro, connect the required account and review the enabled actions. Client availability and account requirements vary; adding the connector does not authorize every app automatically.
Can I use Precoro through an API or SDK?
Yes, supported actions can run through the Weavz REST API, TypeScript SDK or Python SDK. Configure a workspace and the required connections, use scoped access, and pass the intended end-user context when acting for a customer.
What authentication does Precoro require?
The catalog lists custom credentials for Precoro. Use Hosted Connect to authorize the intended account. Required permissions, provider app access and available connection methods depend on the integration.
How do I review sensitive Precoro actions?
Limit enabled actions, scope credentials to the intended user and configure Human Gates for the operations that need review. A matching policy can pause a send, record change or other sensitive action for an approver before execution.
What limits or costs apply to Precoro?
Weavz plan limits apply to the actions and resources you use. The external provider may also require an account, a paid plan, API credits or specific permissions, and may enforce its own rate limits. Check current Weavz pricing and the provider’s terms before rollout.
What Precoro triggers are available?
The catalog lists 2 triggers, including New or Updated Record, Webhook Event. Configure the trigger and your event handler before using incoming events to start work.
Connect Precoro in minutes
Get 20,000 free action executions every month. No credit card required.