Official Agentset MCP server that lets Claude retrieve cited knowledge-base results from an Agentset namespace through the `knowledge-base-retrieve` tool, with optional tenant scoping and custom tool descriptions.
The MCP server sends Claude's retrieval queries to the Agentset API using the configured API key and namespace., The `knowledge-base-retrieve` tool can return up to 100 results per call and can rerank results by relevance., Namespace and tenant selection control which indexed documents are searchable; review them before connecting a shared agent., API keys should be scoped, rotated, and stored only in the MCP server environment or a secret manager., Custom tool descriptions can influence when the model calls the retrieval tool, so review them before use in production workflows.
Privacy notes
Retrieved chunks can include private documents, product specs, policies, support content, internal procedures, historical project information, or customer-specific data., Retrieval queries, namespace IDs, tenant IDs, document chunks, citations, and tool outputs may be visible to the MCP client, model provider, Agentset logs, and application telemetry., Tenant IDs are useful for data segregation, but incorrect tenant or namespace configuration can expose the wrong knowledge base., Do not paste API keys, namespace IDs, tenant IDs, or retrieved private chunks into shared issue reports, screenshots, or repository files.
Author
Agentset
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
5 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, third-party handling.
4 areas
SafetyCredentials & tokensThe MCP server sends Claude's retrieval queries to the Agentset API using the configured API key and namespace.
SafetyGeneralThe `knowledge-base-retrieve` tool can return up to 100 results per call and can rerank results by relevance.
SafetyGeneralNamespace and tenant selection control which indexed documents are searchable; review them before connecting a shared agent.
SafetyCredentials & tokensAPI keys should be scoped, rotated, and stored only in the MCP server environment or a secret manager.
SafetyExecution & processesCustom tool descriptions can influence when the model calls the retrieval tool, so review them before use in production workflows.
PrivacyGeneralRetrieved chunks can include private documents, product specs, policies, support content, internal procedures, historical project information, or customer-specific data.
PrivacyThird-party handlingRetrieval queries, namespace IDs, tenant IDs, document chunks, citations, and tool outputs may be visible to the MCP client, model provider, Agentset logs, and application telemetry.
PrivacyGeneralTenant IDs are useful for data segregation, but incorrect tenant or namespace configuration can expose the wrong knowledge base.
PrivacyCredentials & tokensDo not paste API keys, namespace IDs, tenant IDs, or retrieved private chunks into shared issue reports, screenshots, or repository files.
Disclosure: MIT-licensed official MCP package for Agentset. Agentset offers hosted and self-hosted RAG infrastructure; review the service or deployment terms that apply to your environment.
Safety notes
The MCP server sends Claude's retrieval queries to the Agentset API using the configured API key and namespace.
The `knowledge-base-retrieve` tool can return up to 100 results per call and can rerank results by relevance.
Namespace and tenant selection control which indexed documents are searchable; review them before connecting a shared agent.
API keys should be scoped, rotated, and stored only in the MCP server environment or a secret manager.
Custom tool descriptions can influence when the model calls the retrieval tool, so review them before use in production workflows.
Privacy notes
Retrieved chunks can include private documents, product specs, policies, support content, internal procedures, historical project information, or customer-specific data.
Retrieval queries, namespace IDs, tenant IDs, document chunks, citations, and tool outputs may be visible to the MCP client, model provider, Agentset logs, and application telemetry.
Tenant IDs are useful for data segregation, but incorrect tenant or namespace configuration can expose the wrong knowledge base.
Do not paste API keys, namespace IDs, tenant IDs, or retrieved private chunks into shared issue reports, screenshots, or repository files.
Prerequisites
Agentset account or self-hosted Agentset deployment with a populated namespace.
Agentset API key with access to the namespace Claude should query.
Node.js 18.17 or newer for running the `@agentset/mcp` package.
Namespace ID selected with `--ns` or `AGENTSET_NAMESPACE_ID`.
Optional tenant ID reviewed before enabling multi-tenant retrieval.
Schema details
Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Tool listing metadata
Disclosure
MIT-licensed official MCP package for Agentset. Agentset offers hosted and self-hosted RAG infrastructure; review the service or deployment terms that apply to your environment.
Agentset MCP Server is the official @agentset/mcp package for connecting
Claude to an Agentset knowledge base. It runs as a stdio MCP server and exposes
a knowledge-base-retrieve tool that searches a configured namespace, returns
matching chunks, and optionally reranks results.
Use it when an Agentset namespace already contains the documents Claude should
consult, such as product documentation, support articles, policies, or internal
technical knowledge. The server requires an Agentset API key and namespace ID,
and it can optionally pass a tenant ID for multi-tenant data segregation.
These sources were reviewed on 2026-06-06. Prefer the live MCP docs, NPM
package metadata, MCP server source, option parser, Agentset platform README,
and search documentation for current package versions and retrieval behavior.
Features
Run the official @agentset/mcp package with npx, pnpm dlx, yarn dlx,
or bunx.
Search an Agentset namespace through the knowledge-base-retrieve MCP tool.
Pass namespace ID through --ns or AGENTSET_NAMESPACE_ID.
Pass a tenant ID with -t for multi-tenant data segregation.
Override the default tool description with -d.
Control result count with topK, capped by the server schema.
Enable or disable reranking per retrieval call.
Use Agentset's hosted API or a self-hosted Agentset deployment depending on
your environment.
Installation
Run the MCP package with an Agentset API key and namespace:
For multi-tenant applications, add the documented tenant option only after
confirming the namespace and tenant mapping.
Use Cases
Let Claude answer questions from an Agentset product documentation namespace.
Retrieve relevant support articles with citations before drafting a response.
Give an internal assistant access to policies or procedures without exposing
unrelated namespaces.
Use tenant scoping for customer-specific knowledge bases.
Override the tool description so Claude knows when to use Agentset for a
specific workflow.
Safety and Privacy
Agentset MCP is a retrieval bridge into a knowledge base, so access boundaries
matter. Use least-privilege API keys, connect only the namespace Claude should
query, and check tenant IDs carefully in multi-tenant applications. If a shared
agent uses the server, document which namespace and tenant scope it can access.
Treat retrieval queries, chunks, citations, namespace IDs, tenant IDs, and API
keys as sensitive. Retrieved content can include private documentation, support
history, policies, product details, or customer data. Keep keys in environment
variables or a secret manager, rotate them when shared configs change, and avoid
copying private retrieval output into public issues, screenshots, or commits.
Duplicate Check
No agentset-ai/mcp-server, agentset-ai/agentset, @agentset/mcp, Agentset
MCP Server, or matching source URL entry was found in content/mcp or
README.md.
Show that Agentset MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/agentset-mcp-server)
How it compares
Agentset MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
1 trust signal differ across this comparison (Submitter).
Official Agentset MCP server that lets Claude retrieve cited knowledge-base results from an Agentset namespace through the `knowledge-base-retrieve` tool, with optional tenant scoping and custom tool descriptions.
MCP server for the Graphlit platform, enabling Claude to ingest, search, retrieve, organize, and operate on files, web pages, feeds, collections, conversations, memory, connectors, crawls, and RAG-ready project knowledge.
Apache-licensed TypeScript MCP server for Obsidian vaults with stdio and Streamable HTTP transports, Local REST API access, note search, section-aware edits, tag/frontmatter management, path policies, and read-only controls.
Official Pinecone Developer MCP server that connects Claude and other MCP clients to Pinecone projects and documentation for index management, record upserts, semantic search, cascading multi-index search, reranking, and documentation lookup over integrated-inference indexes.
✓The MCP server sends Claude's retrieval queries to the Agentset API using the configured API key and namespace.
The `knowledge-base-retrieve` tool can return up to 100 results per call and can rerank results by relevance.
Namespace and tenant selection control which indexed documents are searchable; review them before connecting a shared agent.
API keys should be scoped, rotated, and stored only in the MCP server environment or a secret manager.
Custom tool descriptions can influence when the model calls the retrieval tool, so review them before use in production workflows.
✓Graphlit MCP Server can ingest files, web pages, messages, posts, emails, issues, text, memory, feeds, crawls, and connected SaaS data into a Graphlit project.
Tools can create or delete contents, feeds, collections, conversations, specifications, and workflows, and can configure project defaults when explicitly requested.
Web crawling, web search, screenshots, podcast search, feed scheduling, publishing, and connector operations may contact third-party services and process external content.
Generated audio and image publishing can call configured model/provider services and consume credits or quota.
Require confirmation before ingesting private repositories, emails, drive files, Slack/Teams/Discord data, customer documents, large crawls, generated media, deletion operations, or project configuration changes.
✓Cyanheads Obsidian MCP can read, list, search, create, append, patch, replace, delete, tag, and edit frontmatter in the configured vault through the Local REST API plugin.
The server defaults to full-vault access unless read paths, write paths, or read-only mode are configured.
Set `OBSIDIAN_READ_ONLY=true` for research-only workflows, then narrow writes with `OBSIDIAN_WRITE_PATHS` before allowing note edits.
Delete operations are permanent in the vault and should require human review even when the MCP host supports destructive-tool prompts.
Command-palette tools are disabled unless `OBSIDIAN_ENABLE_COMMANDS=true`; command execution can trigger opaque or destructive Obsidian plugin behavior.
Streamable HTTP deployments should use JWT or OAuth auth before being exposed beyond a trusted local machine.
✓The server can create indexes and upsert records, so an agent with a write-capable API key can change live Pinecone project state.
Run the npm package `@pinecone-database/mcp` through `npx`, which downloads and executes the published package on each launch; pin to a trusted version if reproducibility matters.
Scope the Pinecone API key to the intended project and use read-only or least-privilege keys when index creation and writes are not needed.
Require human review before `create-index-for-model` and `upsert-records` runs that mutate production indexes.
Privacy notes
✓Retrieved chunks can include private documents, product specs, policies, support content, internal procedures, historical project information, or customer-specific data.
Retrieval queries, namespace IDs, tenant IDs, document chunks, citations, and tool outputs may be visible to the MCP client, model provider, Agentset logs, and application telemetry.
Tenant IDs are useful for data segregation, but incorrect tenant or namespace configuration can expose the wrong knowledge base.
Do not paste API keys, namespace IDs, tenant IDs, or retrieved private chunks into shared issue reports, screenshots, or repository files.
✓Graphlit environment IDs, organization IDs, JWT secrets, project IDs, resource IDs, connector tokens, URLs, files, emails, messages, issues, transcripts, screenshots, memories, conversations, usage records, and retrieved sources can be exposed to the MCP client.
Ingested documents may be extracted to Markdown; audio and video may be transcribed; images and pages may be described or screenshot.
Connected services such as Slack, Discord, Google Drive, Microsoft 365, GitHub, Jira, Linear, Notion, Dropbox, Box, Reddit, and Twitter/X can expose private workspace content.
Usage records can include request, response, variables, token counts, bytes, units, and credit charges for project operations.
Keep Graphlit secrets in local MCP client configuration only, and review retention, deletion, and connector policies before ingesting regulated or customer data.
✓Vault notes, headings, block references, frontmatter, tags, file metadata, outgoing links, search queries, command names, plugin status, and edit history may be exposed to the MCP client and model provider.
API keys, local plugin endpoints, HTTP auth settings, path allowlists, logs, OpenTelemetry traces, and Docker environment variables can reveal private vault structure or credentials.
Tag listing is vault-wide in upstream behavior and can reveal tag names outside narrowed read paths.
Notes may contain personal journals, client work, credentials, meeting notes, research plans, health data, or other sensitive knowledge-base content.
✓The `PINECONE_API_KEY` is read from the MCP client environment and grants access to the associated Pinecone project; keep it out of prompts, notes, and committed files.
Index names, configurations, namespaces, statistics, record contents, and search queries can be exposed to the MCP client and model provider.
Records and search text may contain embedded documents, customer data, or proprietary content, so review what is sent into indexes and returned by searches.
Documentation search and tool calls reach Pinecone endpoints such as api.pinecone.io, so network access and request metadata leave the local machine.
Prerequisites
Agentset account or self-hosted Agentset deployment with a populated namespace.
Agentset API key with access to the namespace Claude should query.
Node.js 18.17 or newer for running the `@agentset/mcp` package.
Namespace ID selected with `--ns` or `AGENTSET_NAMESPACE_ID`.
Active Graphlit platform account and project access.
Graphlit organization ID, environment ID, and JWT secret from the Graphlit API settings dashboard.
Node.js 18 or newer for the npm stdio server.
Review of which files, URLs, feeds, SaaS connectors, memories, conversations, collections, and web crawls Claude may create or query.
Node.js 24 or newer, or Bun 1.3.11 or newer.
Obsidian vault with the Obsidian Local REST API community plugin enabled.
Local REST API key stored in the MCP client environment.
Stdio MCP client, or reviewed Streamable HTTP deployment with authentication.
Node.js 18 or newer with `npx` available.
Pinecone account and API key generated from the Pinecone console at app.pinecone.io.
MCP client that supports stdio server configuration, such as Claude Desktop or Cursor.
Awareness that index management and record tools require integrated-inference indexes.
Install
Run `npx @agentset/mcp --ns <namespace-id>` with `AGENTSET_API_KEY` set in the MCP server environment.