ConnectWise API Gateway MCP Server for Claude
CWM API Gateway MCP MCP server exists for a simple reason — assistants are far more useful when they can act on CWM API Gateway MCP directly instead of describing what you should do. ConnectWise API Gateway MCP Server for Claude.
This Model Context Protocol (MCP) server provides a comprehensive interface for interacting with the ConnectWise Manage API. It simplifies API discovery, execution, and management for both developers and AI assistants.
Once CWM API Gateway MCP is connected, these are the calls the assistant has available:
CONNECTWISE_API_URL — The base URL for all API requests to your ConnectWise instanceCONNECTWISE_COMPANY_ID — Included in the 'clientId' header of each request to identify your companyCONNECTWISE_AUTH_PREFIX — Required prefix added before your public key in the authentication username. ConnectWise API requires this prefix to identify the type of integrationsearch_api_endpoints — Search for API endpoints by query stringnatural_language_api_search — Find endpoints using natural language descriptionslist_api_categories — List all available API categoriesget_category_endpoints — List all endpoints in a specific categoryget_api_endpoint_details — Get detailed information about a specific endpointexecute_api_call — Execute an API call with path, method, parameters, and datasend_raw_api_request — Send a raw API request in the format "METHOD /path [JSON body]"save_to_fast_memory — Manually save an API query to Fast Memorylist_fast_memory — List all queries saved in Fast MemoryYou will need 8 environment variables: CONNECTWISE_API_URL, CONNECTWISE_COMPANY_ID, CONNECTWISE_PUBLIC_KEY, CONNECTWISE_PRIVATE_KEY, CONNECTWISE_AUTH_PREFIX, COMPANY_ID, PUBLIC_KEY, PRIVATE_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
manage.json) - included in the repositoryjasondsmith72/CWM-API-Gateway-MCP on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. CWM API Gateway MCP's toolset — CONNECTWISE_API_URL, CONNECTWISE_COMPANY_ID, CONNECTWISE_AUTH_PREFIX and 11 more — is a fair guide to whether it matches your workflow. It is maintained by jasondsmith72; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| CONNECTWISE_API_URL | The base URL for all API requests to your ConnectWise instance |
| CONNECTWISE_COMPANY_ID | Included in the 'clientId' header of each request to identify your company |
| CONNECTWISE_AUTH_PREFIX | Required prefix added before your public key in the authentication username. ConnectWise API requires this prefix to identify the type of integration (e.g., "api+", "integration+", etc.) |
| search_api_endpoints | Search for API endpoints by query string |
| natural_language_api_search | Find endpoints using natural language descriptions |
| list_api_categories | List all available API categories |
| get_category_endpoints | List all endpoints in a specific category |
| get_api_endpoint_details | Get detailed information about a specific endpoint |
| execute_api_call | Execute an API call with path, method, parameters, and data |
| send_raw_api_request | Send a raw API request in the format "METHOD /path [JSON body]" |
| save_to_fast_memory | Manually save an API query to Fast Memory |
| list_fast_memory | List all queries saved in Fast Memory |
| delete_from_fast_memory | Delete a specific query from Fast Memory |
| clear_fast_memory | Clear all queries from Fast Memory |
{
"mcpServers": {
"cwm-api-gateway": {
"command": "npx",
"args": ["-y", "jasondsmith72/CWM-API-Gateway-MCP"],
"env": {
"CONNECTWISE_API_URL": "your-value",
"CONNECTWISE_COMPANY_ID": "your-value",
"CONNECTWISE_PUBLIC_KEY": "your-value",
"CONNECTWISE_PRIVATE_KEY": "your-value",
"CONNECTWISE_AUTH_PREFIX": "your-value",
"COMPANY_ID": "your-value",
"PUBLIC_KEY": "your-value",
"PRIVATE_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
manage.json) - included in the repository| Variable | Description | Required |
|---|---|---|
| CONNECTWISE_API_URL | Endpoint or connection string the server talks to. | Yes |
| CONNECTWISE_COMPANY_ID | Configuration value read at startup. | Optional |
| CONNECTWISE_PUBLIC_KEY | Credential the server authenticates with. | Yes |
| CONNECTWISE_PRIVATE_KEY | Credential the server authenticates with. | Yes |
| CONNECTWISE_AUTH_PREFIX | Configuration value read at startup. | Optional |
| COMPANY_ID | Configuration value read at startup. | Optional |
| PUBLIC_KEY | Credential the server authenticates with. | Yes |
| PRIVATE_KEY | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.