Skip to main content
Glama

Why?

LLMs often have outdated knowledge about mobile SDKs. mobile-docs-mcp solves this by:

  • Fetching live documentation from official sources and converting it to clean markdown

  • Querying package registries for the latest versions in real-time

  • Pulling open GitHub issues so the LLM knows about current bugs and limitations

  • Caching everything locally (24h TTL) for fast, offline-friendly responses


Related MCP server: Library Docs MCP Server

Supported SDKs

Adding a new SDK is as simple as dropping a JSON file into the sdks/ directory.


Tools

iDocumentation

Tool

Description

list_sdks

List all available SDKs with their categories and documentation pages

search_docs

Full-text search across all SDK documentation, returns relevant sections

refresh_docs

Invalidate cache and re-fetch documentation (all or specific SDK)

Package Registries

Tool

Description

search_packages

Search for packages across npm, pub.dev, CocoaPods, Maven Central, or PyPI

get_package_info

Get latest version, license, homepage, and repository for any package

GitHub

Tool

Description

get_github_issues

Fetch open issues from any GitHub repo with optional label filtering


Package Registries


Getting Started

Quick Start (npx — no install needed)

Run directly without installing:

npx @freeapptools/mobile-docs-mcp

Configure Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "mobile-docs-mcp": {
      "command": "npx",
      "args": ["-y", "@freeapptools/mobile-docs-mcp"],
      "env": {
        "GITHUB_TOKEN": "ghp_your_token_here"
      }
    }
  }
}

GITHUB_TOKEN is optional but recommended to avoid GitHub API rate limits (60 → 5,000 requests/hour).

Configure Claude Code

Add to your Claude Code settings:

{
  "mcpServers": {
    "mobile-docs-mcp": {
      "command": "npx",
      "args": ["-y", "@freeapptools/mobile-docs-mcp"]
    }
  }
}

Global Install (optional)

If you prefer a permanent installation:

npm install -g @freeapptools/mobile-docs-mcp

Then use mobile-docs-mcp directly as the command instead of npx.


Adding a New SDK

Create a JSON file in the sdks/ directory:

{
  "name": "YourSDK",
  "version": "latest",
  "baseUrl": "https://docs.yoursdk.com",
  "docs": [
    {
      "category": "Getting Started",
      "pages": [
        {
          "title": "Installation",
          "url": "https://docs.yoursdk.com/install"
        },
        {
          "title": "Quick Start",
          "url": "https://docs.yoursdk.com/quickstart"
        }
      ]
    }
  ]
}

That's it. The server picks it up automatically on next startup.


Configuration

docs-config.json in the project root:

{
  "cacheTtlMs": 86400000,
  "cacheDir": ".cache",
  "sdksDir": "./sdks"
}

Field

Default

Description

cacheTtlMs

86400000 (24h)

Cache time-to-live in milliseconds

cacheDir

.cache

Local cache directory path

sdksDir

./sdks

Directory containing SDK JSON files

Override the config path with the DOCS_CONFIG_PATH environment variable.


Development

# Watch mode
npm run dev

# Run tests (82 tests)
npm test

# Build
npm run build

Project Structure

mobile-docs-mcp/
├── src/
│   ├── index.ts          # Entry point — stdio transport
│   ├── config.ts         # Config loading + Zod validation
│   ├── tools.ts          # 6 MCP tool registrations
│   ├── resources.ts      # MCP resource registrations
│   ├── registry.ts       # Package registry API handlers
│   ├── github.ts         # GitHub issues API
│   ├── fetcher.ts        # HTML → Markdown conversion
│   ├── cache.ts          # File-based cache with TTL
│   ├── parser.ts         # Markdown section parser
│   ├── search.ts         # Full-text search engine
│   ├── types.ts          # TypeScript interfaces
│   └── __tests__/        # 82 unit tests
├── sdks/                 # SDK documentation configs (28 files)
├── docs-config.json      # Global configuration
├── package.json
└── tsconfig.json

License

MIT

Available Tools

6 tools
get_github_issuesA

Get recent open GitHub issues for a repository. Useful for checking known bugs and feature requests.

Inputs: repo (required), limit, labels.

get_package_infoA

Get detailed info about a specific package (latest version, license, homepage, repository)

Inputs: name (required), registry (required).

list_sdksA

List all available SDK documentation sources with categories

Inputs: no named parameters.

refresh_docsB

Refresh cached documentation. Optionally specify an SDK name to refresh only that SDK.

Inputs: sdk.

search_docsB

Search across all SDK documentation. Returns relevant sections matching the query.

Inputs: query (required), sdk.

search_packagesB

Search for packages/libraries in a package registry (npm, pub.dev, CocoaPods, Maven Central, PyPI)

Inputs: query (required), registry (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct area: SDK listing, doc search, doc cache refresh, package search, package details, and GitHub issues. There is slight potential overlap between list_sdks and search_docs, but descriptions make the boundary clear.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: list_, search_, refresh_, get_. No mixed conventions or vague verbs.

    Tool Count5/5

    Six tools is well-scoped for a mobile documentation and package-lookup server. Each tool serves a clear purpose without redundancy or bloat.

    Completeness4/5

    The core workflows—discovering SDKs, searching docs, looking up packages, and checking repository issues—are covered. Minor gaps exist such as no full-document retrieval endpoint, but agents can work around this via search_docs.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server implementation that provides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context
      20 npm
      263
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      An MCP server that fetches real-time documentation for popular libraries like Langchain, Llama-Index, MCP, and OpenAI, allowing LLMs to access updated library information beyond their knowledge cut-off dates.
      1
      3
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Generic MCP server that exposes Markdown documentation to LLMs, enabling them to search and answer questions about any software documentation.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Local MCP server that indexes documentation from URLs/files into a vector database, enabling coding agents to search and use up-to-date library and API documentation.
      1
      -