Browse

Node.js server implementing Model Context Protocol (MCP) for filesystem operations.

<!-- mcp-name: io.github.modelcontextprotocol/server-git -->

**[Architecture](docs/architecture.md) | [Project Structure](docs/structure.md) | [Startup Process](docs/startup.md) | [Server Features](docs/features.md) | [Extension Points](docs/extension.md) | [How It Works](docs/how-it-works.md)**

A basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across chats.

An MCP server implementation that provides a tool for dynamic and reflective problem-solving through a structured thinking process.

Fastify adapters for the MCP TypeScript server SDK.

A CLI tool that dynamically builds commands based on schemas retrieved from MCP servers that can be executed against the configured MCP server.

Uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails.

> [!IMPORTANT] **This is the `main` branch which contains v2 of the SDK (currently in development, pre-alpha).** > > We anticipate a stable v2 release in Q1 2026. Until then, **v1.x remains the recommended version** for production use. v1.x will continue to receive bug fixes and security updates for at least 6 months after v2 ships to give people time to upgrade. > > For v1 documentation, see the [V1 API docs](https://ts.sdk.modelcontextprotocol.io/). For v2 API docs, see [`/v2/`](https://ts.sdk.modelcontextprotocol.io/v2/).

Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works with multi-package repos, or single-package repos to help you version and publish your code. You can find the full documentation for it [in our repository](https://github.com/changesets/changesets)

[](https://goreportcard.com/report/github.com/github/github-mcp-server)

The purpose of the E2E tests is to have a simple (currently) test that gives maintainers some confidence in the black box behavior of our artifacts. It does this by: * Building the `github-mcp-server` docker image * Running the image * Interacting with the server via stdio * Issuing requests that interact with the live GitHub API

[](https://npmjs.org/package/chrome-devtools-mcp)

<!-- mcp-name: io.github.modelcontextprotocol/server-fetch -->

<!-- mcp-name: io.github.modelcontextprotocol/server-time -->

This directory contains runnable MCP **client** examples built with `@modelcontextprotocol/client`.

This directory contains runnable MCP **server** examples built with `@modelcontextprotocol/server` plus framework adapters:

The MCP (Model Context Protocol) TypeScript client SDK. Build MCP clients that connect to MCP servers.

The packages in `packages/middleware/*` are **thin integration layers** that help you expose an MCP server in a specific runtime, platform, or web framework.

The MCP (Model Context Protocol) TypeScript server SDK. Build MCP servers that expose tools, resources, and prompts.