English Français العربية

Trove

Official registry Other

Trove MCP.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http trove 'https://gateway.pipeworx.io/trove/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "trove": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/trove/mcp"
        }
    }
}
NPM package @pipeworx/mcp-trove
Claude Code 
claude mcp add trove -e 'PIPEWORX_API_KEY=<your pipeworx_api_key>' -- npx -y @pipeworx/mcp-trove@0.2.0
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "trove": {
            "command": "npx",
            "args": [
                "-y",
                "@pipeworx/mcp-trove@0.2.0"
            ],
            "env": {
                "PIPEWORX_API_KEY": "<your pipeworx_api_key>"
            }
        }
    }
}

Environment variables

  • PIPEWORX_API_KEY secret Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-trove
  2. Tools
  3. Quick Start
  4. No MCP client? Call it over HTTP
  5. Standalone (no gateway account)
  6. Using with ask_pipeworx
  7. More
  8. License

mcp-trove

Trove MCP.

Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.

Tools

ToolDescription
searchSearch the Trove collection by keyword. Returns matching items with ids (pass an id to work), titles, creators/sources, dates and links. Requires your own free Trove API key, passed as _apiKey.
workFetch full details for one Trove item by id — a Trove work id (from search). Requires your own free Trove API key, passed as _apiKey.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "trove": {
      "url": "https://gateway.pipeworx.io/trove/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/trove/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1684+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/trove_search \
  -H 'Content-Type: application/json' \
  -d '{"query":"Australian Aboriginal art"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/trove_search. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "trove": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-trove"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-trove

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Trove data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Frequently asked questions

What is Trove?

Trove MCP.

How do I install Trove?

It runs as a remote server. In Claude Code: claude mcp add --transport http trove 'https://gateway.pipeworx.io/trove/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Trove need an API key?

Yes. It expects PIPEWORX_API_KEY, which you set in its configuration.

Is Trove open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Trove?

It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.