Smithery vs StackOne

Smithery

Service tokens can be limited by namespace, resource, operation and connection metadata, with a lifetime of at most 24 hours. No terms of service, rate limits or SLA were found, the pricing page could not be read, and the newest client release is from 20 July 2026.

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.

Smithery

1. Keep the API key on the backend and hand an agent a service token limited to connections with read and execute and a metadata match
2. Create connections with PUT /connect/{namespace}/{connectionId}, which is an upsert, and check status.state before calling a tool
3. On auth_required or input_required, send the person to setupUrl, then retry with the same connectionId
4. Tool names on the namespace MCP endpoint are prefixed with the connection ID, such as user-123-github.search_repositories
5. Do not rely on smithery skill commands. Version 1.1.1 of the CLI removed them

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