RSpace MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RSPACE_URL | Yes | RSpace base URL, e.g. https://community.researchspace.com | |
| RSPACE_API_KEY | Yes | RSpace API Key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| statusA | Determines if RSpace server is running, returning its status |
| get_documentsB | Gets most recent RSpace documents up to 100 at a time |
| get_single_Rspace_documentB | Gets a single RSpace document by its numeric id or string globalId |
| createNewNotebookA | Creates a new RSpace notebook |
| createNotebookEntryA | Adds content as a new notebook entry in an existing notebook |
| tagDocumentOrNotebookEntryC | Tags a document or notebook entry with one or more tags :param doc_id: :param tags: :return: |
| renameDocumentOrNotebookEntryC | Renames a document or notebook entry :param doc_id: :param name: the new name :return: |
| getAuditEventsA | Gets audit trail of all actions performed in RSpace. Optionally can filter by:
|
| downloadFileB | Get the file contents given a file id, and a file-system location to save to |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| literature_search | Performs a literature review using pubmed on the given topic |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.