StackOne vs Zapier MCP (agent actions)

StackOne

StackOne's MCP server signs each person in with OAuth, lets them grant individual accounts and actions, and by default exposes two search and execute tools in place of the full catalogue. Session token URLs carry the credential in the query string for a year by default, and the Consumption Schedule and pricing page disagree on whether failed calls are billed.

Zapier MCP (agent actions)

16 meta-tools in agentic mode, or managed mode with only the actions you pick. Connection tokens are long-lived and the docs allow them in the URL query string.

StackOne

1. Send Accept: application/json,text/event-stream on every MCP request to https://api.stackone.com/mcp, by POST only. Without it the server answers 406
2. In search_execute mode call {provider}_search_actions first and pass the returned action_id to {provider}_execute_action. Never hardcode action ids
3. Pass the API key as the Basic auth username with an empty password, and name the linked account in x-account-id
4. On 429 or 408 wait the seconds given in Retry-After. StackOne has already retried a provider's 429 up to five times within a 60-second request lifetime
5. On 412 read errorCode and details.statusReasons. AccountErrorStatus needs a person to re-authenticate the linked account

Zapier MCP (agent actions)

1. Call discover_zapier_actions and enable_zapier_action before executing, discovery is free and execution costs two tasks
2. Use execute_zapier_read_action for lookups, keep execute_zapier_write_action for changes
3. Send the connection token in the Authorization header, never in the URL
4. Count batch writes per item before starting, five rows is ten tasks