nectr-mcp

An MCP server for nectr, the markdown library for your LLMs.

It lets a model search your library, read any saved page as clean markdown, save new pages, and list your projects. You don't need to paste links into the chat.

• Search: a model can't guess your permalinks, but it can call search_library("pricing page").

• Private pages: pages you haven't shared have no working public link, but your key can still read them.

• Saving: "save these docs and keep them current" becomes one step, and nectr re-crawls them on your plan's schedule.

• Freshness: every read says when the page was last fetched.

Setup

1. In nectr, open Settings → API keys and create a key. It starts with nct_.

2. Add the server to your MCP client's configuration. Most desktop and editor clients use an mcpServers block like this:

{
  "mcpServers": {
    "nectr": {
      "command": "npx",
      "args": ["-y", "nectr-mcp"],
      "env": {
        "NECTR_API_KEY": "nct_your_key_here"
      }
    }
  }
}

3. Restart the client. The four tools below should appear.

Node.js 20 or newer is required.

Related MCP server: data-olympus MCP server

Tools

There is deliberately no delete. A model that could delete your library by misreading a request isn't worth the convenience.

Search returns summaries rather than bodies so that looking around your library doesn't fill the model's context. It reads a full page only when it chooses to.

Limits and errors

The server uses the same developer API as any other script, so your plan's limits apply unchanged. Errors are worded so a model knows whether to retry:

Security

Your API key is stored in plain text in your MCP client's config file. That's normal for MCP servers, but anyone who can read that file can use the key.

• Create a dedicated key for each client, so you can revoke one without breaking the others.

• If a key leaks, delete it under Settings → API keys in nectr. It stops working immediately.

• This server only ever reads and adds pages. The key itself is broader: it has the same access to the nectr API as your account, deletion included, so treat it like a password.

Development

npm install
npm run typecheck
npm test
npm run build
NECTR_API_KEY=nct_... node dist/index.js   # speaks MCP over stdio

The tests run against a fake nectr API (test/fake-api.ts) and through a real MCP client over an in-memory transport (test/server.test.ts).

License

MIT