M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
B

Bookworm Mcptools

Community
An MCP server providing tools for BookWorm, such as catalog and registry services.
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #374 of 438
Stars
★ 507 Very popular
Transport
stdio (local process)
Runtime
Hosted (no local runtime) · Docker
Credentials
No credential needed
License
MIT
Last commit
37FMRS · D

This server is an MCP tool within the BookWorm demo project, providing catalog and registry services. It is not an official product but part of the project. It showcases MCP integration in .NET microservices, but given the demo nature, it is not recommended for production use.

Strongest · Maintenance 12/20 Weakest · Reliability 5/20

Reliability
5/20
Security and permissions
8/20
Maintenance
12/20
Documentation
6/20
Setup experience
6/20
Why each score
Reliability 5/20
The manifest is structurally valid and declares a streamable-http remote plus an OCI stdio package, with a plausible .NET MCP tool scenario for catalog/registry access. However, the remote URL (https://bookworm.com/mcp) is a placeholder domain, the manifest subfolder (src/Integrations/BookWorm.McpTools) conflicts with the stated server path (src/Services/McpTools/BookWorm.McpTools), all four environment variables share the same description, and no CI workflow files or committed tests covering this server's key paths were supplied. Static calibration caps reliability at 12, and missing execution evidence forces a low score (5).
Security and permissions 8/20
No red lines are hit: no malware, credential theft, destructive actions, or tokens in install examples. The manifest marks none of the catalog endpoints as secrets, which is appropriate for URLs. SLSA 2 and OpenSSF Scorecard badges in the README indicate supply-chain attention. Deductions: tool-level least privilege and confirmation behavior cannot be verified from the provided material; data-flow boundaries between the MCP server and catalog/registry services are undisclosed; container provenance is asserted by badges, not demonstrated in the provided files.
Maintenance 12/20
MIT license, repository not archived, and README shows multiple CI pipelines (backend, frontend, Keycloakify), SonarCloud coverage, SLSA 2, and OpenSSF Scorecard badges — evidence of ongoing active development. Deductions: 64 open issues with unknown response quality, no security-response channel documented, and no release cadence or changelog visible in the provided evidence.
Documentation 6/20
The README is a strong project-level overview (architecture diagram, goal checklists, local run steps, Azure deploy steps), and the manifest lists environment variables. Deductions: there is no MCP-server-specific documentation covering tool parameters, authentication, rate limits, cost, or troubleshooting; no usage examples for the declared tools; and the duplicated placeholder env-var descriptions confuse rather than clarify setup.
Setup experience 6/20
The OCI stdio package is a plausible self-contained install path and the four required variables are listed. But the setup is not documented in the README, no mainstream-client config example (e.g., Claude Desktop/VS Code) is provided, the remote points to a placeholder domain, and the full project bootstrap requires mise, Docker, and Aspire CLI. Static calibration caps setup at 15 without executable evidence; here the gaps lower it to 6.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkConnects to a database

Best for

  • Developers wanting to integrate an MCP server into a .NET Aspire application.
  • Teams needing standardized AI tool interfaces for multi-agent collaboration.

Not for

  • Production use: The project explicitly states it's for demo purposes only and not production-ready.
  • Users seeking a full BookWorm client UI; this server only provides backend tools.

Required permissions

  • Network access: Requires access to the configured catalog service endpoints (CATALOG_HTTP and CATALOG_HTTPS) to perform tool calls.

Risks and side effects

  • Dependency on the configured catalog service availability; tool calls will fail if endpoints are unreachable.
  • Since the project is a demo, there may be unresolved security or stability issues.
  • When using AI features, external APIs (e.g., OpenAI) may be involved, posing data egress risks.

Setup

Before you start

Runtime：Hosted (no local runtime) · Docker

CATALOG_HTTP required HTTP endpoint of the BookWorm catalog service, marked required in the manifest; set it to your deployed catalog address.
CATALOG_HTTPS required HTTPS endpoint of the BookWorm catalog service, marked required in the manifest; set it to your deployed catalog address.

Based on the repository and server manifest, the server is distributed as an OCI image via ghcr.io/foxminchan/bookworm/mcptools:1.0.0. Running it requires setting environment variables: CATALOG_HTTP, CATALOG_HTTPS, services__catalog__http__0, and services__catalog__https__0, which specify the catalog service HTTP/HTTPS endpoints. For detailed local setup and deployment, refer to the repository README.

Check that it works

Connect via streamable-http to https://bookworm.com/mcp in your MCP client and confirm catalog and registry tools appear in the tool list; then ask about the catalog to verify a live response.

Troubleshooting

  1. Ensure all required environment variables are set and verify the endpoint values are valid.
  2. Check that the catalog service is running and network accessible from the MCP server.
  3. Ensure you are using the correct version of the OCI image (1.0.0) and follow the repository's deployment instructions.

Things to try

Once connected, you can ask your AI assistant things like:

  • List the books available in the BookWorm catalog
  • Look up the details of a book in the catalog
  • Check the registry service for available BookWorm services
  • Compare a few books from the catalog

Use cases

As a developer, access BookWorm catalog and registry services via MCP during development or demos.
Integrate BookWorm catalog and registry tools in AI agent workflows for intelligent book management.

Overview

This is an MCP server that provides tools for BookWorm, such as catalog and registry services. BookWorm is a demo cloud-native application built with Aspire, integrating AI, microservices, domain-driven design, and multi-agent systems. This server implements standardized AI tooling via MCP and supports A2A and AG-UI protocols.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 63.3k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision cba97a699a10 Data synced 2026-10-19 Read the FMRS scoring method