Hypertool MCP server

Read from the package source without running it. The installed server may list more.

• activate-persona

  Activate a specific persona with optional toolset selection. This tool orchestrates the complete persona activation workflow including validation, toolset application, and state management. Only one persona can be active at a time - activating a new persona will automatically deactivate the current one. Returns comprehensive activation results with detailed error handling and actionable suggestion

• add-tool-annotation

  Add contextual annotations to a tool in the current toolset to guide LLM usage. Annotations provide user-specific guidance, best practices, and usage notes that will be displayed with the tool's description. Example: {toolRef: {namespacedName: 'linear.create_issue'}, notes: [{name: 'team-selection', note: 'Always confirm team with user first'}]}

• build-toolset

  Build and save a custom toolset by selecting specific tools. Like assembling tools from a workshop - pick the exact tools you need for a specific task or workflow. You must specify which tools to include. Each tool must specify either namespacedName or refId for identification. Example: {name: 'dev-essentials', tools: [{namespacedName: 'git.status'}, {namespacedName: 'docker.ps'}], autoEquip: true

• deactivate-persona

  Deactivate the currently active persona and restore the previous system state. This tool performs complete cleanup including toolset restoration, MCP configuration reversion, and state clearing. Returns comprehensive deactivation results with detailed information about cleanup operations. If no persona is currently active, returns success with appropriate messaging.

• delete-toolsetwrite action

  Delete a saved toolset configuration

• enter-configuration-mode

  Switch the server to configuration mode for managing tools and toolsets. In this mode, you can access: list-available-tools (browse all discovered tools), build-toolset (create custom tool collections), list-saved-toolsets (view saved configurations), equip-toolset (activate a toolset), delete-toolset (remove configurations), get-active-toolset (check current status), and add-tool-annotation (add

• equip-toolset

  Equip a saved toolset configuration to filter available tools

• exit-configuration-mode

  Leave configuration mode and return to normal operational mode. This will hide configuration tools and restore access to your equipped toolset's tools (or show only navigation tools if no toolset is equipped). The server will automatically exit configuration mode when you successfully equip a toolset. Use this when you're done with configuration tasks and ready to use your tools.

• get-active-persona

  Get information about the currently active persona. Returns the active persona's configuration, toolset, activation metadata, and validation status. Returns null if no persona is currently active.

• get-active-toolset

  Get detailed information about the currently equipped toolset including availability status

• list-available-tools

  Discover all tools available from connected MCP servers. Returns structured data showing tools grouped by server for toolset creation. Tools can be referenced by 'namespacedName' (e.g., 'git.status') or 'refId' (unique hash). Example: Call with no parameters to see all tools organized by server with detailed metadata for each tool.

• list-personas

  List available personas with their validation status and metadata. Returns structured data showing all discovered personas with essential information for selection and activation.

• list-saved-toolsets

  List all saved toolset configurations with detailed information including server configurations and tool counts

• unequip-toolset

  Unequip the currently equipped toolset and show all available tools

• validate-persona

  Validate a specific persona's structure and configuration with comprehensive reporting. Performs multi-layer validation including YAML syntax, schema validation, business rules, tool resolution, and MCP config validation. Supports both persona folder paths and individual persona.yaml/yml file paths. Returns detailed validation results with actionable suggestions for fixing any issues found.

• Code scan385 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 345 days ago4/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Safety score

77/100

higher than 50% of 4,460 AI and agents servers

Tools

15

the typical AI and agents server has 6

Tools that change things

7%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

158

more than 95% of 2,711 AI and agents servers

Hypertool: common questions

Is Hypertool MCP server safe?

Mostly: it is graded B (77/100). Read the Hypertool safety report

How do I install Hypertool?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Hypertool need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Hypertool maintained?

The last commit was 378 days ago (2025-10-21). The latest release is v0.0.42.

How does Hypertool compare with other AI and agents MCP servers?

safety score 77/100 (higher than 50% of 4,460 AI and agents servers); tools 15 (the typical AI and agents server has 6); tools that change things 7% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.