MCP Server for TypeScript SDK Context

Created By
DotNaosa year ago
Overview

What is MCP Server for TypeScript SDK Context?

MCP Server for TypeScript SDK Context is a server implementation designed to provide context about the modelcontextprotocol/typescript-sdk repository and its documentation.

How to use MCP Server?

To use the MCP Server, install the dependencies, configure your environment with a GitHub Personal Access Token, build the server, and then run it either directly or via an MCP client like VS Code.

Key features of MCP Server?

  • Fetches file content directly from the modelcontextprotocol/typescript-sdk GitHub repository.
  • Allows searching for code within the repository using the GitHub API.
  • Includes a placeholder for searching the official documentation website.

Use cases of MCP Server?

  1. Retrieving specific file contents from the TypeScript SDK repository.
  2. Searching for code snippets or functions within the repository.
  3. Integrating with documentation search tools for enhanced user experience.

FAQ from MCP Server?

  • How do I set up the MCP Server?

Follow the setup instructions to install dependencies, configure your environment, and build the server.

  • Can I use this server with other programming languages?

This server is specifically designed for the TypeScript SDK context, but similar implementations can be created for other languages.

  • Is there a way to enhance the documentation search feature?

Yes, integrating with an external search tool like Bing Search can enhance the documentation search functionality.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
DotNaos
Star
0
Language
JavaScript
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)

a day ago