AIPOCH Open-Science MCP server
Commit Nov 14, 2026Lets an AI client plan and run reproducible research workflows with Python/R notebooks, literature review, and traceable evidence packages.
Also known as aipoch/open-science
- Stars
- 5,528
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 14, 2026
- License
- Apache-2.0
What is AIPOCH Open-Science MCP?
AIPOCH Open-Science lets an AI client plan and run reproducible research workflows with Python/R notebooks, literature review, and traceable evidence packages.
Summary generated from the project's README
About AIPOCH Open-Science MCP server
Planning a research task and keeping the evidence attached is what AIPOCH Open-Science handles inside an AI client. It is a local-first workbench for reproducible science, aimed at researchers and developers who want literature review, Python or R notebook analysis, and traceable results in one session. You start a project, describe your goal and expected outputs, attach files, pick a model and approval mode, then use @ to reference project files or / to choose a skill.
The workbench runs in a desktop app for macOS 12+, Windows 10/11 x64 and Linux x64/ARM64, or as a standalone CLI and Web UI installed from the npm package @aipoch/open-science with Node.js 22.13.0 or later; a Homebrew cask and a separate tap formula also exist. First-time setup walks through environment, data location, agent runtime, model provider and optional notebook runtime, and you connect a supported provider, custom gateway, or a Claude or Codex subscription. Credentials, endpoints and models are validated during that wizard.
What sets it apart is the handoff. A .science Research Package bundles conversation branches, file versions, Notebook records and verification evidence, so a recipient can trace a figure or table back to its inputs; Fork to continue creates a writable copy. Provenance shows the inputs, code and execution history behind a file version and allows rerunning it. A completed branch can become a Research Film with English narration from a local speech engine, downloadable as an HTML player or MP4.
What you can do with it
- 1Screen papers against criteriaHave the client import a Zotero library, filter papers by inclusion criteria, and open each source PDF to confirm a finding.
- 2Trace a figure to inputsAsk which code, file version and execution run produced a given table or figure before trusting it in a write-up.
- 3Run Python or R analysisExecute a notebook analysis and review the resulting tables and figures next to the source files in the same session.
- 4Share a reproducible packageExport a .science package and hand it to a colleague so they can inspect the recorded steps and file versions behind a result.
- 5Generate a research filmTurn a finished conversation branch into a narrated presentation and export it as an MP4 for a lab meeting.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 13, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packageNot checked
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesNot checked
README
View on GitHub💡 AIPOCH Open-Science v1.2.1 updates
November 11, 2026
- Unified Resource Center: Manage skills, connectors, specialists, and Marketplace installs together; installation also works in the Web UI.
- Manual prompt optimization: Invoke your configured provider from the composer, review or edit the result, and undo it; save custom templates in Project settings.
- Built-in Agent upgrades: Use Codex subscriptions for the main agent and subagents, select Claude Fable 5.2 with a 1M context window, and use provider-supported output limits.
- Bibliography CSV: Export selected references or a whole project or collection with 16 stable English column names.
- Compact research exports: Notebook and Compute histories store unique evidence once, reducing the size and export time of long
.sciencehistories. - Cloud compute sign-in: Modal and Hugging Face prepare compatible Python before browser authorization; account verification follows the system proxy.
- Reliability improvements: Windows update recovery, answered questions, and research films across session switches improve; idle interpreters are reclaimed after 15 minutes without session activity.
View the full v1.2.1 release notes
A research record to share, a film to watch
Hand off a result with a .science package. Export the conversation branches, file versions, Notebook records, and verification evidence you want to share. Recipients can import the package into their own projects, open the read-only record, and trace a figure or table back to its inputs. Verification records describe the sender’s checks. In the desktop app, Fork to continue creates a writable copy.
Present the same work as a Research Film. In the desktop app, choose Generate research film on a completed conversation branch. Your configured model prepares the presentation from the recorded session, and the local speech engine generates English narration. Review the film, then download the HTML player or export an MP4. A .science package can also carry the player for a film already generated on an included branch.
🚀 Quick Start
1. Download the app
Open the official download page and choose the installer for your computer:
| Your computer | Choose |
|---|---|
| macOS 12+ — Apple Silicon (M1 or newer) | The macOS DMG for Apple Silicon / ARM64 |
| macOS 12+ — Intel | The macOS DMG for Intel / x64 |
| Windows 10/11 x64 | The Windows x64 installer (code-signed) |
| Linux x64 | The Linux x64 AppImage or Debian package |
| Linux ARM64 | The Linux ARM64 AppImage or Debian package |
See download verification for checks before installation.
On macOS, you can also install with Homebrew:
brew install --cask open-science
The release assets include standalone CLI archives for macOS, Linux, and Windows. They bundle Node.js, so you can run the CLI without installing Node.js, npm, or Homebrew.
For the standalone CLI on macOS or Linux, use the separate AIPOCH tap:
brew install aipoch/tap/open-science
This Formula includes Node and runs without the desktop app; its release may differ from the desktop Cask. See the standalone runtime guide for prerequisites and upgrades.
For the standalone CLI and Web UI, install the published npm package with Node.js 22.13.0 or later:
npm install --global @aipoch/open-science
open-science start --no-open
open-science url
Open the printed URL to complete setup, or follow the terminal setup guide. npm supports macOS ARM64/x64, glibc Linux ARM64/x64 and Windows x64; the desktop app is not required. Keep npm optional dependencies enabled and review the Linux prerequisites and upgrade instructions. The URL contains an authentication token; keep it private.
Windows reinstalls preserve research data. For a full cleanup, see the data reset tool, which permanently deletes local data after confirmation.
2. Complete first-time setup
Follow the setup wizard: Environment → Data location → Agent runtime → Model provider → Notebook runtime.
Complete the required environment and agent-runtime checks and test your model connection. Python/R Notebook setup is optional; Notebook and data-location settings can be changed later.
After setup, open System settings to change appearance or notifications. In General, you can find diagnostics, command-line tools, and the guide to manual installation and updates.
The former Model settings tab is now Local capabilities, covering PDF extraction, OCR language packs, and research narration. Narration requires a locally installed voice model.
3. Start a research project
- Click New project, open a session, and describe your research goal, inputs, and expected outputs.
- Attach files, select a model and approval mode, then send the task. Use
@to reference project files or/to choose a skill. - Review tool activity and any approval requests, preview the results, and check their available evidence in Provenance.
Screenshots in this README illustrate the workflow. Labels, catalogs, and other interface details may differ from the version you install.
What can you do with AIPOCH Open-Science?
| Task | How it works |
|---|---|
| Review literature | Import references from Zotero, screen papers against your criteria, and open the source PDFs to check a finding. |
| Analyze data | Run Python or R in a Notebook and inspect the resulting tables and figures alongside the source files. |
| Trace a result | Open a file version in Provenance to inspect its inputs, code, and execution history. Rerun it when the recipe, inputs, and runtime are available. |
| Hand off a result | Share a .science package so others can inspect the recorded steps and file versions behind a result. |
| Extend a workflow | Enable scientific data connectors, choose built-in skills, or install additional skills and specialists from the marketplaces. |
| Choose a model | Connect a supported provider or custom gateway, or use a supported Claude or Codex subscription. Available protocols depend on the agent backend. |
Benchmark Results
AIPOCH evaluated Open-Science on research tasks ranging from literature search to reproducing published results.
| Task | Benchmark | Result from AIPOCH’s run |
|---|---|---|
| Find a paper | LitQA2-FullText-Search, Test | Target paper in the top 30 for 68/75 questions (90.67% Recall@30). |
| Answer a question from the literature | LitQA2-FullText, Test | 70/75 correct answers (93.33% accuracy). |
| Write a cited answer | ScholarQA-CS2, 100 validation questions | 0.9289/1 composite quality score. Official test references use different questions. |
| Carry out a workflow | ASI-Bench, local runs with the same model | 59.46 on B4 (Codex 55.45) and 56.11 on B2 (Codex 56.09). |
| Reproduce published results | CORE-Bench-Hard | 36/37 tasks correct (97.30%, including retests). |
| Analyze biomedical data | BiomniBench-DA, Public 50 | 79.05 mean judge score (81.04 and 77.06, weighted equally). |
| Generate hypotheses | DiscoveryBench, 25 validation tasks | 0.7467/1 mean score using a local model judge. |
These local runs used different metrics, models, and task sets from August to November 2026. The scores describe those runs. They were not rerun for this release.
Evaluation overview · CORE-Bench-Hard report · BiomniBench-DA report
Data, Permissions, and Trust
AIPOCH Open-Science stores project data, settings, artifact versions, and provenance evidence on the local computer. API Keys are kept locally and use the operating system's secure credential storage when it is available. Logs are local and are not uploaded automatically.
External data flow is still possible and should be reviewed:
- Model requests send the prompt and necessary context to the selected model provider.
- Web searches and remote connectors send their displayed parameters to external services.
- Local connectors may execute trusted commands on the computer.
- The application can also contact update servers, marketplace catalogs, and runtime or model download services.
- Attachments,
@references, logs, and generated reports may contain sensitive research data.
Choose the narrowest permission profile that fits the task:
| Mode | Behavior | Recommended use |
|---|---|---|
Ask for approval |
Requests approval for actions not already covered by scoped grants or trusted application tool policies | New workflows, sensitive data, unfamiliar scripts |
Auto-approve edits |
Uses the backend's native auto review when available; otherwise automatically allows clearly low-risk workspace operations | Trusted file-editing work with controlled external access |
Full access |
Automatically allows edits, commands, network, and connectors | Clearly scoped, fully trusted, unattended work |
The effective profile depends on the selected backend and existing grants. Connector, tool, and compute-network policies also apply; check the effective mode shown by the app.
Review connector parameters and tool activity before approving them. Never include API Keys, access tokens, patient identifiers, unpublished data, or sensitive local paths in screenshots or public issue logs.
Developer guides
- Development · Build and package from source · Contribute a change
- Running Open-Science · Standalone runtime · Service lifecycle · Mobile pairing
- Automation · CLI · Node.js SDK · Connect an MCP client
Frequently Asked Questions
A: Check the API Key for missing characters or spaces, verify the Base URL and region, use the provider's exact model ID, and confirm network access and account balance. For a Claude subscription, retry the shared browser login or refresh the isolated claude setup-token credential, depending on the selected mode.
A: The current step has not met its required condition. Fix any environment row marked Action needed, install or repair the selected agent runtime, or validate the model provider, depending on the active step. Notebook setup is optional and only affects Notebook execution.
A: Remote Compute (SSH) is always enabled and does not need to be enabled in Settings. Register an SSH compute host under Settings → Connections → Compute, make it available to the current session, and then use natural language or /remote-compute-ssh. You need a reachable SSH host, valid authentication, permission for the required directories, and the software, dependencies, and compute resources required by the workload. Direct SSH does not require a scheduler; Slurm mode requires a working Slurm environment and permission to submit jobs. “Always enabled” refers to the skill, not to the availability of every registered host.
Kubernetes, Hugging Face Jobs, Modal, and Ray are also available for user-connected targets. Before each external submission, approve the target, command, resources, and outputs. Recovery records resume result collection after a restart, and published results open in Compute Preview. Provision the required account, software, resources, and permissions yourself; cloud jobs may incur charges.
A: Yes. Install the standalone CLI, or use Settings → General → Command line tool → Install command to control an already running desktop instance. The npm installation requires Node.js; Homebrew and standalone bundled-runtime packages include it. Initialize the local profile, then control the service and submit research tasks without opening a browser:
# Initialize the local CLI profile and start the service in the background
open-science init
open-science start --no-open
# Create a project and run a task by its exact name
open-science project create "Systematic review"
open-science run --project "Systematic review" \
--prompt-file ./task.md \
--approval-profile auto \
--skill literature-review \
--wait --json
# Download a generated artifact
open-science artifacts list <session-id> --json
open-science artifacts download <artifact-id> --output ./report.md
See the CLI guide for the full command reference, JSON/JSONL output formats, exit codes, and headless service options.
A: Open the generated artifact and choose Provenance. Select a version to inspect the content identity and the available producer code, execution history, inputs, environment inventory, producing conversation context, and reviewer evidence. Evidence AIPOCH Open-Science could not verify is marked unavailable.
A: Yes. Edit a completed user message and resend it to create a new branch from that point. The original later turns remain available, and the revision arrows beside the message switch between the alternative paths.
Contributors
Thank you to everyone who contributes code, documentation, translations, bug reports, and community support to AIPOCH Open-Science.
Get Involved
Help improve AIPOCH Open-Science: report a bug, suggest a feature, ask a question, or contribute. Choose a channel below to get started.
| Channel | Use it for |
|---|---|
| GitHub Issues | Bugs, reproducible failures, and concrete feature proposals |
| GitHub Discussions | Design questions, roadmap proposals, and longer technical conversations |
| Discord | Community help, contributor coordination, and informal discussion |
| X / @aipoch_ai | Release announcements and build-in-public updates |
| AIPOCH Open-Science website | Official product overview and downloads |
Before opening a public issue, remove API Keys, tokens, private file paths, unpublished data, patient identifiers, and other sensitive material from logs and screenshots. See CONTRIBUTING.md for the development workflow.
If AIPOCH Open-Science is useful to you, star the repository on GitHub.
For shipped, partial, and planned capabilities, see the Capability Map.
AIPOCH Open-Science MCP questions
What is a .science research package?
A .science package is a portable export containing conversation branches, file versions, Notebook records, and verification evidence that recipients can import and inspect.
Can I trace a figure or table back to its inputs?
Yes, opening a file version in Provenance shows its inputs, code, and execution history, and you can rerun it when the recipe, inputs, and runtime are available.
Does Open-Science run Python and R code?
Yes, you can run Python or R in a Notebook and inspect the resulting tables and figures alongside the source files.
Which model providers can I connect?
You can connect a supported provider or custom gateway, or use a supported Claude or Codex subscription; available protocols depend on the agent backend.
Which platforms does it support?
It runs on macOS 12+, Windows 10/11 x64, and Linux x64/ARM64, with a standalone CLI and npm package also available.