typesense-mcp-server
Provides an MCP (Model Context Protocol) server that lets an MCP client query a Typesense instance to perform searches against one or more Typesense collections, exposing a tool (typesense_search) that accepts typical Typesense search parameters and supports filtering/faceting plus pagination.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
TLS enforcement is not clearly stated beyond a configurable protocol env var; if set to http, traffic may be unencrypted. Auth is via a single Typesense API key without documented per-tool/per-tenant scoping. Secret handling best practices are not described (only that TYPESENSE_API_KEY has a default value in README, which is a potential insecure practice indicator). No additional MCP-layer authentication/authorization is documented.
⚡ Reliability
Best When
You need a simple, generic MCP tool for read-only Typesense querying with common search controls (query_by/filter_by/page/per_page).
Avoid When
You cannot provide a Typesense API key securely, or you require explicit, documented MCP tool schemas, error codes, and rate-limit behavior.
Use Cases
- • Integrate Typesense search into AI agents via MCP (e.g., Claude/Cursor)
- • Tool-based semantic/search workflows where the agent needs to query specific Typesense collections
- • Building agent-driven search experiences with filter expressions and pagination
- • Prototype a generic search tool across multiple Typesense collections
Not For
- • Bulk indexing or ingestion workloads
- • Applications needing write operations/updates (the described tool is for search/retrieval only)
- • Environments that require OAuth/SSO-based auth flows (only API-key-like auth is documented)
- • Hard multi-tenant environments that need strong per-user authorization and audit controls
Interface
Authentication
README documents a single Typesense API key configuration via env var. No additional MCP auth mechanism (e.g., client auth, per-request credentials) is described.
Pricing
No pricing information for the MCP server is provided; costs would depend on Typesense hosting and usage.
Agent Metadata
Known Gotchas
- ⚠ Ensure correct Typesense parameter formatting for filter_by (e.g., field:value, operators) because the tool forwards search parameters.
- ⚠ page is 1-based and per_page has a max (documented as max 100); agents should respect these bounds.
- ⚠ If TYPESENSE_PROTOCOL is set to https but the server is not configured for TLS, requests may fail; README defaults to http.
- ⚠ If query_by is omitted, it defaults to '*', which may increase load/cost and broaden search unexpectedly.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for typesense-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.