Skip to main content
Glama
remotebrowser

Goodreads MCP Server

by remotebrowser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid
README.md
# ⚠️ DEPRECATED

This repository has been **deprecated** and is no longer maintained.

## 🔄 Migration Notice

Please use the new GetGather MCP instead:

**👉 [github.com/mcp-getgather/mcp-getgather](https://github.com/mcp-getgather/mcp-getgather)**

All future development, updates, and support will be provided in the new repository.

Thank you for your understanding.
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_books' has a clearly defined purpose that cannot be confused with any other tool in the set.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern ('get_books'), and with only one tool, there is no inconsistency to evaluate. The naming convention is straightforward and appropriate for the function.

Tool Count2/5

A single tool is too few for a server named 'Goodreads MCP Server', which implies broader functionality for interacting with the Goodreads platform. The scope appears limited to retrieving books only, lacking operations like search, reviews, or user interactions, making the tool count insufficient for the expected domain.

Completeness2/5

The tool surface is severely incomplete for a Goodreads server. It only provides book retrieval, missing essential operations such as searching books, managing reviews, accessing user profiles, or handling shelves. This creates significant gaps that will likely cause agent failures when attempting typical Goodreads-related tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources