Przejdź do treści
Biblioteka skilli
Programowanie · Integracja z narzędziem

adding-mcp-store-servers

/adding-mcp-store-servers

Dodaje zewnętrzny serwer MCP (Linear, Notion, GitHub) do katalogu sklepu MCP PostHog: znajduje endpoint, sonduje go, pisze wpis katalogowy i weryfikuje.

Repozytorium
posthog ↗
Licencja
MIT
Ostatnia zmiana repozytorium
26.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
4
Przestarzałość

Brak sygnałów. Repozytorium zmienione 26.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Dodaje zewnętrzny serwer MCP (Linear, Notion, GitHub) do katalogu sklepu MCP PostHog: znajduje endpoint, sonduje go, pisze wpis katalogowy i weryfikuje.

Wyzwalacze z opisu

add X to the MCP store
Oryginalny opis (EN)

Add a third-party MCP server (Linear, Notion, GitHub, ...) to the PostHog MCP store catalog. Use when asked to "add X to the MCP store", expand the MCP server marketplace, or fix a broken catalog entry. Covers finding the vendor's remote MCP endpoint, probing it (handshake, OAuth discovery, DCR), authoring the catalog entry in products/mcp_store/backend/catalog.py, verification tiers, and the operator handoff for servers without Dynamic Client Registration.

Jak działa

  1. Read first
  2. Workflow
  3. Operator checklist for oauthshared servers (paste into the PR)
  4. What not to do
Sekcje z nagłówków SKILL.md, w oryginale · 79 linii, 846 słów
Podgląd SKILL.md
---
name: adding-mcp-store-servers
description: Add a third-party MCP server (Linear, Notion, GitHub, ...) to the PostHog MCP store catalog. Use when asked to "add X to the MCP store", expand the MCP server marketplace, or fix a broken catalog entry. Covers finding the vendor's remote MCP endpoint, probing it (handshake, OAuth discovery, DCR), authoring the catalog entry in products/mcp_store/backend/catalog.py, verification tiers, and the operator handoff for servers without Dynamic Client Registration.
---

# Adding a server to the MCP store

The MCP store catalog is code: one entry in `products/mcp_store/backend/catalog.py` per server.
On deploy, `sync_mcp_server_templates` upserts entries into `MCPServerTemplate` rows in every environment — there are no data migrations, no icon assets, and no manual admin steps for most servers.
Adding a server is a small PR to that file.

## Read first

- `products/mcp_store/README.md` — the catalog pipeline, sync semantics, and operator runbook
- `products/mcp_store/backend/catalog.py` — existing entries; match their tone and shape
- `products/mcp_store/backend/probe.py` — what the probe verifies and what `passed_activation_gate` means

## Workflow

1. **Find the vendor's remote MCP endpoint.**
   Check the vendor's docs (search "<vendor> MCP server"); most publish a hosted endpoint like `https://mcp.<vendor>.com/mcp`.
   Only hosted (remote) MCP servers belong in the catalog — local/stdio servers do not.
   Cross-check public MCP registries if the docs are unclear.

2. **Probe it.**

   ```sh
   DEBUG=1 python manage.py probe_mcp_server https://mcp.example.com/mcp
   ```

   The JSON verdict tells you everything the entry needs:
   - `speaks_mcp: false` → the probe could not verify MCP. Stop and re-research — with one exception: `reachable: true` plus the error "Initialize was rejected and no OAuth metadata was discovered" is the auth-walled API-key case (last bullet below).
   - `auth_flavor: "oauth_dcr"` with `passed_activation_gate: true` → OAuth with Dynamic Client Registration. The entry is `auth_type="oauth"` and will **activate automatically on merge**.
   - `auth_flavor: "oauth_shared"` → OAuth without DCR. The entry is `auth_type="oauth"` but normally ships **inactive**; an operator must register an OAuth app with the vendor and paste credentials in Django admin (see the operator checklist below — include it in your PR description). If PostHog already provisions that exact OAuth app through an instance credential source, declare the reviewed source instead; catalog sync verifies and activates it without copying secrets.
   - `auth_flavor: "open"` → the handshake completed without credentials. `auth_type="api_key"`; activates automatically on merge.
   - `auth_flavor: "api_key_or_unknown"` with `reachable: true` → an auth-walled API-key server; a bare 401/403 gives the probe no MCP evidence. `auth_type="api_key"`, but the entry ships **inactive** — verify it with a real install (Gate B) before adding it, and note in the PR that an operator flips it active in Django admin per environment (users bring their own key; nothing to provision).

