convez.ai
MCP ServerIntegração & APIsAvançado
Spera-Law-Group-LLC

Accelo MCP Server

Spera-Law-Group-LLC/accelo-mcp

Integração Accelo via MCP com OAuth por usuário e ferramentas de cotação

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP que integra o Accelo com clientes como LibreChat agents, expondo ferramentas de gerenciamento de cotações. Autentica por usuário via OAuth do Accelo, garantindo que cada ação respeite as permissões individuais. Implementa um proxy OAuth completo com armazenamento seguro de tokens.

Instalação

$npx convez-ai Spera-Law-Group-LLC/accelo-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
1
Forks
0
Acompanhando
0
Saúde
37%
Último commit
há 6 dias
Versão
—
Issues abertas
28
Contribuidores
1

Casos de uso

  • Criar e gerenciar cotações no Accelo através de agentes IA
  • Listar e atualizar deals e cotações com permissões por usuário
  • Integrar fluxos de vendas/propostas em automações LibreChat

Veredito

Solução sólida de integração MCP para Accelo com arquitetura OAuth robusta e modelagem explícita de campos de cotação. Recomendado para equipes que precisam expor funcionalidades Accelo em agentes IA mantendo segurança e permissões por usuário.

README

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

accelo-mcp

A Model Context Protocol (MCP) server for Accelo. It exposes Accelo quote tools to MCP clients (such as LibreChat agents) and authenticates per user via Accelo OAuth, so every action respects that user's own Accelo permissions.

Status: early. Tools: list_quotes, get_quote, get_deal, create_quote, update_quote.

How auth works

This server is an OAuth proxy:

  • To the MCP client it acts as an OAuth Authorization Server (with discovery + dynamic client registration + PKCE).
  • To Accelo it acts as an OAuth client (authorization-code grant).

The MCP client never sees the Accelo token. When a user authorizes, they are bounced to Accelo's consent screen; the resulting Accelo access/refresh tokens are stored locally (SQLite) keyed to an opaque subject, and the MCP client is handed one of our opaque tokens that maps back to it. Accelo tokens are refreshed automatically.

Quote fields

create_quote and update_quote model every client-editable Accelo quote field explicitly, each mapping 1:1 to an Accelo quote key. Pick the field that matches the user's intent — do not route client-facing body text into notes.

FieldClient-facing?Notes
title—Quote title. Required on create.
affiliation_id—Company/contact affiliation the quote is for.
manager_id—Accelo staff member who owns/manages the quote.
date_expiry—Expiry date as a Unix timestamp (seconds).
notesNo (INTERNAL)Internal notes only. Never put introduction/conclusion/terms text here.
introductionYesIntroduction section shown at the top of the quote.
conclusionYesConclusion section shown at the bottom of the quote.
terms_and_conditionsYesTerms and conditions section.
client_portal_accessYesClient portal access setting.

History: earlier versions only surfaced title and notes as named params; all other keys were reachable only through an unconstrained freeform fields map. A request to set the conclusion therefore got silently written to notes (Accelo accepts it, so no error was raised). These fields are now modeled explicitly and the freeform passthrough was removed. See src/mcp.js (editableQuoteFields).

Prerequisites

  1. An Accelo deployment (e.g. https://YOURDEPLOY.api.accelo.com).
  2. A registered Accelo Web Application (Accelo: Configurations -> API -> Register Application). Set its redirect URI to: https://<your-public-host>/oauth/callback
  3. Node 20+ or Docker.

Configuration

Copy .env.example to .env and fill in:

VarDescription
ACCELO_CLIENT_ID / ACCELO_CLIENT_SECRETFrom your Accelo Web App
ACCELO_BASE_URLhttps://YOURDEPLOY.api.accelo.com/api/v0
ACCELO_OAUTH_URLhttps://YOURDEPLOY.api.accelo.com/oauth2/v0
PUBLIC_BASE_URLPublic HTTPS URL of this server
OAUTH_REDIRECT_URI<PUBLIC_BASE_URL>/oauth/callback (must match Accelo)
OAUTH_SCOPEAccelo scopes, e.g. read(all) write(all)
TOKEN_DB_PATHSQLite path (default /app/data/tokens.db)
PORTListen port (default 8787)

Never commit .env (it is gitignored).

Run

Docker (recommended)

docker compose up -d --build
curl -s http://127.0.0.1:8787/healthz

The compose file publishes only on loopback (127.0.0.1:8787). Put a TLS reverse proxy (nginx, Caddy, etc.) in front of it for PUBLIC_BASE_URL.

Node

npm install
npm start

Endpoints

PathPurpose
POST /mcpMCP streamable-HTTP endpoint (Bearer auth)
GET /.well-known/oauth-authorization-serverAS metadata
GET /.well-known/oauth-protected-resourceResource metadata
POST /registerDynamic client registration
GET /authorizeStart auth (redirects to Accelo)
GET /oauth/callbackAccelo redirect target
POST /tokenToken + refresh
GET /healthzHealth check

Using with LibreChat

Add an MCP server pointing at https://<your-public-host>/mcp with OAuth enabled. LibreChat will discover the OAuth endpoints, register a client, and prompt each user to authorize Accelo on first use.

License

MIT

Ver o original no GitHub

Bom para

Relacionados