Shanone MCP Server - Shanone Documentation

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.

Remote MCP exposes 32 tools: one health check, four discovery/schema/execution tools, two connection tools, 13 skill tools, nine service/permission tools, and three Analytics tools.

Available tools

Tool	Purpose	Plans and billing
`shanone_health_check`	Check MCP connectivity, API-key authentication, and backend health. No provider credentials are tested.	Free+; non-billable
`shanone_search_tools`	Search tools with inline input schemas for top candidates. Fetch a schema separately only for schemaRef results; use list_service_tools for complete listings.	Free+; non-billable
`shanone_list_service_tools`	List tools for one service with pagination. Follow subsequent pages to retrieve the full list.	Free+; non-billable
`shanone_get_tool_schema`	Fetch an input schema for schemaRef results, or refresh a known schema.	Free+; non-billable
`shanone_list_connections`	List saved connections visible to the caller. Stored configuration is not proof that authentication still works.	Free+; non-billable
`shanone_check_connection`	Verify saved connections using read-only provider APIs. Omitting service checks all connected services, with pagination.	Free+; non-billable
`shanone_execute_tool`	Execute an integration tool. Inspect both the execution envelope and the provider result; completing a tool invocation does not by itself prove the provider operation succeeded.	Free+; per executed tool
`shanone_get_tool_usage`	Aggregate tool usage	Plus+; 1 on success
`shanone_search_tool_logs`	Search execution logs	Plus+; 1 on success
`shanone_get_tool_log`	Inspect one execution	Plus+; 1 on success
`shanone_list_skills`	List saved skills, newest first. The query is optional; an empty query lists your saved skills with pagination.	Plus+; billable on success
`shanone_get_skill`	Read a skill’s name, summary, and full instructions. The agent follows the instructions itself; this call does not execute the workflow.	Plus+; billable on success
`shanone_create_skill`	Create a reusable skill. All three fields must be non-empty. description and body are stored as summary and instructions.	Plus+; billable on success
`shanone_update_skill`	Update an existing skill. Only non-empty optional fields are changed; empty strings leave the existing values unchanged.	Plus+; billable on success
`shanone_delete_skill`	Permanently delete a skill.	Plus+; billable on success
`shanone_list_skill_files`	List additional files bundled with a skill, including paths and sizes. The main instructions are read with get_skill.	Plus+; billable on success
`shanone_read_skill_file`	Read a text file bundled with a skill. Binary files return a description instead of their contents; use the dashboard to view or download them.	Plus+; billable on success
`shanone_write_skill_file`	Create or overwrite a UTF-8 text file. Missing parent folders are created automatically.	Plus+; billable on success
`shanone_delete_skill_file`	Delete one file bundled with a skill.	Plus+; billable on success
`shanone_grep_skill`	Search skill files with a regular expression. Results include file paths and line numbers; narrow the pattern if results are truncated.	Plus+; billable on success
`shanone_create_skill_folder`	Create an empty skill folder. This is optional before writing files because write_skill_file creates parent folders.	Plus+; billable on success
`shanone_delete_skill_folder`	Delete a folder and all files and subfolders inside it. This operation cannot be undone.	Plus+; billable on success
`shanone_rename_skill_path`	Rename or move a file or folder. Moving a folder moves its contents. An existing destination is rejected rather than overwritten.	Plus+; billable on success
`shanone_list_services`	List registered service names, display names, and tool counts. No administrator role is required.	Free+; non-billable
`shanone_list_user_tool_permissions`	List a target user’s tool and service permission overrides.	Free+; non-billable
`shanone_set_user_tool_permission`	Allow or deny one tool for a target user. A tool override takes priority over a service override or role default.	Free+; non-billable
`shanone_set_user_service_permission`	Allow or deny the tools of a service for a target user, subject to individual tool overrides.	Free+; non-billable
`shanone_get_permission_summary`	Summarize a target user’s enabled and disabled services and tools.	Free+; non-billable
`shanone_batch_set_user_permissions`	Apply up to 500 service/tool permission operations in one call. Inspect each operation’s result; one failure does not abort the entire batch.	Free+; non-billable
`shanone_get_tool_parameter_policy`	Read the argument constraints configured for a target user’s tool. Tool access and allowed argument values are separate controls.	Free+; non-billable
`shanone_set_tool_parameter_policy`	Set or replace one field’s argument policy. Constraints are applied by the server during execution.	Free+; non-billable
`shanone_delete_tool_parameter_policy`	Remove the policy on one field. This does not change the tool’s allow/deny permission.	Free+; non-billable

API-key, user, and resource permissions apply separately from plan availability. Managing or inspecting another user’s permissions requires Root or delegated SA2 access.

Recommended workflows

Provider tools: search_tools (with inputSchema) → execute_tool. Fetch get_tool_schema only for schemaRef results or after list_service_tools.
Gmail accounts: list_connections → check_connection when needed → execute_tool with an explicit connection_id.
Skills (Plus+): list_skills → get_skill → the agent follows the instructions. Bundled files can also be listed, read, and searched.
Administration: list_services → set permissions or argument constraints → inspect get_permission_summary.

Usage and allowance

Administrative calls are recorded in Analytics without consuming billable allowance. Skills consume one Tool Call only on success. A connection check and its internal probes are non-billable, and only the parent call is counted. Provider execution follows the underlying tool’s normal billing rules. All parameters and errors · Setup

​Available tools

​Recommended workflows

​Usage and allowance

Available tools

Recommended workflows

Usage and allowance