Skip to main content
The three Analytics tools are added in the Node.js 0.7.0 / Python 0.4.0 source release. Remote deployment and npm/PyPI publication are separate steps. Check your endpoint’s tools/list for availability.
Shanone uses the Model Context Protocol (MCP) to give AI clients access to external services, saved skills, and permission management. Remote MCP exposes 32 tools.

​
Discover and execute tools

Instead of registering every provider API operation as an MCP tool, discover the operation you need:
  1. Use shanone_search_tools to discover an operation and its input schema. Use shanone_list_service_tools for full listings.
  2. If inputSchema is present, call shanone_execute_tool with an arguments object matching it.
Only fetch shanone_get_tool_schema before execution when the result contains schemaRef instead. Search includes schemas for the top three candidates by default, within a combined 24,000 UTF-8 byte budget. Set schema_limit from 0 to 5 to adjust this. When provider OAuth is required, follow the connection instructions in the execution result. For Gmail, select an account with shanone_list_connections and pass an explicit connection_id when executing. Use shanone_check_connection to verify whether stored connections still work.

​
Connection methods

Updated implementations use object arguments across all transports. Check tools/list for the actual contract of your endpoint and installed package version.
This update has been verified on the dev/akaso remote environment. Production rollout and npm/PyPI publication are separate release steps. Discovery/execution support starts with Node.js 0.6.0 and Python 0.3.0. If an older server advertises string arguments, follow its schema or switch to an updated endpoint.

​
Authentication and access control

Remote MCP requires an API key (Authorization: Bearer sh_..., or X-API-Key) and an organization ID (X-Org-Id, or the org_id query parameter). The organization ID identifies the organization being accessed. Configure SHANONE_API_KEY for a local proxy. Plan availability does not replace API-key scopes, user permissions, resource access, or provider connections. Managing other users’ permissions requires Root or delegated SA2 access.

​
Tool categories and billing

Free users can still discover all 13 skill tools, including their names, descriptions, and input schemas. The server checks the plan at execution time and returns PLAN_UPGRADE_REQUIRED before accessing skill data on Free. Non-billable tools are also recorded in Analytics. Connection verification counts one parent call, not each internal API probe. Provider execution is recorded under the actual provider tool name without adding a separate shanone_execute_tool count. “Billable” means consuming your plan’s Tool Call allowance, not necessarily an additional monetary charge. Tool catalog · All parameters and errors · Setup

​
Analytics MCP

The three Analytics tools require Plus or above and consume one Tool Call on success, including empty searches and each page. API keys authenticate the caller; user Analytics permissions authorize access. No Analytics-specific key scope or key reissue is required. Self is the default scope; organization reads also require analytics:Users, and payloads require analytics:ReadLogPayload. Aggregation, search, details, and permissions