convez.ai
MCP ServerIntegração & APIsIntermediário
fredericboyer

Loopio MCP Server

fredericboyer/loopio-mcp

Integração MCP com Loopio Data API v2 para Claude

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP não oficial que expõe a Loopio Data API v2 para clientes Claude. Oferece acesso de leitura por padrão, com escrita e exclusão opcionais. Integra-se nativamente ao Claude Desktop e Claude Code para consultas e gerenciamento de biblioteca e projetos.

Instalação

$npx convez-ai fredericboyer/loopio-mcp

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 2 meses
Versão
v0.4.0
Issues abertas
17
Contribuidores
2

Casos de uso

  • Consultar biblioteca de conteúdo e respostas no Loopio a partir de Claude
  • Pesquisar e recuperar informações de projetos e questões
  • Automatizar criação e atualização de entradas de biblioteca (com enable_writes)
  • Responder propostas de projetos programaticamente através de IA

Veredito

Integração bem arquitetada e segura, com controle granular de permissões (reads/writes/deletes via env vars). Ideal para times que usam Loopio + Claude e precisam automatizar acesso à biblioteca de respostas. Requer credenciais OAuth2 e conhecimento de MCP para configuração.

README

A tradução para o português deste README ainda está na fila.

loopio-mcp

A local MCP server exposing the Loopio Data API (v2) to MCP clients (Claude Desktop, Claude Code). Read-only by default; writes and deletes are opt-in.

Unofficial. This is an independent, community-built project. It is not affiliated with, endorsed by, or supported by Loopio Inc. "Loopio" is a trademark of its respective owner and is used here only to identify the API this server targets. Use of the Loopio API is subject to Loopio's own terms.

Tools

Read (always on): search_library, get_library_entry, get_library_structure, list_projects, get_project, get_project_questions, get_project_status_summary.

Write (require LOOPIO_ENABLE_WRITES=true): create_library_entry, update_library_entry, answer_project_entry.

Delete (require LOOPIO_ENABLE_WRITES=true and LOOPIO_ENABLE_DELETES=true): delete_library_entry.

Setup

In Loopio, sign in as an Admin and go to Admin > Integrations > For Developers > Add an App. Select the scopes you need (library:read, project:read, and optionally library:write, project:write, library:delete). Scopes cannot be changed after creation, so select every scope you might enable. Copy the Client ID and Secret (the secret is shown only once).

MCP client configuration

Add the server to your MCP client (Claude Desktop, Claude Code). Run it directly with npx (no checkout needed), or build from source.

With npx (recommended)

Requires the package to be published to npm.

{
  "mcpServers": {
    "loopio-mcp": {
      "command": "npx",
      "args": ["-y", "loopio-mcp"],
      "env": {
        "LOOPIO_CLIENT_ID": "your-client-id",
        "LOOPIO_CLIENT_SECRET": "your-client-secret",
        "LOOPIO_ENABLE_WRITES": "false"
      }
    }
  }
}

From source

git clone https://github.com/fredericboyer/loopio-mcp
cd loopio-mcp
npm install && npm run build

Then point your client at the built entry file, using an absolute path:

{
  "mcpServers": {
    "loopio-mcp": {
      "command": "node",
      "args": ["/absolute/path/to/loopio-mcp/dist/server.js"],
      "env": {
        "LOOPIO_CLIENT_ID": "your-client-id",
        "LOOPIO_CLIENT_SECRET": "your-client-secret",
        "LOOPIO_ENABLE_WRITES": "false"
      }
    }
  }
}

Environment variables

VariableRequiredDefaultDescription
LOOPIO_CLIENT_IDYes—OAuth2 client id from the Loopio app.
LOOPIO_CLIENT_SECRETYes—OAuth2 client secret (shown only once at app creation).
LOOPIO_ENABLE_WRITESNofalseEnable the write tools (create_library_entry, update_library_entry, answer_project_entry).
LOOPIO_ENABLE_DELETESNofalseEnable the delete tool (delete_library_entry). Ignored unless LOOPIO_ENABLE_WRITES is also true.
LOOPIO_HOSTNoapi.loopio.comAPI host. Use api.int01.loopio.com for Loopio's test environment.
LOOPIO_API_BASE_PATHNo/data/v2API base path.
LOOPIO_SCOPESNoderived from the flags aboveSpace-delimited override of the requested OAuth scopes.
LOOPIO_MAX_RESULTSNo200Maximum items returned per list/search tool (must be a positive integer).

The server requests only the OAuth scopes matching the enabled tiers, so a read-only deployment never holds write or delete scopes.

Testing against the mock server

You can exercise the tools without real credentials by pointing the base URL at Loopio's Stoplight mock:

$env:LOOPIO_CLIENT_ID="mock"; $env:LOOPIO_CLIENT_SECRET="mock"
$env:LOOPIO_API_BASE_PATH="/loopio/loopio-api/84330"; $env:LOOPIO_HOST="stoplight.io"

Note: the mock does not implement OAuth, so this only exercises request/response shapes for endpoints that the mock serves. Use the live API for end-to-end verification.

Live smoke test (read-only)

With real credentials you can verify end-to-end auth and read access without writing anything:

$env:LOOPIO_CLIENT_ID="<real>"; $env:LOOPIO_CLIENT_SECRET="<real>"
npx tsx scripts/live-smoke.ts "security"

This calls get_library_structure and search_library and prints a short summary. It never creates, updates, or deletes data. A non-zero exit with a clear message indicates an auth, scope, or configuration problem.

Development

  • npm test runs the unit tests.
  • npm run dev runs the server from source via tsx.
Ver o original no GitHub

Bom para

Relacionados