mcp

This MCP server integrates Agentset's retrieval-augmented generation tooling, enabling you to expose a configurable set of tools that can be used by an agent for document-based tasks. By adding this server to your Claude environment, you enable the agent to access Agentset's capabilities (such as querying documents, performing RAG-style retrieval, and leveraging the tool descriptions you provide) via the MCP interface. The included example shows how to add the Agentset MCP to Claude so that the agent can call the @agentset/mcp package as a managed tool within your namespace.

To use, ensure you have an API key and a namespace ID for your Agentset account. Then run the MCP via npx, which will fetch the latest package and launch the server under the specified namespace. You can customize tool descriptions and behavior by passing descriptive text or additional flags when invoking the MCP, and you can set environment variables to control authentication and scope for each request.

Prerequisites:

• Node.js and npm (or use a compatible environment that can run npx)
• Access credentials for Agentset (API key and namespace ID)

Installation steps:

1. Ensure you have an API key and namespace ready for Agentset:

   • AGENTSET_API_KEY=your-api-key
   • AGENTSET_NAMESPACE_ID=your-namespace-id

2. Install and run the MCP via npx (as shown in the repository):

# Replace with your actual API key and namespace if you want to export them inline
AGENTSET_API_KEY=your-api-key AGENTSET_NAMESPACE_ID=your-namespace-id npx @agentset/mcp --ns your-namespace-id

3. If you are integrating with Claude, use the provided Claude config snippet to add the MCP as a tool:

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

4. Verify the server is reachable and the tool is discoverable by your agent platform. Ensure firewall and network rules allow MCP endpoint access if running in a restricted environment.

Tips and common notes:

• Environment variables: AGENTSET_API_KEY and AGENTSET_NAMESPACE_ID are required to access Agentset resources. You can override them per invocation as needed.
• Tool descriptions: You can customize the tool description passed to the MCP to help users understand its purpose within your app (as shown by the -d option in examples).
• Tenant handling: You can specify a tenant via -t your-tenant-id when invoking the MCP for multi-tenant setups.
• If you encounter issues, check that the API key has the correct permissions for the target namespace and that the npm package @agentset/mcp is accessible from your environment.
• Keeping the MCP up to date is as simple as using the latest tag in the npx command (@latest).