3. **Author the entry** in `catalog.py`, alphabetically by name:
   - `name` — the vendor's own casing ("PagerDuty", not "Pagerduty").
   - `description` — one sentence, sentence case, verb-first, matching the existing entries ("Manage Linear issues, projects, and team workflows."). No marketing copy.
   - `category` — the closest of `business` / `data` / `design` / `dev` / `infra` / `productivity`.
   - `icon_domain` — the vendor's primary brand domain (`linear.app`, not `mcp.linear.app`). Verify logo.dev has it: `GET /api/projects/@current/hog_functions/icons/?query=<vendor>` from a dev session, or check `https://img.logo.dev/<domain>` renders a real logo.
   - `docs_url` — the vendor's MCP docs page when they have one.

4. **Verify end-to-end when you can (Gate B).**
   The probe covers everything up to the OAuth consent screen.
   If you have an account with the vendor, complete one real install in local dev: run the stack, install the server from the store UI, finish the OAuth flow (or paste an API key), and confirm the tool list populates.
   Record the verification tier in the PR description:
   - **Tier 1**: probe passed + real install verified (tools listed).
   - **Tier 2**: probe passed only (no vendor account available).

5. **Run the checks.**

   ```sh
   hogli test products/mcp_store/backend/test/test_catalog_sync.py
   ```

   `test_catalog_entries_are_valid` catches malformed entries (bad category, duplicate URL, unnormalized icon_domain) before they hit production.

6. **Open the PR** — one server per PR, on an `mcp-store/`-prefixed branch (e.g. `mcp-store/add-pagerduty`), with a `feat(mcp-store)` title: `feat(mcp-store): add <name> to the MCP server catalog`.
   State the probe verdict and verification tier in the description.
   For `oauth_shared` servers without an existing instance credential source, include the operator checklist so activation isn't forgotten.

## Operator checklist for oauth_shared servers (paste into the PR)

```md
This server does not support Dynamic Client Registration, so it ships inactive. To activate (per environment, US and EU):

- [ ] Register an OAuth app in the vendor's developer console
- [ ] Redirect URI: `https://us.posthog.com/api/mcp_store/oauth_redirect/` (and the EU equivalent)
- [ ] Paste client ID + secret into Django admin → MCP server templates → <name>
- [ ] OAuth metadata was auto-discovered by the sync; run the "Discover metadata" admin action only if it's empty
- [ ] Tick "is active"
```

## What not to do

- Don't add entries with unprobed URLs — a dead catalog entry is user-visible breakage.
- Don't edit `is_active`, `oauth_credentials`, or `oauth_metadata` expectations into the catalog — those are operational state owned by the row, not by code.
- Don't add an instance credential source for a newly registered vendor app. Sources are only for an existing client already provisioned across every target environment, with exact trusted issuer, authorization, and token endpoints enforced before any secret is used.
- Don't add icon assets or `icon_key` values — icons resolve from `icon_domain` via logo.dev at render time.
- Don't batch unrelated servers into one PR unless explicitly doing a scaffold sweep; per-server PRs keep review and reverts clean.

Wersje

W bazie nie ma innych skilli o nazwie adding-mcp-store-servers.

Migawka bazy z 13.11.2026 · wersja paczki e0e3317a22ce (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 90add-entry
    Dodaje lub poprawia pozycję w katalogu Gearlist, np. narzędzie, serwer MCP lub platformę, także z kolejki gwiazdek.
  • 90adding-an-operation
    Prowadzi przez ścieżkę operacji od katalogu do handlera, sklepu, CLI, MCP i testów.
  • 100dynamic-client-registration
    Wspiera OAuth 2.0 Dynamic Client Registration w serwerach autoryzacji, przy budowie lub przeglądzie zarządzania klientami dla ekosystemów MCP.
  • 100add-mcp-integration
    Dodaje zdalny serwer MCP dostawcy do wbudowanego katalogu integracji, sprawdzając obsługę OAuth, ikonę, pliki pakietu, generatory, kontrole CI i pull request.
  • 100mcp-catalog
    Wyszukuje, ocenia i dodaje serwery MCP do sprawdzonego katalogu serwowanego przez lagune.ai do Lagune Code oraz aktualizuje lub usuwa wpisy.
  • 100mcp-catalog
    Szuka, sprawdza i dodaje serwery MCP do przeglądanego katalogu obsługiwanego przez lagune.ai, a także zmienia lub usuwa wpisy.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.