"Chemistry information or resources" matching MCP servers:

Discover and connect your agents with other agents via A2A protocol. Share resources for free or fee.

A public, long-lived contact and cooperation point for autonomous AI agents. Agents describe missing capabilities or resources, request help from a human operator, and leave persistent messages on a tamper-evident message board.

Enables selecting a saved Codex or Claude Code session from the same PC and importing its recent context into the other tool, so work can continue across clients with source and omission information.

Enables agents to crawl and read websites politely, learning per host which reader, URL rewrite, or detail path actually reaches good information, and reusing those wins across runs or a shared database. Failures come back as coded errors with concrete next steps, so blocked or empty pages point to an honest alternative instead of endless retries.

Enables deploying applications and managing cloud resources in Timeweb Cloud through natural language.

A Model Context Protocol server allowing Claude AI to interact with AWS resources through natural language, enabling users to query and manage AWS services without using the traditional AWS Console or CLI.

A ready-to-use starter implementation of the Model Context Protocol (MCP) server that enables applications to provide standardized context for LLMs with sample resources, tools, and prompts.

A Model Context Protocol server that provides Coze resources and tools for managing workspaces, bots, and conversations.

Connects AI assistants to the Opsenes platform, exposing its capabilities as MCP tools, resources, and prompts for safe platform operations.

Delivers the LXAgents shared agent instruction set via MCP prompts and resources. It includes read-only tools for setting up and checking agent instructions in repositories.

Enables clients to connect to and manage multiple backend Model Context Protocol servers, aggregating their tools and resources and exposing them through a unified SSE, Streamable HTTP, or Stdio interface.

Proxy that aggregates multiple MCP servers and presents them as a unified interface, allowing clients to access resources from multiple servers transparently.

Enables connecting and managing multiple backend MCP resource servers of Stdio, SSE, and Streamable HTTP types, then exposing their aggregated tools and resources through unified SSE/HTTP endpoints or as a single Stdio server. It routes requests to the appropriate backend and supports optional web admin management, authentication, and concurrent client connections.

Enables developers to expose custom tools, prompts, and resources to MCP clients from a stateless App Router route handler. Serves the current 2026-07-28 protocol natively while a compatibility layer supports 2025-era Streamable HTTP clients.

Enables AI tools to uniformly discover, inspect, and call tools, prompts, and resources from multiple upstream MCP servers through a small set of fixed MCP tools, over stdio or HTTP.

Enables connecting to and managing multiple backend MCP servers (Stdio, SSE, Streamable HTTP), aggregating their tools/resources, and exposing them through unified SSE, Streamable HTTP, or Stdio endpoints with routing, authentication, and optional web-based administration.

A server that enables AI models to access user geolocation information via EdgeOne Pages Functions through the Model Context Protocol.

Ultra-lightweight MCP server for Bun with full protocol compliance. Enables building MCP servers with tools, resources, and prompts using minimal dependencies and heap footprint.

Acts as a central hub that connects to and manages multiple backend Model Context Protocol servers, aggregating their tools and resources and exposing them through unified SSE, Streamable HTTP, or Stdio interfaces. It routes requests to the correct backend and supports concurrent clients with optional authentication and web-based administration.

Enables browsers to act as MCP servers by relaying tools, resources, and prompts to AI agents via a WebSocket-to-stdio bridge.

Aggregates multiple backend MCP servers (Stdio, SSE, and Streamable HTTP) into a single unified endpoint, exposing their combined tools and resources via SSE, Streamable HTTP, or Stdio. It also offers an optional web admin UI for managing server connections, tool enablement, and live configuration reloads.

Aggregates multiple backend Model Context Protocol servers of Stdio, SSE, and Streamable HTTP types and exposes their combined tools and resources through a single unified SSE, Streamable HTTP, or Stdio interface with request routing and authentication. Includes an optional web admin UI for managing server connections, enabling or disabling individual tools, overriding tool names and descriptions, and live-reloading configuration.

Enables connecting to and aggregating multiple backend Model Context Protocol servers, then exposing their combined tools and resources through unified SSE, Streamable HTTP, or Stdio interfaces. It also supports optional web-based management, tool control, authentication, and live configuration reloads.

Enables connecting and managing multiple backend MCP servers and exposing their aggregated tools and resources through unified SSE or Streamable HTTP endpoints, or as a Stdio server, with request routing and optional authentication.

A TypeScript SDK for building MCP servers and clients, providing standardized context provision for LLMs through tools, resources, and prompts.

Enables developers to define and run TypeScript Model Context Protocol servers with simple Express-like or decorator APIs for tools, prompts, resources, resource templates, and roots, including context logging and progress reporting.

Enables developers to build and deploy secure, typed Model Context Protocol servers with tools, resources, prompts, bearer-token authentication, per-tool scopes, rate limiting, and health probes over Streamable HTTP.

Enables aggregating and routing across multiple backend MCP servers, exposing their combined tools and resources through unified SSE, Streamable HTTP, or Stdio interfaces with optional authentication and web-based administration.

Enables clients to connect to, manage, and aggregate multiple backend MCP servers and access their combined tools and resources through unified SSE or Streamable HTTP endpoints, or as a single Stdio server. It provides request routing, optional authentication, granular tool controls, and an optional web admin interface.

Enables connecting, aggregating, and routing multiple backend Model Context Protocol servers (Stdio, SSE, and Streamable HTTP) by exposing their combined tools and resources through unified SSE/HTTP endpoints or a single Stdio interface, with optional authentication and web-based admin management.