Copus MCP Server

MCP server for searching human-curated content recommendations on Copus

Local serverstdioPython

What is the Copus MCP server?

MCP server for searching human-curated content recommendations on Copus. That is what the copus mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

An MCP (Model Context Protocol) server that allows AI assistants to search and retrieve human-curated content recommendations from Copus.

Each curation includes: - Curator's personal note — Why they recommend this - Curator credentials — Why they're qualified to recommend this - Original source URL — The actual content being recommended - AI-enhanced metadata — Key takeaways, target audience, problem solved - Engagement metrics — Views, saves, comments from the community

The tools it exposes

The server publishes 4 tools. What each one is for:

  • Cursor — Add to your Cursor MCP configuration (.cursor/mcp.json in your project or global settings):
  • search_curations — The search_curations tool exposed by this server
  • get_curation — The get_curation tool exposed by this server
  • Testing — The Testing tool exposed by this server

Getting it running

The server ships on npm as copus-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Copus's toolset — Cursor, search_curations, get_curation and 1 more — is a fair guide to whether it matches your workflow. It is maintained by copus-io; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Copus's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
CursorAdd to your Cursor MCP configuration (.cursor/mcp.json in your project or global settings):
search_curationsThe search_curations tool exposed by this server.
get_curationThe get_curation tool exposed by this server.
TestingThe Testing tool exposed by this server.

How to install the Copus MCP server

{
  "mcpServers": {
    "copus": {
      "command": "npx",
      "args": ["copus-mcp-server"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Copus to Cursor.
  • Use Copus to search curations.
  • Use Copus to get curation.

Frequently asked questions

It connects Copus to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Cursor, search_curations, get_curation, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Copus directly.