mcp s-schemas

MCP Servers Schemas acts as a catalog of MCP server definitions. It does not itself run as an active MCP server in this repository; instead, it provides JSON schema definitions and tool definitions for a variety of MCP servers (as referenced in the Official Integrations table). You can browse or download the JSON schema files under the schemas/ directory (for example, schemas/mcp-server-axiom.json, schemas/mcp-server-browserbase.json, etc.), which describe the latest basic information and the tools available for each server. Use these definitions to understand what each MCP server exposes (capabilities, endpoints, and configuration options) and how an LLM or client might interact with them. If a server definition includes a schema link, you can fetch that JSON to understand the expected structure and commands to invoke the server’s tools.

Prerequisites:

• A working development environment with Git installed.
• Access to the repository hosting these MCP server schemas.

Steps:

1. Clone the repository: git clone https://github.com/your-org/oslook-mcp-servers-schemas.git cd oslook-mcp-servers-schemas

2. Browse the available schemas and schemas directory to view the MCP server definitions:

   • schemas/mcp-server-axiom.json
   • schemas/mcp-server-browserbase.json
   • schemas/mcp-server-cloudflare.json ...and so on

3. If you want to programmatically use a schema, fetch the JSON file from the repository or its raw URL and parse it in your application to understand the server’s capabilities and tool definitions.

4. If you maintain a local MCP runtime, you can integrate these schema definitions into your tooling by loading the JSON files and validating responses against the defined schema.

Tips:

• The repository focuses on providing up-to-date schema definitions for various MCP servers. If you need definitions for a specific server, check the referenced Schema links in the Official Integrations table.
• Some entries in the table may not include a schema file; if so, there is no dedicated JSON schema available in this repository yet for that server.
• The site and docs are designed to help users retrieve server definitions without installing a local MCP server; use the schemas as a source of truth for integration.
• When automating retrieval, prefer fetching the JSON files directly from the schemas/ directory to ensure you’re using the latest version.

Environment variables and configuration options are defined within each individual server’s schema (e.g., what tools are exposed, required credentials, and usage patterns). Review the specific mcp-server-*.json files for details.