How do I install Cloudkb?

Cloudkb is a local plugin. Install it using npm package: @reneturcios/cloudkb and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Cloudkb safe to use?

Cloudkb scored 5.6/10 (moderate risk) in MCP Marketplace's automated security scan. It has 2 high or critical findings to review. It's listed, but review the security report on this page before installing.

What credentials does Cloudkb need?

Cloudkb requires the following credentials or environment variables: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION. You can find setup instructions on the server detail page.

What AI apps work with Cloudkb?

Cloudkb uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Cloudkb MCP Server

by CloudCorpRecords

Developer ToolsModerate5.6MCP RegistryLocal

Free

Server data from the Official MCP Registry

Bedrock knowledge bases, data sources and retrieval as MCP tools.

About

Bedrock knowledge bases, data sources and retrieval as MCP tools.

Security Report

5.6

Moderate5.6Moderate Risk

cloudkb is a clean-room Amazon Bedrock knowledge base MCP server that requires AWS credentials from environment variables and sends requests only to amazonaws.com endpoints, which matches its stated purpose. No exfiltration, shell execution, hardcoded secrets, or path traversal was found; path IDs are URL-encoded. The main concerns are low-severity: write operations (start/stop ingestion jobs) are exposed without confirmation, and the default fetch has no timeout, while SigV4 signing is unimplemented so live calls currently fail by design. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 9 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

AWS_ACCESS_KEY_IDRequired

AWS_SECRET_ACCESS_KEYRequired

AWS_REGIONRequired

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-cloudcorprecords-cloudkb": {
      "env": {
        "AWS_REGION": "your-aws-region-here",
        "AWS_ACCESS_KEY_ID": "your-aws-access-key-id-here",
        "AWS_SECRET_ACCESS_KEY": "your-aws-secret-access-key-here"
      },
      "args": [
        "-y",
        "@reneturcios/cloudkb"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

cloudkb

Amazon Bedrock knowledge bases as MCP tools. cloudkb is a clean-room rebuild of the core surface of the AWS Bedrock knowledge base MCP server, under a new name: the same tool names and documented REST request shapes, fresh code, no copied branding.

Tools (core subset, 10)

list_knowledge_bases, get_knowledge_base, list_data_sources, get_data_source, list_ingestion_jobs, get_ingestion_job, start_ingestion_job, stop_ingestion_job, retrieve, retrieve_and_generate.

The first eight tools shape Bedrock Agent (control plane) requests; retrieve and retrieve_and_generate shape Bedrock Agent Runtime (data plane) requests. Request shaping is real and unit-tested; every call goes through an injectable executor interface.

Not in this subset: knowledge base and data source create, update and delete lifecycle, chunking configuration, agents and aliases, flows, prompts, guardrails, evaluation jobs, model invocation and sessions.

Setup

export AWS_ACCESS_KEY_ID=...
export AWS_SECRET_ACCESS_KEY=...
export AWS_REGION=us-east-1   # optional, this is the default

Without credentials, every tool call fails with an error naming AWS_ACCESS_KEY_ID.

Signing gap, stated plainly: SigV4 signing is not implemented in this rebuild. Signing is delegated to an injectable signer/executor hook; with credentials present but no signer injected, a call fails with SigV4 signing not configured: inject a signer/executor instead of sending an unsigned request.

CLI

npx @reneturcios/cloudkb list_knowledge_bases '{}'
npx @reneturcios/cloudkb retrieve '{"knowledge_base_id":"KB1","query":"refund policy"}'
npx @reneturcios/cloudkb mcp        # stdio MCP server

Each tool name is a subcommand taking one JSON object argument.

MCP client config

{
  "mcpServers": {
    "cloudkb": {
      "command": "npx",
      "args": ["-y", "@reneturcios/cloudkb", "mcp"],
      "env": { "AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "...", "AWS_REGION": "us-east-1" }
    }
  }
}

Docker

docker run -i -e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY ghcr.io/cloudcorprecords/cloudkb

Development

npm install
npm run build
npm test

License

MIT

Reviews

No reviews yet

Be the first to review this server!

4.8

Local

MCP Marketplace

Free

by mcp-marketplace · Developer Tools

Search and install MCP servers from inside your AI client.