Unofficial MCP server for the Accelo CRM platform
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"accelo-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# accelo-mcp An unofficial [Model Context Protocol](https://modelcontextprotocol.io/) server for the [Accelo](https://www.accelo.com) CRM platform. It exposes Accelo data and operations to MCP-compatible AI assistants through the documented Accelo REST API. > This project is not affiliated with or endorsed by Accelo. Users are responsible for their Accelo account, OAuth application, permissions, and data handling. ## Installation ### With `uvx` The recommended installation for MCP hosts is: ```json { "mcpServers": { "accelo": { "command": "uvx", "args": ["accelo-mcp"], "env": { "ACCELO_DEPLOYMENT": "your-deployment", "ACCELO_CLIENT_ID": "your-client-id", "ACCELO_CLIENT_SECRET": "your-client-secret" } } } } ``` To pin a release: ```json "args": ["accelo-mcp==0.1.0"] ``` `uvx` installs the package into an isolated environment and runs the `accelo-mcp` command. ### With `pip` ```bash python3 -m pip install accelo-mcp accelo-mcp ``` ### From source ```bash git clone <repository-url> cd accelo-mcp python3 -m venv .venv source .venv/bin/activate pip install -e ".[dev]" ``` ## Configuration Copy `.env.example` to `.env`, or provide these variables through the MCP host: | Variable | Required | Default | Description | |----------|----------|---------|-------------| | `ACCELO_DEPLOYMENT` | Yes | — | Deployment prefix, such as `example` for `example.accelo.com` | | `ACCELO_CLIENT_ID` | Yes | — | OAuth2 client ID from an Accelo application | | `ACCELO_CLIENT_SECRET` | Depends on auth type | — | OAuth2 client secret; not required for public PKCE applications | | `ACCELO_AUTH_TYPE` | No | `web` | `web`, `service`, `installed`, or `public` | | `ACCELO_SCOPE` | No | `read(all)` | OAuth2 scope; defaults to read-only. Add write access explicitly, e.g. `read(all),write(all)`, only if you need the write tools | | `ACCELO_REDIRECT_URI` | For `web` and `public` | `http://localhost:9876/callback` (`web` only) | L…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.