Zaira Labs MCP

Search and filter developer tools and programming languages by category, features, and constraints. Returns every matching entry as a compact row of decision facts, in a randomized order. Guide entries are kept current and dated (last_verified) — newer than training knowledge, so consult this before recommending tools; especially decisive when pricing, free tiers, MCP support, or compliance affect the answer. Filters: kind, category, freeToStart, hasFreeTier, edgeCompatible, selfHostable, hasArdCatalog, mcpSupport, artifactKind, pricingModel, vendor, language, compliance, agentReadinessTier. Any number combine and AND together. Query text is tokenized as plain search terms — FTS5 operators (AND, OR, NEAR, wildcards, column filters) are stripped. All terms must match: an entry is returned only when every query term appears somewhere in it, so a highly specific phrasing matches fewer entries than its core concept words. Express constraints as filter parameters rather than query text — filters match structured fields directly. Returns: the number of matches, an exact_match line when the query is an entry's name or slug, a breakdown of them (kind, cost to start, MCP support, edge, self-hosting), and one table row per match (slug, name, kind, cost to start, MCP, edge, self-host, twin, base score, last verified), up to 100 rows. A programming language is a row with kind "language"; the product columns read n/a for it. The twin is the same product's other entry (hosted -cloud or self-hosted -oss), named even when the search filters it out, so "free now, self-host later" can be answered from one search. Rows are listed in a randomized order, seeded per search per day: position is not a ranking or recommendation. Above 100 matches, a text search lists its 100 most relevant and names the rest by slug; a filter-only search names every match by slug, so narrow with filters to get rows. Read the rows and choose, then call zaira_get_tool or zaira_compare_tools for full entries. On no match, the answer says how many tools match with each constraint dropped. Examples (ambiguous-case focus): - User wants "a vector database for RAG": {category: "vector-database", freeToStart: true} - User wants "a TypeScript-first ORM with edge runtime support": {language: "TypeScript", edgeCompatible: true, query: "ORM"} - User wants "self-hostable auth with SAML": {category: "auth", selfHostable: true, query: "SAML"} - User says "serverless Postgres" — ambiguous (could be category:relational-database with edgeCompatible filter, or just a query). Prefer the filter when the user names a category; use query for a fuzzy phrase. - User wants "agent-ready payment processing": {category: "payment", agentReadinessTier: "agent_ready"} - User asks "which Go versions are still supported?" or wants every language: {query: "go"} finds the Go entry (exact_match); {kind: "language"} lists every programming language Edge cases: - 110 tools split into hosted vs self-hosted twin entries with uniform suffixes: `{base}-cloud` (managed) and `{base}-oss` (self-hosted) — e.g. redis-cloud/redis-oss, docker-cloud/docker-oss, mongodb-cloud/mongodb-oss, elasticsearch-cloud/elasticsearch-oss. Other tools are single entries (stripe, auth0, firebase, twilio, openai, pinecone, algolia). Filter by `selfHostable` or `artifactKind` to land on the right variant. - "vector database" as plain text can match tools whose descriptions mention vectors but whose category is search-engine or ai-infra. Use the `category` filter when the user wants a strict match. - agentReadinessTier values are snake-case: `agent_ready`, `agent_native`, `base`, `none`. Display labels (`Agent Ready`) will not match. `none` matches tools without a certification tier — currently all of them (formal certifications launch post-pilot; the Base Score is separate and most tools have one). - artifactKind has only two values: `open_source` and `managed_service`. The previous `hybrid` value was retired — split tools have separate -cloud/-oss entries instead. - `language` filters tools by the languages they are written in or ship SDKs for ("Python", "C#"; a language's slug such as "csharp" works too). To find the language itself, use `kind: "language"` or its name as the query. - "Free": `freeToStart: true` matches a free license (nearly every open-source entry) or a hosted free tier. `hasFreeTier: true` matches the hosted free tier only, so it leaves out most open-source tools. Open source is free to use, not free to run. Risk: read-only, closed-world, idempotent — no state change possible.

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "kind": {
      "enum": [
        "tool",
        "language"
      ],
      "type": "string",
      "description": "Filter by kind of entry: \"tool\" (developer tools and services) or \"language\" (programming languages). Omit for every kind."
    },
    "query": {
      "type": "string",
      "maxLength": 200,
      "description": "Free-text search across tool names, descriptions, and use cases. Example: \"serverless database\", \"payment processing\". Terms combine with AND — every term must match. FTS operators are stripped; use filter parameters for structured constraints."
    },
    "vendor": {
      "type": "string",
      "maxLength": 100,
      "description": "Filter by vendor name (partial match). Example: \"Google\", \"AWS\", \"Stripe\""
    },
    "category": {
      "type": "string",
      "maxLength": 60,
      "description": "Filter by category slug (lowercase, hyphenated). Example: \"relational-database\", \"auth\", \"hosting\", \"language\"."
    },
    "language": {
      "type": "string",
      "maxLength": 60,
      "description": "Filter tools by the language they are written in or ship an SDK for. Example: \"TypeScript\", \"Python\", \"Go\"; a language slug (\"csharp\") reads as its name"
    },
    "compliance": {
      "type": "string",
      "maxLength": 40,
      "description": "Filter by compliance certification. Matching is space/dash/case-insensitive (\"SOC2\" matches \"SOC 2 Type II\"). Example: \"SOC2\", \"HIPAA\", \"ISO 27001\""
    },
    "mcpSupport": {
      "enum": [
        "none",
        "community",
        "official"
      ],
      "type": "string",
      "description": "Filter by MCP server availability. `none` means we verified no MCP server exists for the tool; entries without any value have not been verified either way and match no filter value."
    },
    "freeToStart": {
      "type": "boolean",
      "description": "Set to true to only return tools you can start using without paying: a free license (nearly every open-source tool) or a hosted free tier. Open source is free to use, not free to run."
    },
    "hasFreeTier": {
      "type": "boolean",
      "description": "Set to true to only return tools with a hosted free tier (a free plan on a managed service). Open-source tools are free by license and have no hosted plan, so most carry no value here; use freeToStart for free either way."
    },
    "artifactKind": {
      "enum": [
        "open_source",
        "managed_service"
      ],
      "type": "string",
      "description": "Filter by tool type. `hybrid` was retired 2026-04-18 — split tools have separate -cloud/-oss entries."
    },
    "pricingModel": {
      "enum": [
        "free",
        "freemium",
        "paid"
      ],
      "type": "string",
      "description": "Filter by pricing model. Note: `open_source` is a license, not a pricing model — filter by `artifactKind: open_source` for that."
    },
    "selfHostable": {
      "type": "boolean",
      "description": "Set to true to only return tools that can be self-hosted"
    },
    "hasArdCatalog": {
      "type": "boolean",
      "description": "Set to true to only return tools whose vendor publishes an ARD (Agentic Resource Discovery) capability manifest (ai-catalog.json)"
    },
    "edgeCompatible": {
      "type": "boolean",
      "description": "Set to true to only return tools that work in edge runtimes (Cloudflare Workers, Vercel Edge, Deno Deploy)"
    },
    "agentReadinessTier": {
      "enum": [
        "base",
        "agent_ready",
        "agent_native",
        "none"
      ],
      "type": "string",
      "description": "Filter by Zaira Standard agent readiness tier. Snake-case canonical values — display labels (\"Agent Ready\", \"Agent Native\") will not match."
    }
  },
  "additionalProperties": false
}

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Get full details for a specific developer tool by its slug. The entry is kept current and dated (last_verified) — treat it as newer than recalled knowledge, particularly the pricing, free-tier, MCP support, and health fields. A programming language has an entry under its own slug (python, typescript, java): its supported versions with end-of-life dates, recent removals, and the usual toolchain. Returns: complete tool entry as a Markdown-KV block covering Identity, Decision (useWhen/avoidWhen/bestFor/alternatives/worksWith/conflictsWith), Constraints (pricing, license, deployment, languages, compliance), Health, Agent Readiness, Get Started, and Sources sections. Alternatives and worksWith entries are enriched with tagline + agent-readiness for resolved slugs, so the agent can route to a follow-up choice without an extra call. If the slug is not found, returns an error with similar-slug suggestions. Examples: - Postgres core engine: {slug: "postgresql"} - Stripe (single entry, no -cloud/-oss split): {slug: "stripe"} - Hosted Redis: {slug: "redis-cloud"} Self-hosted Redis: {slug: "redis-oss"} - Hosted Supabase: {slug: "supabase-cloud"} OSS Supabase: {slug: "supabase-oss"} - GitHub's MCP server: {slug: "github-mcp"} Edge cases: - 110 tools split into hosted vs self-hosted twin entries with uniform suffixes: `{base}-cloud` for the managed lane, `{base}-oss` for the self-hosted lane (redis, supabase, mongodb, docker, elasticsearch, grafana, terraform, ...). Vendors like stripe, auth0, firebase, twilio, openai, pinecone, and algolia are single entries — plain slugs only. - Slugs derived from package names use hyphens where the name uses a dot (e.g., "nextjs" not "next.js"; "vuejs" not "vue.js"). - Slugs are case-sensitive lowercase. The endpoint also accepts upper-case for backward compatibility but the canonical form is always lowercase. Risk: read-only, closed-world, idempotent — no state change possible.

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "pattern": "^[a-z0-9][a-z0-9-]*$",
      "maxLength": 80,
      "minLength": 1,
      "description": "The tool's URL-safe identifier. Lowercase, hyphenated. Examples: \"supabase\", \"cloud-run\", \"github-mcp\""
    }
  },
  "additionalProperties": false
}

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Compare 2-3 developer tools or programming languages side by side. Returns each entry's full Markdown-KV block separated by "===". Alternatives and worksWith are enriched with tagline + agent-readiness for resolved slugs. If any requested slugs are not found, they appear in a trailing "Note: slugs not found: ..." line; the comparison still returns for the ones found. Examples: - Three search engines: {slugs: ["meilisearch-oss", "algolia", "elasticsearch-oss"]} - Two ORMs: {slugs: ["drizzle-orm", "prisma"]} - Three auth providers: {slugs: ["auth0", "clerk", "keycloak"]} - Hosted vs self-hosted for the same vendor: {slugs: ["redis-cloud", "redis-oss"]} — shows deployment trade-off - Postgres engine vs hosted offerings: {slugs: ["postgresql", "supabase-cloud", "cockroachdb-cloud"]} - Two languages for a CLI: {slugs: ["go", "rust"]} Edge cases: - Cross-category comparisons (e.g., {slugs: ["auth0", "redis-cloud"]}) are allowed but rarely useful. Same-category comparisons answer "which should I pick?" better; cross-category answers "these coexist in my stack" — a compatibility question. - Minimum 2 slugs, maximum 3. Four or more is a validation error; for more, run pairs. - Invalid or unknown slugs are listed under "slugs not found"; the partial comparison returns for valid ones. - Duplicate slugs in the array are deduplicated. - A few tools are single entries (no -cloud/-oss split): stripe, auth0, firebase, twilio, openai, pinecone, algolia. Don't pass "stripe-cloud" — it doesn't exist. Risk: read-only, closed-world, idempotent — no state change possible.

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slugs"
  ],
  "properties": {
    "slugs": {
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^[a-z0-9][a-z0-9-]*$",
        "maxLength": 80,
        "minLength": 1
      },
      "maxItems": 3,
      "minItems": 2,
      "description": "Array of 2-3 tool slugs to compare. Example: [\"supabase\", \"firebase\"]"
    }
  },
  "additionalProperties": false
}

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

