Skip to main content
Glama
AtlasRepo MCP
by Arnon-hs

Purpose

AtlasRepo MCP adapts the public AtlasRepo catalog contract to Model Context Protocol clients. It supports local stdio and hosted Streamable HTTP, exposes three bounded read-only tools, and contains no private scoring, account or billing logic.

Owns

Does not own

MCP protocol, schemas and tool descriptions

Catalog ingestion, scoring or moderation

Bounded API client, timeouts and result truncation

Authentication, accounts or payments

stdio executable and Streamable HTTP endpoint

Web/Admin UI or database access

Origin/host validation and health endpoints

Arbitrary URL fetching or code execution

Related MCP server: capalith

Architecture

flowchart LR
  Client["MCP client"] -->|"stdio"| Server["AtlasRepo MCP"]
  Remote["Remote MCP client"] -->|"Streamable HTTP /mcp"| Server
  Server --> Validate["Zod input validation"]
  Validate --> Tools{"Read-only tools"}
  Tools --> Recommend["atlasrepo_recommend"]
  Tools --> Search["atlasrepo_search_tools"]
  Tools --> Repo["atlasrepo_get_repository"]
  Recommend --> API["Public AtlasRepo API"]
  Search --> API
  Repo --> API

Tools

Tool

Input

Result

atlasrepo_recommend

A bounded problem/use-case query

Evidence-backed repository recommendations

atlasrepo_search_tools

Search text and bounded filters

Matching tools from the approved catalog

atlasrepo_get_repository

Repository owner and name

One repository evidence record

All inputs are schema-validated. Upstream calls have a timeout and responses are truncated to a safe maximum. The connector never executes discovered repositories.

Technology

Area

Choice

Language/runtime

TypeScript, Node.js 20+

Protocol

Model Context Protocol SDK

HTTP

Express 5, Streamable HTTP

Validation

Zod 4

Distribution

npm executable and Docker/Zeabur service

Install in one command

Install the AtlasRepo plugin for Codex with the same command shown in the AtlasRepo account:

codex plugin marketplace add Arnon-hs/atlasrepo-mcp && codex plugin add atlasrepo@atlasrepo

The plugin connects to the hosted Streamable HTTP service at https://mcp.atlasrepo.com/mcp. The public catalog tools are read-only; account quota and connected OAuth clients are shown in the AtlasRepo API connections panel.

Local development

npm ci
npm run check
npm test
npm run build
npm run readiness:store
node dist/index.js

HTTP service

PORT=8080 MCP_ALLOWED_HOSTS=localhost npm run start:http

Variable

Purpose

ATLASREPO_API_BASE_URL

Upstream public API origin

ATLASREPO_API_KEY

Optional upstream key; keep secret

ATLASREPO_REQUEST_TIMEOUT_MS

Bounded upstream timeout

PORT

HTTP listener port

MCP_ALLOWED_HOSTS

Comma/space/semicolon-separated Host allowlist

Use .env.example as the non-secret template. Never remove immutable or inherited Zeabur variables.

Verification, deployment and publishing

Every pull request runs secret-free hosted quality gates. After merge, the trusted main workflow runs on one ephemeral JIT runner and performs:

  1. Build and test - typecheck, tests, package smoke and dependency audit.

  2. Image verification - build and inspect the production Docker image.

This repository does not deploy, migrate or probe production from its main workflow. Production releases are owned by the pinned contract in Arnon-hs/atlasrepo-schema/.github/workflows/release.yml, which deploys services sequentially and verifies the release. npm publication is separate: create a reviewed semantic-version tag and let the trusted-publishing workflow publish the package.

Engineering rules

  • Preserve read-only behavior and bounded inputs, timeouts and result sizes.

  • Keep stdout protocol-clean in stdio mode; diagnostics go to stderr without secrets.

  • Never log API keys, authorization headers or full upstream payloads.

  • Add schemas and tests with every tool/contract change.

  • Conventional Commits: feat(mcp): ..., fix(http): ..., docs(mcp): ....

Pull request checklist

  • npm run check, npm test, npm run build and npm run smoke pass.

  • stdio stdout contains protocol messages only.

  • HTTP host/origin protections and health contracts remain intact.

  • No private Platform/Scout logic or write operation was added.

  • The main JIT workflow built and inspected the MCP container image.

  • Any production release was initiated only from the Schema release contract.

License

MIT. See LICENSE.

Available Tools

3 tools
atlasrepo_get_repositoryGet AtlasRepo repository evidenceA

Load the AtlasRepo decision record and linked evidence for one GitHub repository.

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

atlasrepo_recommendRecommend open-source solutionsA

Find evidence-backed repositories and workflows for a concrete engineering or content-production problem.

Inputs: query (required), limit.

atlasrepo_search_toolsSearch AtlasRepo toolsB

Search normalized open-source tools by text, kind, and quality threshold.

Inputs: q, kind, minQuality.

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 3 tools

    Disambiguation4/5

    The tools are mostly distinct: atlasrepo_recommend is problem-driven, atlasrepo_search_tools is structured query-based, and atlasrepo_get_repository is a targeted detail fetch. However, recommend and search_tools could both return repositories/tools, so an agent might occasionally be unsure which path to use for discovery.

    Naming Consistency4/5

    All tools share the atlasrepo_ prefix and use a verb-first style. atlasrepo_search_tools and atlasrepo_get_repository follow a clear verb_noun pattern, but atlasrepo_recommend lacks an object, creating a minor inconsistency.

    Tool Count5/5

    Three tools is well-scoped for this domain: one for problem-level recommendation, one for structured search, and one for inspecting a specific repository record. Each tool covers a distinct part of the workflow without redundancy.

    Completeness4/5

    The read-only decision-record workflow is well covered: discover by problem, search by criteria, and load detailed evidence for a repository. Minor gaps include no explicit list-all/browse capability or a dedicated workflow-detail fetch, but these are workable through the existing tools.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables read-only access to a local-first catalog of portable agent skills, exposing tools to discover ranked matches, inspect stored artifacts, traverse declared relationships, and view configuration.
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to read-only query a self-hosted repository knowledge base, searching documents, source code, and symbols across GitHub and GitLab imports while retrieving source and dependency traces by commit and path.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to generated technical documentation across one or multiple documented repositories, exposing tools to search code and docs, inspect modules and symbols, list gaps, review architecture, and check freshness with file#line citations.
      MIT