Skip to main content
Glama

nanograph-mcp

Build Nanograph datasources from Markdown or PDF corpora and serve them through MCP or a small HTTP/JSON wrapper.

What v1 supports

  • Ingest commands: nanograph-ingest seed --config ..., build, and smoke

  • Server commands: nanograph-mcp --registry ... and nanograph-http --registry ...

  • MCP tools: sources, source, documents, document, sections, search, passage

  • HTTP routes: GET /healthz, GET /datasources, GET /datasources/{name}, GET /datasources/{name}/documents, GET /datasources/{name}/documents/{document_id}, GET /datasources/{name}/documents/{document_id}/sections, POST /search, POST /passage, and POST /mcp

Use /healthz for health checks. Other application responses use the same schema-versioned envelope.

Search modes:

  • mode = "keyword" for all datasources

  • mode = "search" only for datasources built with embeddings enabled

Related MCP server: repocks

Quick start

nanograph-ingest smoke --config examples/corpus-markdown.toml
nanograph-http --registry examples/datasources-public.toml --host 127.0.0.1 --port 8765

The public registry example uses only home, exposure, and enabled for each datasource. Host-local path overrides such as database and config are outside the documented v1 contract.

Documentation:

A
license - permissive license
-
quality - not tested
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/quantumsoftwarelab/nanograph-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server