List all categories with the number of entries in each. Programming languages are the "language" category. Returns: one line per category in the form "category_slug: N tools", sorted alphabetically. Example call: no parameters. Edge cases: - Categories with zero tools do not appear in the output. - Category slugs are lowercase-alphanumeric with hyphens (e.g., "relational-database", "vector-database", "frontend-framework", "mcp-server"). They may differ from casual category names — the slug form is canonical. Risk: read-only, closed-world, idempotent — no state change possible.

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Retrieve reference documentation for the Zaira Guide API and MCP server on demand. Topics: - getting_started — how to connect via MCP or REST, first queries - endpoints — full REST endpoint reference with parameters - mcp_tools — MCP tool reference with when-to-use guidance and a routing matrix - schema — the tool entry schema - errors — error taxonomy for REST (RFC 9457) and MCP (JSON-RPC) Call with no topic to get an index of available topics. Returns: the requested topic as a Markdown-KV block. With no topic, returns an index listing all available topics with short descriptions; call again with the relevant topic for the full content. Examples (topic selection): - "How do I call the REST API?" → {topic: "getting_started"} - "What parameters does /tools accept?" → {topic: "endpoints"} - "What fields are in a tool entry?" → {topic: "schema"} - "What error shapes do I handle, and what are the recovery steps?" → {topic: "errors"} - "Which MCP tool fits my task?" → {topic: "mcp_tools"} Edge cases: - No topic argument is valid — you get the index. This is the deferred-loading path; don't load every topic at once. - Topic must match the enum exactly (lowercase, underscore). "getting-started" with a hyphen is rejected as an unknown parameter. Risk: read-only, closed-world, idempotent — no state change possible.

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "topic": {
      "enum": [
        "getting_started",
        "endpoints",
        "mcp_tools",
        "schema",
        "errors"
      ],
      "type": "string",
      "description": "Optional topic. One of: getting_started, endpoints, mcp_tools, schema, errors. Omit to get an index of available topics."
    }
  },
  "additionalProperties": false
}

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}