@cyanheads/pubchem-mcp-server 1.0.1

package/LICENSE

@@ -0,0 +1,201 @@
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2025 Casey Hand @cyanheads
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,236 @@
+# PubChem MCP Server
+
+[![TypeScript](https://img.shields.io/badge/TypeScript-^5.8.3-blue.svg)](https://www.typescriptlang.org/)
+[![Model Context Protocol](https://img.shields.io/badge/MCP%20SDK-^1.13.2-green.svg)](https://modelcontextprotocol.io/)
+[![Version](https://img.shields.io/badge/Version-1.0.1-blue.svg)](./CHANGELOG.md)
+[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
+[![Status](https://img.shields.io/badge/Status-Beta-orange.svg)](https://github.com/cyanheads/pubchem-mcp-server/issues)
+[![GitHub](https://img.shields.io/github/stars/cyanheads/pubchem-mcp-server?style=social)](https://github.com/cyanheads/pubchem-mcp-server)
+
+**Empower your AI agents and scientific tools with seamless PubChem integration!**
+
+An MCP (Model Context Protocol) server providing comprehensive access to PubChem's vast chemical information database. Enables LLMs and AI agents to search, retrieve, and analyze chemical compounds, substances, and bioassays through the PubChem PUG REST API.
+
+Built on the [`cyanheads/mcp-ts-template`](https://github.com/cyanheads/mcp-ts-template), this server follows a modular architecture with robust error handling, logging, and security features.
+
+## 🚀 Core Capabilities: PubChem Tools 🛠️
+
+This server equips your AI with specialized tools to interact with PubChem:
+
+| Tool Name                                                                                       | Description                                                                     | Key Features                                                                                                                           |
+| :---------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------- |
+| [`pubchem_search_compound_by_identifier`](./src/mcp-server/tools/searchCompoundByIdentifier/)   | Searches for PubChem Compound IDs (CIDs) using a list of chemical identifiers.  | - Search by `name`, `smiles`, or `inchikey`.<br/>- Accepts multiple identifiers in a single call for bulk lookups.                     |
+| [`pubchem_fetch_compound_properties`](./src/mcp-server/tools/fetchCompoundProperties/)          | Fetches a list of specified physicochemical properties for one or more CIDs.    | - Retrieve properties like `MolecularWeight`, `XLogP`, `IUPACName`, etc.<br/>- Essential for gathering detailed chemical data in bulk. |
+| [`pubchem_get_compound_image`](./src/mcp-server/tools/getCompoundImage/)                        | Fetches a 2D image of a compound's structure for a given CID.                   | - Returns the raw image data as a binary blob.<br/>- Supports `small` (100x100) and `large` (300x300) image sizes.                     |
+| [`pubchem_search_compounds_by_structure`](./src/mcp-server/tools/searchCompoundsByStructure/)   | Performs a structural search using a SMILES string or a CID as the query.       | - Supports `substructure`, `superstructure`, and `identity` search types.<br/>- Essential for finding structurally related compounds.  |
+| [`pubchem_search_compounds_by_similarity`](./src/mcp-server/tools/searchCompoundsBySimilarity/) | Finds compounds with a similar 2D structure to a query compound.                | - Based on a Tanimoto similarity score.<br/>- Search by `smiles` or `cid`.<br/>- Configurable `threshold` and `maxRecords`.            |
+| [`pubchem_search_compounds_by_formula`](./src/mcp-server/tools/searchCompoundsByFormula/)       | Finds PubChem Compound IDs (CIDs) that match a given molecular formula.         | - Supports exact matches and formulas with additional elements.<br/>- Configurable `maxRecords`.                                       |
+| [`pubchem_fetch_substance_details`](./src/mcp-server/tools/fetchSubstanceDetails/)              | Retrieves details for a given PubChem Substance ID (SID).                       | - Fetches synonyms, source, dates, related CIDs, and full compound data in one call.                                                   |
+| [`pubchem_fetch_assay_summary`](./src/mcp-server/tools/fetchAssaySummary/)                      | Fetches detailed summaries for a list of up to 5 PubChem BioAssay IDs (AIDs).   | - Includes name, description, source, and statistics.<br/>- Supports bulk fetching for multiple AIDs.                                  |
+| [`pubchem_search_assays_by_target`](./src/mcp-server/tools/searchAssaysByTarget/)               | Finds PubChem BioAssay IDs (AIDs) associated with a specific biological target. | - Search by `genesymbol` or `proteinname`.                                                                                             |
+| [`pubchem_fetch_compound_xrefs`](./src/mcp-server/tools/fetchCompoundXrefs/)                    | Fetches external cross-references (XRefs) for a given CID.                      | - Retrieve `RegistryID`, `PubMedID`, `PatentID`, etc.<br/>- Robustly handles large datasets with pagination.                           |
+
+---
+
+## Table of Contents
+
+| [Overview](#overview) | [Features](#features) | [Installation](#installation) |
+| [Configuration](#configuration) | [Project Structure](#project-structure) |
+| [Tools](#tools) | [Development](#development) | [License](#license) |
+
+## Overview
+
+The PubChem MCP Server acts as a bridge, allowing applications (MCP Clients) that understand the Model Context Protocol (MCP) – like advanced AI assistants (LLMs), IDE extensions, or custom research tools – to interact directly and efficiently with PubChem's vast chemical database.
+
+Instead of complex API integration or manual searches, your tools can leverage this server to:
+
+- **Automate chemical research**: Search for compounds, fetch detailed properties, find similar structures, and analyze bioassay results programmatically.
+- **Gain chemical insights**: Access detailed compound data, substance information, and bioassay metadata without leaving the host application.
+- **Integrate PubChem into AI-driven science**: Enable LLMs to conduct chemical research, analyze structure-activity relationships, and support evidence-based discovery.
+
+Built on the robust `mcp-ts-template`, this server provides a standardized, secure, and efficient way to expose PubChem functionality via the MCP standard. It achieves this by integrating with the PubChem PUG REST API, ensuring compliance with rate limits and providing comprehensive error handling.
+
+> **Developer Note**: This repository includes a [.clinerules](.clinerules) file that serves as a developer cheat sheet for your LLM coding agent with quick reference for the codebase patterns, file locations, and code snippets.
+
+## Features
+
+### Core Utilities
+
+Leverages the robust utilities provided by the `mcp-ts-template`:
+
+- **Logging**: Structured, configurable logging (file rotation, stdout JSON, MCP notifications) with sensitive data redaction.
+- **Error Handling**: Centralized error processing, standardized error types (`McpError`), and automatic logging.
+- **Configuration**: Environment variable loading (`dotenv`) with comprehensive validation.
+- **Input Validation/Sanitization**: Uses `zod` for schema validation and custom sanitization logic.
+- **Request Context**: Tracking and correlation of operations via unique request IDs using `AsyncLocalStorage`.
+- **Type Safety**: Strong typing enforced by TypeScript and Zod schemas.
+- **HTTP Transport**: High-performance HTTP server using **Hono**, featuring session management with garbage collection and CORS support.
+- **Authentication**: Robust authentication layer supporting JWT and OAuth 2.1, with fine-grained scope enforcement.
+- **Deployment**: Multi-stage `Dockerfile` for creating small, secure production images with native dependency support.
+
+### PubChem Integration
+
+- **PubChem PUG REST Integration**: Comprehensive access to the PubChem API via a dedicated, rate-limited client.
+- **Advanced Search Capabilities**: Search by identifier, structure, similarity, and molecular formula.
+- **Full Compound Data**: Retrieve complete compound properties, including physicochemical data, names, and identifiers.
+- **Substance and Assay Information**: Fetch detailed records for substances (SIDs) and bioassays (AIDs).
+- **Cross-Referencing**: Find links to other databases like PubMed, patent registries, and gene databases.
+- **Image Generation**: Directly fetch 2D structural images of compounds.
+
+## Installation
+
+### Prerequisites
+
+- [Node.js (>=20.0.0)](https://nodejs.org/)
+- [npm](https://www.npmjs.com/) (comes with Node.js)
+- [Docker](https://www.docker.com/) (optional, for containerized deployment)
+
+### Install via npm (recommended)
+
+```bash
+npm install @cyanheads/pubchem-mcp-server
+```
+
+### Alternatively Install from Source
+
+1. Clone the repository:
+
+   ```bash
+   git clone https://github.com/cyanheads/pubchem-mcp-server.git
+   cd pubchem-mcp-server
+   ```
+
+2. Install dependencies:
+
+   ```bash
+   npm install
+   ```
+
+3. Build the project:
+   ```bash
+   npm run build
+   *or npm run rebuild*
+   ```
+
+## Configuration
+
+### Environment Variables
+
+Configure the server using environment variables. These environmental variables are set within your MCP client config/settings (e.g. `cline_mcp_settings.json` for Cline).
+
+| Variable              | Description                                                                              | Default     |
+| --------------------- | ---------------------------------------------------------------------------------------- | ----------- |
+| `MCP_TRANSPORT_TYPE`  | Transport mechanism: `stdio` or `http`.                                                  | `stdio`     |
+| `MCP_HTTP_PORT`       | Port for the HTTP server (if `MCP_TRANSPORT_TYPE=http`).                                 | `3010`      |
+| `MCP_HTTP_HOST`       | Host address for the HTTP server (if `MCP_TRANSPORT_TYPE=http`).                         | `127.0.0.1` |
+| `MCP_ALLOWED_ORIGINS` | Comma-separated list of allowed origins for CORS (if `MCP_TRANSPORT_TYPE=http`).         | (none)      |
+| `MCP_LOG_LEVEL`       | Logging level (`debug`, `info`, `notice`, `warning`, `error`, `crit`, `alert`, `emerg`). | `info`      |
+| `LOG_OUTPUT_MODE`     | Logging output mode: `file` or `stdout`.                                                 | `file`      |
+| `MCP_AUTH_MODE`       | Authentication mode for HTTP: `jwt` or `oauth`.                                          | `jwt`       |
+| `MCP_AUTH_SECRET_KEY` | **Required for `jwt` auth.** Minimum 32-character secret key for JWT authentication.     | (none)      |
+| `LOGS_DIR`            | Directory for log file storage (if `LOG_OUTPUT_MODE=file`).                              | `logs/`     |
+
+**Note**: The PubChem API does not require an API key for basic use, so no key is needed in the environment configuration.
+
+### MCP Client Settings
+
+Add the following to your MCP client's configuration file (e.g., `cline_mcp_settings.json`). This configuration uses `npx` to run the server, which will automatically install the package if not already present:
+
+```json
+{
+  "mcpServers": {
+    "pubchem-mcp-server": {
+      "command": "npx",
+      "args": ["@cyanheads/pubchem-mcp-server"],
+      "env": {},
+      "disabled": false,
+      "autoApprove": []
+    }
+  }
+}
+```
+
+## Project Structure
+
+The codebase follows a modular structure within the `src/` directory:
+
+```
+src/
+├── index.ts              # Entry point: Initializes and starts the server
+├── config/               # Configuration loading (env vars, package info)
+│   └── index.ts
+├── mcp-server/           # Core MCP server logic and capability registration
+│   ├── server.ts         # Server setup, capability registration
+│   ├── transports/       # Transport handling (stdio, http)
+│   └── tools/            # MCP Tool implementations (subdirs per tool)
+├── services/             # External service integrations
+│   └── pubchem/          # PubChem API client
+├── types-global/         # Shared TypeScript type definitions
+└── utils/                # Common utility functions (logger, error handler, etc.)
+```
+
+For a detailed file tree, run `npm run tree` or see [docs/tree.md](docs/tree.md).
+
+## Tools
+
+The PubChem MCP Server provides a comprehensive suite of tools for chemical information retrieval, callable via the Model Context Protocol.
+
+| Tool Name                                | Description                                                             | Key Arguments                                     |
+| :--------------------------------------- | :---------------------------------------------------------------------- | :------------------------------------------------ |
+| `pubchem_search_compound_by_identifier`  | Searches for CIDs using a list of identifiers (name, SMILES, InChIKey). | `identifierType`, `identifiers`                   |
+| `pubchem_fetch_compound_properties`      | Fetches physicochemical properties for one or more CIDs.                | `cids`, `properties`                              |
+| `pubchem_get_compound_image`             | Fetches a 2D structural image for a given CID.                          | `cid`, `size?`                                    |
+| `pubchem_search_compounds_by_structure`  | Performs a structural search (substructure, superstructure, identity).  | `searchType`, `query`, `queryType`, `maxRecords?` |
+| `pubchem_search_compounds_by_similarity` | Finds compounds with a similar 2D structure to a query.                 | `query`, `queryType`, `threshold?`, `maxRecords?` |
+| `pubchem_search_compounds_by_formula`    | Finds CIDs that match a given molecular formula.                        | `formula`, `allowOtherElements?`, `maxRecords?`   |
+| `pubchem_fetch_substance_details`        | Retrieves details for a given Substance ID (SID).                       | `sid`                                             |
+| `pubchem_fetch_assay_summary`            | Fetches summaries for a list of up to 5 BioAssay IDs (AIDs).            | `aids`                                            |
+| `pubchem_search_assays_by_target`        | Finds BioAssay IDs (AIDs) associated with a biological target.          | `targetType`, `targetQuery`                       |
+| `pubchem_fetch_compound_xrefs`           | Fetches external cross-references for a given CID.                      | `cid`, `xrefTypes`, `page?`, `pageSize?`          |
+
+_Note: All tools support comprehensive error handling and return structured JSON responses._
+
+## Development
+
+### Build and Test
+
+```bash
+# Build the project (compile TS to JS in dist/ and make executable)
+npm run build
+
+# Test the server locally using the MCP inspector tool (stdio transport)
+npm run inspector
+
+# Test the server locally using the MCP inspector tool (http transport)
+npm run inspector:http
+
+# Clean build artifacts
+npm run clean
+
+# Generate a file tree representation for documentation
+npm run tree
+
+# Clean build artifacts and then rebuild the project
+npm run rebuild
+
+# Format code with Prettier
+npm run format
+
+# Start the server using stdio (default)
+npm start
+# Or explicitly:
+npm run start:stdio
+
+# Start the server using HTTP transport
+npm run start:http
+```
+
+## License
+
+This project is licensed under the Apache License 2.0 - see the [LICENSE](LICENSE) file for details.
+
+---
+
+<div align="center">
+Built with the <a href="https://modelcontextprotocol.io/">Model Context Protocol</a>
+</div>

package/dist/config/index.d.ts

@@ -0,0 +1,98 @@
+/**
+ * @fileoverview Loads, validates, and exports application configuration.
+ * This module centralizes configuration management, sourcing values from
+ * environment variables and `package.json`. It uses Zod for schema validation
+ * to ensure type safety and correctness of configuration parameters.
+ *
+ * Key responsibilities:
+ * - Load environment variables from a `.env` file.
+ * - Read `package.json` for default server name and version.
+ * - Define a Zod schema for all expected environment variables.
+ * - Validate environment variables against the schema.
+ * - Construct and export a comprehensive `config` object.
+ * - Export individual configuration values like `logLevel` and `environment` for convenience.
+ *
+ * @module src/config/index
+ */
+/**
+ * Main application configuration object.
+ * Aggregates settings from validated environment variables and `package.json`.
+ */
+export declare const config: {
+    /** Information from package.json. */
+    pkg: {
+        name: string;
+        version: string;
+    };
+    /** MCP server name. Env `MCP_SERVER_NAME` > `package.json` name > "mcp-ts-template". */
+    mcpServerName: string;
+    /** MCP server version. Env `MCP_SERVER_VERSION` > `package.json` version > "0.0.0". */
+    mcpServerVersion: string;
+    /** Logging level. From `MCP_LOG_LEVEL` env var. Default: "debug". */
+    logLevel: string;
+    /** Absolute path to the logs directory. From `LOGS_DIR` env var. */
+    logsPath: string;
+    /** Runtime environment. From `NODE_ENV` env var. Default: "development". */
+    environment: string;
+    /** MCP transport type ('stdio' or 'http'). From `MCP_TRANSPORT_TYPE` env var. Default: "stdio". */
+    mcpTransportType: "stdio" | "http";
+    /** HTTP server port (if http transport). From `MCP_HTTP_PORT` env var. Default: 3010. */
+    mcpHttpPort: number;
+    /** HTTP server host (if http transport). From `MCP_HTTP_HOST` env var. Default: "127.0.0.1". */
+    mcpHttpHost: string;
+    /** Array of allowed CORS origins (http transport). From `MCP_ALLOWED_ORIGINS` (comma-separated). */
+    mcpAllowedOrigins: string[] | undefined;
+    /** Auth secret key (JWTs, http transport). From `MCP_AUTH_SECRET_KEY`. CRITICAL. */
+    mcpAuthSecretKey: string | undefined;
+    /** The authentication mode ('jwt' or 'oauth'). From `MCP_AUTH_MODE`. */
+    mcpAuthMode: "jwt" | "oauth";
+    /** OAuth 2.1 Issuer URL. From `OAUTH_ISSUER_URL`. */
+    oauthIssuerUrl: string | undefined;
+    /** OAuth 2.1 JWKS URI. From `OAUTH_JWKS_URI`. */
+    oauthJwksUri: string | undefined;
+    /** OAuth 2.1 Audience. From `OAUTH_AUDIENCE`. */
+    oauthAudience: string | undefined;
+    /** OpenRouter App URL. From `OPENROUTER_APP_URL`. Default: "http://localhost:3000". */
+    openrouterAppUrl: string;
+    /** OpenRouter App Name. From `OPENROUTER_APP_NAME`. Defaults to `mcpServerName`. */
+    openrouterAppName: string;
+    /** OpenRouter API Key. From `OPENROUTER_API_KEY`. */
+    openrouterApiKey: string | undefined;
+    /** Default LLM model. From `LLM_DEFAULT_MODEL`. */
+    llmDefaultModel: string;
+    /** Default LLM temperature. From `LLM_DEFAULT_TEMPERATURE`. */
+    llmDefaultTemperature: number | undefined;
+    /** Default LLM top_p. From `LLM_DEFAULT_TOP_P`. */
+    llmDefaultTopP: number | undefined;
+    /** Default LLM max tokens. From `LLM_DEFAULT_MAX_TOKENS`. */
+    llmDefaultMaxTokens: number | undefined;
+    /** Default LLM top_k. From `LLM_DEFAULT_TOP_K`. */
+    llmDefaultTopK: number | undefined;
+    /** Default LLM min_p. From `LLM_DEFAULT_MIN_P`. */
+    llmDefaultMinP: number | undefined;
+    /** OAuth Proxy configurations. Undefined if no related env vars are set. */
+    oauthProxy: {
+        authorizationUrl: string | undefined;
+        tokenUrl: string | undefined;
+        revocationUrl: string | undefined;
+        issuerUrl: string | undefined;
+        serviceDocumentationUrl: string | undefined;
+        defaultClientRedirectUris: string[] | undefined;
+    } | undefined;
+    /** Supabase configuration. Undefined if no related env vars are set. */
+    supabase: {
+        url: string;
+        anonKey: string;
+        serviceRoleKey: string | undefined;
+    } | undefined;
+};
+/**
+ * Configured logging level for the application.
+ * Exported for convenience.
+ */
+export declare const logLevel: string;
+/**
+ * Configured runtime environment ("development", "production", etc.).
+ * Exported for convenience.
+ */
+export declare const environment: string;