convez.ai
MCP Server
milojarow

espocrm-skills

milojarow/espocrm-skills

Ver no GitHub
InicialPluginScore · de 0 a 100

Expert Claude Code skills for operating self-hosted EspoCRM 9.x — REST API & MCP patterns, auth, custom entities

Instalação

$npx convez-ai milojarow/espocrm-skills

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
1
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 1 mês
Versão
—
Issues abertas
0
Contribuidores
1

README

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

espocrm-skills

Expert Claude Code skills for operating self-hosted EspoCRM

What is this?

This repository contains a Claude Code skill that teaches AI assistants how to operate a self-hosted EspoCRM 9.x instance via its REST API or an MCP server — without re-hitting the discovery walls that have already been mapped.

Why this skill exists

Driving EspoCRM through its API has non-obvious traps:

  • Two separate auth paths (api-user X-Api-Key vs admin Basic+Token) with different permitted operations
  • Schema work (custom entities, fields, links, layouts) lives on endpoints that don't follow the obvious paths
  • Records created by the wrong user pollute streams, audit logs, and reporting
  • Custom entities need 7+ layouts populated or the UI silently breaks
  • A long tail of validationFailure / 403 / 404 / 405 walls

This skill encodes the verified endpoints, the two auth flows, sound customer-modeling defaults, and the walls already hit — so sessions go straight to what works.

The skill

SkillDescription
espocrmEspoCRM 9.x operating manual — auth, native + custom entities, verified endpoints, customer modeling, and common errors

Installation

Add this marketplace in Claude Code:

/plugin → Marketplaces → Add Marketplace → milojarow/espocrm-skills

Then install:

/plugin → Discover → espocrm-skills → Install

Requirements

  • A self-hosted EspoCRM 9.x instance
  • An api-type user with an API key (daily CRUD) and an admin user (schema work)
  • Optionally, an EspoCRM MCP server for tool-based access (mcp__espocrm__* tools) — copy .mcp.json.example and fill in your instance URL + api-user API key. Prefer a wrapper script that injects the key from a secrets file over hardcoding it.

License

MIT

Ver o original no GitHub

Bom para

Relacionados