hyperspell-mcp
OfficialSupports configuration through .env files for storing authentication tokens and feature flags when using the inspector.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hyperspell-mcp search my documents for quarterly sales reports"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Hyperspell MCP Server (deprecated)
This server is no longer maintained. Use the current MCP server instead:
npx -y @hyperspell/hyperspell-mcpSetup and usage: https://docs.hyperspell.com/advanced/mcp-overview
Available Tools
6 toolsAdd FileC
Add a file or website from a URL to Hyperspell.
Inputs: url (required).
Add MemoryC
Add a plain text document or memory to Hyperspell.
Inputs: text (required), title.
Get CollectionC
Get a list of all documents in a collection
Inputs: collection_name (required).
Get DocumentC
Get a document from a collection
Inputs: document_id (required).
List CollectionsB
Get a list of all collections on Hyperspell
Inputs: no named parameters.
Search HyperspellC
Search Hyperspell for documents and data.
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: adding content (files/memories), retrieving collections/documents, and searching. No overlap exists, as tools target specific resources and actions like 'Add File' vs. 'Add Memory' or 'Get Collection' vs. 'Get Document'.
Naming is mixed with inconsistent patterns: 'Add File' and 'Add Memory' use verb-noun but with capital letters, while 'Get Collection', 'Get Document', 'List Collections', and 'Search Hyperspell' use verb-noun with varying capitalization and one tool including the server name. This makes it readable but lacks a uniform convention.
With 6 tools, the count is well-scoped for a document management server, covering core operations like adding, retrieving, listing, and searching without being too sparse or bloated. Each tool earns its place in the workflow.
The toolset covers essential CRUD-like operations for a document repository: adding content, retrieving collections/documents, and searching. Minor gaps exist, such as no update or delete tools, but agents can likely work around this for basic usage without significant failures.
Maintenance
Related MCP Connectors
Connect your AI to all your data - 200+ sources, intelligently filtered, compliance-ready.
Build and run agents and automations across hundreds of apps using natural language.
Turn the web into structured, reliable, actionable enterprise data for AI Agents
Your personal data for AI — Telegram, bank, courses, Zoom & more, scoped to you.
Related MCP Servers
AlicenseAqualityCmaintenanceEnable AI agents to work reliably - giving them secure access to structured data, tools to take action, and the context needed to make smart decisions.85440MIT- FlicenseNot gradedqualityNot gradedmaintenanceUniversal AI API Orchestrator. 850 tools across 53 services under a single MCP interface. Connect Claude, GPT, or Gemini to Stripe, Slack, GitHub, LinkedIn, Cloudflare, Shopify, Twilio, and 46 more via natural language. $0.10/execution, no subscription. Patent Pending.274 npm5-
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to over 30 business tools like Gmail, Slack, and Airtable through a single unified interface. It enables users to perform actions across multiple platforms using natural language without managing individual API integrations.22 npmMIT
- AlicenseNot gradedqualityDmaintenanceA universal AI API orchestrator that connects to 17+ services (Stripe, Slack, GitHub, etc.) and enables natural language task execution, multi-step automation, and complex orchestration across them without coding.274 npm1MIT