Catalysis Hub for Claude Desktop

Created By
QuentinCodya year ago
Overview

What is Catalysis Hub?

Catalysis Hub is a database that provides access to computational catalysis research data, including reaction energetics, surface structures, DFT calculation parameters, and publication metadata. It allows users to interact with this data through Claude Desktop.

How to use Catalysis Hub?

To use Catalysis Hub, set it up in Claude Desktop by editing the configuration file to include the Catalysis Hub server details. After setup, you can ask Claude to query the database for specific information.

Key features of Catalysis Hub?

  • Access to a comprehensive database of catalysis research data.
  • Ability to perform queries using natural language through Claude.
  • Support for GraphQL interface for advanced data retrieval.

Use cases of Catalysis Hub?

  1. Searching for recent publications on specific catalysts.
  2. Analyzing reaction mechanisms and energetics.
  3. Comparing different catalyst materials based on adsorption energies.

FAQ from Catalysis Hub?

  • Can I access all catalysis data through Claude?

Yes, you can query a wide range of data related to catalysis research.

  • What should I do if Claude cannot access Catalysis Hub?

Ensure the configuration is correct and restart Claude Desktop. If issues persist, contact support.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
QuentinCody
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago