Suitecrm MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 79 installs a week from npm. Last commit 8 Jul 2026.
Open-source MCP gateway for SuiteCRM - 24 CRM tools, OAuth2/OIDC auth, multi-entity, observability.
We read the source, 6 d ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
run(["runuser", "-u", username, "--", npm_path, "install", "--silent"], cwd=bridge_dir)
r = subprocess.run(cmd, capture_output=capture, text=True, cwd=cwd)
- /var/run/docker.sock:/var/run/docker.sock:ro
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Today is the operative word: we check Suitecrm MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add suitecrm-mcp -e 'SUITECRM_ENDPOINT=<SUITECRM_ENDPOINT>' -e 'SUITECRM_PREFIX=<SUITECRM_PREFIX>' -e 'PORT=<PORT>' -e 'AUTH0_DOMAIN=<AUTH0_DOMAIN>' -e 'AUTH0_AUDIENCE=<AUTH0_AUDIENCE>' -- npx -y suitecrm-mcp-gateway
{
"mcpServers": {
"suitecrm-mcp": {
"command": "npx",
"args": [
"-y",
"suitecrm-mcp-gateway"
],
"env": {
"AUTH0_AUDIENCE": "<AUTH0_AUDIENCE>",
"AUTH0_DOMAIN": "<AUTH0_DOMAIN>",
"PORT": "<PORT>",
"SUITECRM_ENDPOINT": "<SUITECRM_ENDPOINT>",
"SUITECRM_PREFIX": "<SUITECRM_PREFIX>"
}
}
}
}
[mcp_servers.suitecrm-mcp]
command = "npx"
args = ["-y", "suitecrm-mcp-gateway"]
env = { SUITECRM_ENDPOINT = "<SUITECRM_ENDPOINT>", SUITECRM_PREFIX = "<SUITECRM_PREFIX>", PORT = "<PORT>", AUTH0_DOMAIN = "<AUTH0_DOMAIN>", AUTH0_AUDIENCE = "<AUTH0_AUDIENCE>" }
{
"mcpServers": {
"suitecrm-mcp": {
"command": "npx",
"args": [
"-y",
"suitecrm-mcp-gateway"
],
"env": {
"AUTH0_AUDIENCE": "<AUTH0_AUDIENCE>",
"AUTH0_DOMAIN": "<AUTH0_DOMAIN>",
"PORT": "<PORT>",
"SUITECRM_ENDPOINT": "<SUITECRM_ENDPOINT>",
"SUITECRM_PREFIX": "<SUITECRM_PREFIX>"
}
}
}
}
{
"servers": {
"suitecrm-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"suitecrm-mcp-gateway"
],
"env": {
"AUTH0_AUDIENCE": "<AUTH0_AUDIENCE>",
"AUTH0_DOMAIN": "<AUTH0_DOMAIN>",
"PORT": "<PORT>",
"SUITECRM_ENDPOINT": "<SUITECRM_ENDPOINT>",
"SUITECRM_PREFIX": "<SUITECRM_PREFIX>"
}
}
}
}
Put your own values in place of
<SUITECRM_ENDPOINT> (SuiteCRM v4_1 REST endpoint URL, e.g. https://crm.example.com/service/v4_1/rest.php), <SUITECRM_PREFIX> (Tool name prefix, e.g. suitecrm), <PORT> (Port the gateway listens on), <AUTH0_DOMAIN> (OIDC provider domain, e.g. your-tenant.auth0.com), <AUTH0_AUDIENCE> (OAuth2 API audience identifier).
The author’s registry entry marks them as required.
OAuth 2.1/OIDC resource-server reference for secure MCP authorization
AI governance MCP server for policy enforcement, cost control, and observability.
eBPF-based GPU causal observability with 7 MCP tools for AI-assisted GPU debugging
Solana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments.
TypeScript template for building MCP servers with declarative tooling, observability, and auth.
The complete open-source SEO data stack for AI agents: 7 sources, 86 tools, one MCP server
Multi-tenant hosted MCP server for Oura Ring — 21 read-only tools, OAuth per user.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Answers built from our own checks of this server.