RSpace MCP Server
Related Servers
Alternatives to RSpace MCP Server
No user-submitted related servers found.
Related Servers
AlicenseBqualityBmaintenanceA proof-of-concept server that enables LLM agents to interact with RSpace API endpoints using the Model Context Protocol, allowing AI assistants to access and manipulate research data in RSpace.504AGPL 3.0- AlicenseNot gradedqualityBmaintenanceExposes the agent's tools over the Model Context Protocol, enabling LLMs to track applications, generate cover letters, and process emails.MIT
- AlicenseNot gradedqualityDmaintenanceExposes Swagger/OpenAPI-defined APIs through the Model Context Protocol, making them accessible to AI agents.11 npmISC

Rossum MCP Serverofficial
FlicenseBqualityDmaintenanceA Model Context Protocol server that provides AI agents with read-only access to Rossum API resources (queues, schemas, hooks, workspaces) for analysis purposes.61-- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol server enabling LLMs to search, retrieve, and manage documents through Rememberizer's knowledge management API.35Apache 2.0
- AlicenseNot gradedqualityDmaintenanceExposes your FastAPI endpoints as Model Context Protocol tools with authentication, preserving schemas and documentation.1MIT
TDQS
Scored across 9 tools
Each tool targets a distinct resource/action combination, with clear singular/plural distinctions (e.g., get_documents vs get_single_Rspace_document) and separate operations for creating notebooks vs entries, tagging vs renaming. No two tools appear to do the same thing.
The tool names mix snake_case (get_documents, get_single_Rspace_document) with camelCase (createNewNotebook, tagDocumentOrNotebookEntry), and an inconsistent verb style (status vs get_ vs create vs tag). This violates the consistency rule and creates a chaotic naming pattern.
With 9 tools covering status, document retrieval, notebook/entry creation, tagging, renaming, audit, and file download, the set is well-scoped and every tool serves a distinct purpose within the RSpace domain.
The surface covers core workflows (retrieve, create, tag, rename, audit, download) but lacks deletion and direct content update for existing documents, and it's unclear if notebooks/entries can be listed distinctly. These gaps could require agent workarounds.