RSpace MCP server

This is a proof-of-concept MCP server for RSpace that runs locally on your machine. It uses the RSpace Python client and exposes some RSpace API endpoints to LLM agents using the Model Context Protocol. The repository also contains example agent skills that package up conventions and reference files for working with RSpace in a specific way.

Installation and configuration

1. Clone or download this repository to your local machine

2. Install uv and python

3. Run uv sync to install dependencies

4. Create a .env file in the same folder and add

   RSPACE_URL=RSpace URL # e.g. https://community.researchspace.com 
   RSPACE_API_KEY=your API key

5. Connect your LLM app with the RSpace MCP server

   1. For VS Code Copilot, add an mcp.json with the following content

      {
        "inputs": [
          {
            "type": "promptString",
            "id": "rspace-apikey",
            "description": "RSpace API Key",
            "password": true
          },
          {
            "type": "promptString",
            "id": "rspace-url",
            "description": "RSpace base URL",
            "password": false
          }
        ],
        "servers": {
          "rspace": {
            "command": "uv",
            "args": [
              "--directory",
              "<full path to this directory>",
              "run",
              "main.py"
            ],
            "env": {
              "RSPACE_API_KEY": "${input:rspace-apikey}",
              "RSPACE_URL": "${input:rspace-url}"
            }
          }
        }
      }

   2. For Claude Desktop, add a claude_desktop_config.json with the following content:

      {
        "mcpServers": {
          "rspace": {
            "command": "<path to uv command>",
            "args": [
              "--directory",
              "<full path to this directory>",
              "run",
              "main.py"
            ],
            "env": {}
          }
        }
      }

Keeping the context small (tool dispatcher)

The server has a lot of tools, and every tool definition is sent to the model on every request, which costs context tokens. To keep that cost low, only the read-only core group is listed directly: status plus the search and get/list tools across documents, forms, inventory, instruments, and the audit trail. Reads are safe and common, so they need no extra step.

Everything that changes state (create, update, and the deletes) is registered but hidden, and the model reaches it through three always-present dispatcher tools:

• list_rspace_tools(toolset) — discover hidden tools and which group they are in.

• describe_rspace_tool(names) — get the input schema for one or more tools.

• rspace_invoke(tool_name, arguments) — run any tool by name; arguments are validated against the tool's real schema. Destructive tools additionally require confirm=true.

This means a mutation is always a deliberate discover-then-invoke, and the highest-consequence operations (deletes) never sit in the always-visible tool list. Because the listed set never changes, it also works on every MCP client (it does not rely on tools/list_changed, which Claude Desktop and the claude.ai connectors do not act on mid-session). Tool names are unchanged, so a skill can still refer to a capability by name; the model discovers and invokes it on demand.

To expose more groups directly (skipping the dispatcher for them), set RSPACE_DIRECT_TOOLSETS in the client env block to a comma-separated list of groups, or all to list everything:

RSPACE_DIRECT_TOOLSETS=inventory-write,inventory-containers

Groups: core (always direct, read-only), plus the mutation groups eln-docs, eln-forms, inventory-write, inventory-containers, inventory-templates, instruments, files-lom, and destructive.

Related MCP server: Anytype MCP Server

Using the RSpace through the MCP server

Please bear in mind that this is a proof of concept and your production use case might require a more specific MCP server configured with specifically fine-tuned tools. The tools provided here in this prototype ...

• do not exhaustively feature the functionality currently available through the RSpace Python client

• might be more than you need for your use case

• might not be optimally configured for how you would like to interact with RSpace

We're curious to learn about how you (want to) use this solution, so let us know about your experiences and learnings or contribute them directly to this repository.

Use cases and applications

You can find descriptions of some usecases and examples in the examples folder and we're looking forward to hearing about new examples and learnings. If you have an experience to share, feel free to contribute.

Using an agent skill

The skills/rspace-franklin folder contains a ready-to-customise skill for working with RSpace through this MCP server — a task loop, FAIR and naming conventions, and placeholder reference files for your lab's standards, SOPs, and more. Copy the folder, give it your own name, and edit the [EDIT ME] sections to match your lab before using it.

Contributing new Tools

If you develop new tools or toolsets, feel free to share code snippets or entire tool sets in the tools folder with appropriate annotations.

Contributing new Skills

If you build a skill for a different working style, research domain, or workflow, feel free to share it in the skills folder alongside its own reference files.

Acknowledgements

This project is based on code originally created by richarda23.