WP Maps MCP integration for AI agents.
Connect AI agents to WP Maps through 10 structured actions, including get product, create products, and delete products. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 10
- 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 WP Maps integration exposes
The WP Maps Agent App exposes 10 provider-backed actions for location, marketing, and data work. Its current contract lets an authorized agent get one wp maps product by id, create one or more products in wp maps, and delete one or more wp maps products by id. 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 WP Maps account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real WP Maps capabilities.
Showing 10 of 10 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_productREADGet one WP Maps product by ID.
INPUTS: productId / language
create_productsWRITECreate one or more products in WP Maps.
INPUTS: products / language
delete_productsHIGH IMPACTDelete one or more WP Maps products by ID.
INPUTS: productIds / language
create_storesWRITECreate one or more stores in WP Maps.
INPUTS: stores / geocoder / language
delete_storesHIGH IMPACTDelete one or more WP Maps stores by ID.
INPUTS: storeIds / language
get_storeREADGet one WP Maps store by ID.
INPUTS: storeId / language
list_productsREADList all products in the connected WP Maps account.
INPUTS: language
list_storesREADList all stores in the connected WP Maps account.
INPUTS: language
update_productsWRITEUpdate one or more existing products in WP Maps.
INPUTS: products / language
update_storesWRITEUpdate one or more existing stores in WP Maps.
INPUTS: stores / geocoder / language
INPUT CONTRACTS
Know what the action needs before it runs.
get_product
productIdREQUIRED- WP Maps resource ID.
languageOPTIONAL- WP Maps language code used for localized fields, such as en_US.
create_products
productsREQUIRED- Products to create.
languageOPTIONAL- WP Maps language code used for localized fields, such as en_US.
delete_products
productIdsREQUIRED- Product IDs to delete.
languageOPTIONAL- WP Maps language code used for localized fields, such as en_US.
create_stores
storesREQUIRED- Stores to create.
geocoderOPTIONAL- Geocoder used when WP Maps resolves store coordinates.
languageOPTIONAL- WP Maps language code used for localized fields, such as en_US.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Product
Get one WP Maps product by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_productControl Create Products
Create one or more products in WP Maps. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_productsVerify with Get Store
Get one WP Maps store by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_storeSAFETY BOUNDARY
Operate WP Maps with explicit limits
- Authorize WP Maps 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_products` and `delete_stores` 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 WP Maps rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the WP Maps task completed successfully.
CONNECTION MODEL
API key
WP Maps private access token sent as access_token. Generate it from Configuration > Access Token: https://wpmaps.com/help/generate-wp-maps-api-access-token/.
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
- 4
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 2
- REVIEW SIGNALS
- 0
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 WP Maps.