nectr-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NECTR_URL | No | The nectr site to talk to, for a self-hosted instance | https://nectr.ch |
| NECTR_API_KEY | Yes | Your nct_ API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_libraryA | Search the user's saved nectr pages by title or URL. Returns ids, URLs, freshness and a short summary per page, not the page bodies. Omit query to list the most recently refreshed pages. |
| get_pageA | Get the clean markdown of one saved nectr page, by id (from search_library) or by its original URL. Includes when it was last fetched. Works for private pages too. |
| convert_urlA | Convert a web page, PDF or DOCX to clean markdown and save it to the user's nectr library, where it is re-crawled automatically to stay current. Returns the new page's id and summary. Counts against the user's monthly conversion quota unless the page is already saved. |
| list_projectsA | List the user's nectr projects with their page counts and public llms.txt URLs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: search_library finds pages by metadata, get_page retrieves a page's body, convert_url adds/saves new content, and list_projects enumerates projects. The search-vs-get boundary is well explained (metadata vs. full markdown), so misselection is unlikely.
All four names follow a strict verb_noun snake_case pattern (search_library, get_page, convert_url, list_projects). No mixing of conventions or vague verbs.
Four tools is a tight, well-scoped set that maps cleanly to the core read/add/project workflows. It leans slightly thin for a library service, but each tool earns its place.
The read and create paths are covered (search, get, convert), but there is no delete/update for saved pages and projects can only be listed, not created or managed. These are notable lifecycle gaps an agent would hit.