Quaderno MCP integration for AI agents.
Connect AI agents to Quaderno through 12 structured actions, including get account, create contact, delete contact, and calculate tax rate. Review authentica…
- ACTION CONTRACTS
- 12
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Quaderno integration exposes
The Quaderno Agent App exposes 12 provider-backed actions for finance and developer tools work. Its current contract lets an authorized agent retrieve the quaderno account identity and api endpoint for the api key, create a quaderno contact, and delete a quaderno contact permanently. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Quaderno account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Quaderno capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_accountREADRetrieve the Quaderno account identity and API endpoint for the API key.
create_contactWRITECreate a Quaderno contact.
INPUTS: contact
delete_contactHIGH IMPACTDelete a Quaderno contact permanently.
INPUTS: id
calculate_tax_rateREVIEWCalculate the Quaderno tax rate for an address and transaction details.
INPUTS: from_country / from_postal_code / to_country / to_postal_code / to_city
create_productWRITECreate a Quaderno product.
INPUTS: product
delete_productHIGH IMPACTDelete a Quaderno product permanently.
INPUTS: id
get_contactREADRetrieve one Quaderno contact by ID.
INPUTS: id
get_productREADRetrieve one Quaderno product by ID.
INPUTS: id
list_contactsREADList Quaderno contacts with optional search or processor ID filters.
INPUTS: q / processor_id
list_productsREADList Quaderno products with an optional search query.
INPUTS: q
update_contactWRITEUpdate a Quaderno contact. Fields not provided are left unchanged.
INPUTS: id / contact
update_productWRITEUpdate a Quaderno product. Fields not provided are left unchanged.
INPUTS: id / product
INPUT CONTRACTS
Know what the action needs before it runs.
create_contact
contactOPTIONAL- The Quaderno contact fields to create or update.
delete_contact
idOPTIONAL- The Quaderno object ID.
calculate_tax_rate
from_countryOPTIONAL- The seller's two-letter ISO country code.
from_postal_codeOPTIONAL- The seller's ZIP or postal code.
to_countryREQUIRED- The customer's two-letter ISO country code.
to_postal_codeOPTIONAL- The customer's ZIP or postal code.
to_cityOPTIONAL- The customer's city.
create_product
productOPTIONAL- The Quaderno product fields to create or update.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account
Retrieve the Quaderno account identity and API endpoint for the API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_accountControl Create Contact
Create a Quaderno contact. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contactVerify with Get Contact
Retrieve one Quaderno contact by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_contactSAFETY BOUNDARY
Operate Quaderno with explicit limits
- Authorize Quaderno with API key and grant only the provider access required by the selected actions.
- 6 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_contact` and `delete_product` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Quaderno rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Quaderno task completed successfully.
CONNECTION MODEL
API key
Quaderno API key used with HTTP Basic Auth. Create or view API keys in your Quaderno account: https://quadernoapp.com/users/api-keys
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 2
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Quaderno.