Pine Labs SDK API Documentation MCP Server

io.github.prakhargour10Published by GitHub account prakhargour10v1.2.0Updated Oct 24, 2026

List and fetch official Pine Labs SDK API documentation via MCP tools.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Lets an assistant list and fetch official Pine Labs SDK API documentation through MCP tools.

What you can do
This server exposes MCP tools for browsing and retrieving official Pine Labs SDK API documentation. An assistant can list available documentation entries and fetch their contents so answers about Pine Labs SDK APIs are grounded in the official reference. It runs locally over stdio and is intended for desktop use.
When to use it
Use it when you are integrating with Pine Labs SDKs and want an assistant to look up official API documentation while coding. It is most useful for developers who need quick, reference-backed answers about Pine Labs SDK endpoints and usage.
Requirements
Runs as a local process on the user's machine over stdio; desktop only, not available as a web executable. A container image is published for streamable-http transport. No authentication, environment variables, or headers are declared.
Before you install
The server fetches documentation from an external source, so requests may leave your machine. No credentials, payments, or write actions are declared, but review the source before relying on it for production decisions.

Installation

In SourceWeft

  1. Open Pine Labs SDK API Documentation MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.2.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.