Directory listings and one-click install badges (VS Code, Cursor, Smithery, Glama, awesome-mcp-servers)

Aberta
#178 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
2/5
Tempo estimado
Meio dia
Facilidade para iniciantes
40/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
json, markdown, typescript, vscode

Direção de pesquisa

The badges should be generated from the same MCP config JSON that the README already uses, so start by finding that config and the README install section. Build the vscode:mcp/install?... and Cursor deeplinks from it, then test them in VS Code and Cursor on Windows. The directory submissions (Glama, Smithery, PulseMCP, mcpservers.org, awesome-mcp-servers) are external and need a maintainer's account, so a newcomer should expect to coordinate on those parts. Done means working badges and listings in at least four directories, plus a merged awesome-list PR.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

effort: small impact: medium marketing

What / who: Add "Install in VS Code" / "Install in VS Code Insiders" badges (vscode:mcp/install?... deeplinks, VS Code MCP docs) and a Cursor install deeplink (Cursor MCP docs) to the README and connect page. List the server on Glama, Smithery, PulseMCP, mcpservers.org, and via PR to awesome-mcp-servers. For developers browsing for MCP tools.

Why: Comparable servers (DevStudio, third-eye-mcp, mcp-screenshot) are found through exactly these directories (Glama search, mcpservers.org). None of them match this repo's depth, but this repo isn't listed where people look. The official Registry (#90) is done; these are the next channels and cost an afternoon.

Approach: Badges generated from the same config JSON used in the README. Submit each listing; add glama.json if needed for ownership claim. Track listings in a short checklist in the issue.
Done: Badges live (tested on Windows VS Code + Cursor), listed in 4+ directories, and an awesome-list PR is merged.

Linguagem predominante
TypeScript
Estrelas
1
Forks
4
Merge médio
14h 8min
PRs com merge (30d)
48

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de TMHSDigital/screencast-mcp

Todas as issues de TMHSDigital/screencast-mcp

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.