A Model Context Protocol server that provides access to Typesense search capabilities
MCP Typesense Server becomes available to MCP clients through the mcp typesense server mcp server. A Model Context Protocol server that provides access to Typesense search capabilities.
A Model Context Protocol (MCP) server implementation that provides AI models with access to Typesense search capabilities. This server enables LLMs to discover, search, and analyze data stored in Typesense collections.
Once connected, the assistant can call these 10 tools directly:
typesense_query — Search for documents in Typesense collections with powerful filteringInput — Query text, collection name, search fields, filters, sort options, limittypesense_get_document — Retrieve specific documents by ID from collectionstypesense_collection_stats — Get statistics about a Typesense collectiontypesense_list_collections — List all available collections with their schemasFull — text search with customizable parametersResources — The Resources tool exposed by this serverTools — The Tools tool exposed by this serverPrompts — The Prompts tool exposed by this serverDebugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCPThe server is distributed via npm as @michaellatman/mcp-get, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. MCP Typesense Server sits in that group, and the shape of its toolset — typesense_query, Input, typesense_get_document among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| typesense_query | Search for documents in Typesense collections with powerful filtering |
| Input | Query text, collection name, search fields, filters, sort options, limit |
| typesense_get_document | Retrieve specific documents by ID from collections |
| typesense_collection_stats | Get statistics about a Typesense collection |
| typesense_list_collections | List all available collections with their schemas |
| Full | text search with customizable parameters |
| Resources | The Resources tool exposed by this server. |
| Tools | The Tools tool exposed by this server. |
| Prompts | The Prompts tool exposed by this server. |
| Debugging | Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script: |
{
"mcpServers": {
"typesense": {
"command": "npx",
"args": [
"-y",
"typesense-mcp-server",
"--host", "your-typesense-host",
"--port", "8108",
"--protocol", "http",
"--api-key", "your-api-key"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.