Skip to main content
Glama
enesjakozh
agentset-ai

Agentset

Official
by agentset-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Agentset MCP

MCP server for Agentset, an open-source platform for Retrieval-Augmented Generation (RAG). Designed for developers who want to build intelligent, document-based applications quickly and efficiently.

npm version License Build Status Downloads Size

Installation

using npm:

AGENTSET_API_KEY=your-api-key npx @agentset/mcp --ns your-namespace-id

using yarn:

AGENTSET_API_KEY=your-api-key yarn dlx @agentset/mcp --ns your-namespace-id

using pnpm:

AGENTSET_API_KEY=your-api-key pnpm dlx @agentset/mcp --ns your-namespace-id

Related MCP server: MCP-RAGNAR

Adding to Claude

{
  "mcpServers": {
    "agentset": {
      "command": "npx",
      "args": ["-y", "@agentset/mcp@latest"],
      "env": {
        "AGENTSET_API_KEY": "agentset_xxx",
        "AGENTSET_NAMESPACE_ID": "ns_xxx"
      }
    }
  }
}

Tips

Passing namespace id as an environment variable

AGENTSET_API_KEY=your-api-key AGENTSET_NAMESPACE_ID=your-namespace-id npx @agentset/mcp

Passing a custom tool description

AGENTSET_API_KEY=your-api-key npx @agentset/mcp --ns your-namespace-id -d "Your custom tool description"

Passing a tenant id:

AGENTSET_API_KEY=your-api-key npx @agentset/mcp --ns your-namespace-id -t your-tenant-id

API Reference

Visit the full documentation for more details.

Available Tools

1 tool
knowledge-base-retrieveA

Look up information in the Knowledge Base. Use this tool when you need to:

  • Find relevant documents or information on specific topics

  • Retrieve company policies, procedures, or guidelines

  • Access product specifications or technical documentation

  • Get contextual information to answer company-specific questions

  • Find historical data or information about projects

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesThe query to search for data in the Knowledge Base
topKNoThe maximum number of results to return. Defaults to 10.
rerankNoWhether to rerank the results based on relevance. Defaults to true.

TDQS

A3.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description fully carries the burden of disclosing behavior. It only describes basic functionality without addressing side effects (none expected but not stated), read-only nature, error handling, or performance characteristics. For a retrieval tool, the description should at least imply idempotency or lack of mutations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and efficiently uses a bulleted list for clarity. The opening sentence is slightly generic, but overall it is well-structured and not verbose. Every line adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers common use cases but lacks information about the return format (no output schema) and potential errors. For a simple retrieval tool, it is partially complete, but missing output schema details and edge case handling reduces completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds no additional detail beyond the schema's parameter descriptions. It does not explain the implications of rerank or topK further, nor does it provide usage examples for parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Look up information in the Knowledge Base.' It provides a specific verb ('retrieve') and resource ('Knowledge Base'), and lists concrete use cases like finding documents, policies, and product specs. Since there are no sibling tools, no differentiation is needed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs when to use the tool via a bulleted list of scenarios (e.g., 'Find relevant documents,' 'Access product specifications'). It provides clear context but does not mention when not to use it or alternatives, which is less critical given no sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedknowledge-base-retrieve
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is no possibility of confusion or overlap. The tool's purpose is clearly defined as knowledge base retrieval, making selection unambiguous.

Naming Consistency5/5

With a single tool named knowledge-base-retrieve, there is no inconsistent naming pattern. The name is descriptive and predictable, though hyphenated rather than snake_case or camelCase.

Tool Count3/5

One tool is borderline: it is sufficient for a simple read-only knowledge base retrieval service, but the 'Agentset' server name suggests a broader scope that is not reflected by a single tool.

Completeness3/5

The tool covers retrieval well, but there are no create, update, delete, or list operations. For a purely read-only knowledge base this may be sufficient, but for a general knowledge base or an agent set, the surface is incomplete.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • ickyMCP

    dl1683
    A
    license
    Not graded
    quality
    D
    maintenance
    RAG-powered document search server that enables semantic search across large collections of legal and business documents (PDF, Word, Excel, PowerPoint) using local embeddings with no API costs.
    4
    MIT

  • MCP-RAGNAR

    bixentemal
    A
    license
    Not graded
    quality
    D
    maintenance
    A local RAG server that enables document indexing and sentence window retrieval across multiple file formats like PDF, MD, and DOCX. It supports both local Hugging Face models and OpenAI embeddings for efficient context-aware querying through the Model Context Protocol.
    GPL 3.0

  • local-rag-mcp-server

    nilab-llc
    F
    license
    Not graded
    quality
    D
    maintenance
    A fully offline local RAG server that utilizes ChromaDB and Ollama to index and query PDF, text, and Markdown documents. It allows users to manage local knowledge bases and perform semantic searches with AI-generated responses.
    -

  • rag-mcp

    Kamalesh-Kavin
    F
    license
    A
    quality
    D
    maintenance
    Enables indexing local documents (PDF, Markdown, text, code) into a knowledge base and querying them via semantic search using local embeddings, all running privately on your machine.
    4
    -

Appeared in Searches