Skip to main content
Nika ships with 105 MCP server entries in its catalog, aligned with the official MCP Registry schema (v2025-12-11). Each entry declares one or more local-install packages (npm / pypi / oci / cargo / mcpb) and/or remotes (streamable-http / sse endpoints). The workflow YAML invoke: verb references servers by id — Nika handles the rest.
Canonical source: crates/nika-catalog/data/mcp-servers.toml. Schema: nika/mcp-servers@1.0. Snapshot 2026-04-17 — grep -c '^\[\[servers\]\]' = 105. Build-time invariants (enforced in build.rs): unique ids, packages+remotes non-empty, known category, pricing ∈ , alias non-collision.

Overview

Servers

105 entries

Categories

17 — from anthropic to vectordb

Invocation

invoke: verb with server: <id>

How to invoke one

nika: v1
workflow: scrape-and-summarise

tasks:
  - id: crawl
    invoke:
      tool: "mcp:firecrawl/scrape"   # mcp:<server>/<tool> · server id from the catalog below
      args:
        url: https://example.com

  - id: summarise
    depends_on: [crawl]
    infer:
      model: anthropic/claude-sonnet-4-6   # <provider>/<name>
      prompt: "Summarise: ${{ tasks.crawl.output.content }}"
Verb invoke: is live in v. The Nika MCP catalog here is about workflows calling external MCP tools; Nika’s own agent-facing MCP server remains read-only (nika_check, nika_explain).

By category

Shipped by the Model Context Protocol project itself.
IdTitleRegistryIdentifier
filesystemFilesystemnpm@modelcontextprotocol/server-filesystem
memoryMemorynpm@modelcontextprotocol/server-memory
pdfPDFnpm@modelcontextprotocol/server-pdf
One-liners:
  • filesystem — read and write local files with path-based access control.
  • memory — persistent key/value memory store.
  • pdf — PDF text + structure extraction.

Distribution mix

Of the 105 entries:
  • 102 ship as npm packages (stdio via npx).
  • 1 ships as pypi (qdrant, runs via uvx).
  • 1 ships as oci (grafana, Go binary in a container image).
  • 1 is a pure remote endpoint (intercom, OAuth streamable-http).
The catalog’s registry_type field is validated at build time — runner is required for pypi packages and forbidden for every other registry type.

Authentication

Every server that needs credentials declares at least one [[servers.env_vars]] entry with is_secret = true or false. The env var names are visible in mcp-servers.toml — search for ^name = under your chosen server.
Nika never stores API tokens in workflow YAML. Secrets are read from environment variables at run time. Use nika doctor to see which provider variables are present or missing; it reports presence only and never prints values.

See also

Verbs

How invoke: routes to MCP tools + built-ins at runtime.

Builtins

The 63 engine-native tools under nika:*.

Providers catalog

LLM providers for the infer: and agent: verbs.

Error codes

MCP errors — the spec’s NIKA-MCP namespace (NIKA-MCP-001 server unreachable · NIKA-MCP-002 call failed); the engine’s internal diagnostics registry stays engine-side.