Data & contentPublic source

Knowledge Base MCP Server

Enterprise knowledge base for ADK-Rust Enterprise agents. 9 MCP tools for articles, TF-IDF search boosted by helpfulness, feedback loops, gap detection, versioning, and draft/publish workflow.

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Provides knowledge capabilities through a typed MCP contract.

Provides base capabilities through a typed MCP contract.

Architecture

How Knowledge Base MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Knowledge Base MCP Server

Validates the request and owns 9 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Knowledge Base MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Knowledge Base MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

9 named tools

search_articles

Search knowledge base with TF-IDF scoring, boosted by helpfulness

read only

get_article

Get full article by ID — body, version, owner, reviewer, freshness

read only

find_related

Find articles related to a given article by shared tags and category

read only

create_draft

Create a new article draft

internal write

suggest_update

Suggest an update to an existing article — creates a new draft version

internal write

publish_article

Publish a draft article — requires reviewer name

internal write

record_feedback

Record feedback on an article (helpful/not helpful)

internal write

list_articles

List articles filtered by category and/or status

read only

get_knowledge_gaps

Get knowledge gaps — queries with no results, ranked by frequency

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

5 read only4 internal write

The registry manifest declares read only, internal write tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-knowledge-base

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-knowledge-base",
    ["mcp-knowledge-base"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/architecture.svg Issues and support ↗github.com issues

Keep exploring