ResearchTwin MCP Server

Federated research discovery with S-Index metrics across a network of digital twins. Exposed over MCP by the researchtwin mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

ResearchTwin is an open-source, federated platform that transforms a researcher's publications, datasets, and code repositories into a conversational Digital Twin. Built on a Bimodal Glial-Neural Optimization (BGNO) architecture, it enables dual-discovery where both humans and AI agents collaborate to accelerate scientific discovery.

Its toolset

Everything the assistant can do here goes through one of these:

• Endpoint — Schema.org Type

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need 4 environment variables: ANTHROPIC_API_KEY, S2_API_KEY, GITHUB_TOKEN, DISCORD_BOT_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. ResearchTwin's toolset — Endpoint — is a fair guide to whether it matches your workflow. It is maintained by martinfrasch; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the researchtwin mcp server does with a few real requests.