Skip to main content
Glama

Server Details

Nifra docs, runnable examples, and API types as an MCP server for any AI assistant.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
nifrajs/nifra
GitHub Stars
2
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 7 tools

Disambiguation4/5

Each tool targets a distinct artifact type: prose docs (nifra_docs), copy-paste snippets (nifra_example), declaration text (nifra_types), guided steps (nifra_learn), and symptom-based diagnosis split by domain (nifra_frontend vs nifra_runtime). The two closest pairs are nifra_example/nifra_gallery (both examples) and nifra_frontend/nifra_runtime (both symptom diagnosis), but each description explicitly states the boundary, so an agent can pick correctly with careful reading.

Naming Consistency5/5

Every tool uses the same nifra_<noun> namespace prefix with a short, lowercase suffix (docs, example, types, learn, gallery, frontend, runtime). The only minor wrinkle is 'learn' being a verb among nouns, but the pattern is unmistakable and predictable.

Tool Count5/5

Seven tools is well within the sweet spot and each one covers a genuinely different retrieval or diagnostic modality. Nothing feels redundant or padded; the gallery and examples are the only pair that could arguably be merged.

Completeness4/5

The surface covers search, runnable code, exact type declarations, onboarding flow, cross-adapter client debugging, and runtime-difference debugging, which is strong coverage of a docs/knowledge server. Minor gaps exist around version/migration lookups and deployment-specific troubleshooting, but those partly fall under docs/examples/learn.

Available Tools

7 tools
nifra_docsA
Read-onlyIdempotent
Inspect

Search nifra's framework documentation and get back ONLY the matching sections - auth, uploads, ISR, WebSockets, loaders, deployment, anything. Call with no query for the cheap section index; pass query (e.g. "isr revalidate") for the top matching sections. Use this instead of reading llms-full.txt (~150 KB) whole. For the EXACT TypeScript of a type/interface/function, call nifra_types instead (don't read .d.ts files).

Inputs: limit, query.

nifra_exampleA
Read-onlyIdempotent
Inspect

Get a verified, copy-pasteable Nifra code example for a task - auth route, file upload, ISR page, loader/action, typed client, SSE, deployment, and more. Every snippet is typechecked against the installed Nifra version, so it compiles as-is. Returns code as text for direct use. Call with no query for the grouped index; pass query (e.g. "protected route", "upload", "isr revalidate") for matching snippets.

Inputs: limit, query.

nifra_frontendA
Read-onlyIdempotent
Inspect

Diagnose a client-side Nifra problem by symptom across every adapter (React, Preact, Solid, Vue, Svelte, and vanilla). Returns the likely cause, a concrete fix, and how to verify it. Covers the Nifra server/client seam, hydration mismatches, duplicated framework runtimes, loader-data typing, and adapter-specific reactivity guidance. Call with no args for the index; pass symptom (e.g. "hydration mismatch", "value stopped updating") and/or adapter to filter.

Inputs: limit, adapter, symptom.

nifra_learnA
Read-onlyIdempotent
Inspect

Walk the guided path to build a nifra app end to end - an ORDERED sequence (create → page route → loader → typed API → typed client → auth → background jobs → deploy), not the random-access search of nifra_docs/nifra_example. Call with no args for the step index; pass step: N for that step's goal, how to do it (which tool emits the correct artifact), and how to verify it. Use it when scaffolding a new app or learning nifra's flow - each step composes the other nifra_* tools.

Inputs: step.

nifra_runtimeA
Read-onlyIdempotent
Inspect

Explain a behavior that differs between Bun, Node, Deno and Cloudflare Workers by symptom. These are runtime behaviors, not Nifra's: request-target and Host handling, pipelining, JSON content-type, engine error messages, recursion depth, .env loading, and runtime-specific APIs. Returns what each runtime does, the fix (and the Nifra option that decides it when there is one), how to verify it, and the versions it was measured on. Call with no args for the index; pass symptom (e.g. "path guard skipped", "env var undefined") and/or runtime to filter.

Inputs: limit, runtime, symptom.

nifra_typesA
Read-onlyIdempotent
Inspect

Get the exact TypeScript declaration of any exported @nifrajs/* symbol - interface, type, class, function, or const. Each signature is generated from the package's built .d.ts and returns the complete declaration rather than prose. Pass name for an exact symbol (e.g. "RateLimitStore", "RouteSchema", "Context", "rateLimit"); pass query to search by keyword; omit both for the per-package index of names. A name lookup is always the complete declaration; a query returns a one-line summary plus the signature, collapsing an oversized body - pass full: true to override.

Inputs: full, name, limit, query.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      C
      quality
      D
      maintenance
      An MCP server that exposes Discord bot actions as tools for LLM clients.
      29
      1
      -
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      AST-aware code exploration MCP server for AI agents, optimized for token efficiency.
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.