Gripp MCP
This MCP server lets you interact with the Gripp API (and optionally GoHighLevel) through Claude or other MCP clients.
List Gripp entities and methods (
gripp_list_entities)Inspect entity fields, enums, references, and examples (
gripp_describe_entity)Retrieve entities with filters, paging, and ordering (
gripp_get,gripp_getone)Create, update, and delete entities (requires explicit
confirm: true)Call any documented Gripp method directly (
gripp_call) and batch multiple calls in a transaction (gripp_batch)Non-read operations are blocked unless confirmed, ensuring safe writes
Optionally access GoHighLevel contacts, opportunities, and generic API calls via provided GHL tools (requires separate OAuth setup)
Can be run locally via stdio or deployed as a remote Streamable HTTP MCP on Vercel
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Gripp MCP list companies with name containing Acme"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Gripp MCP
Model Context Protocol server for the Gripp API 3.0 endpoint at https://api.gripp.com/public/api3.php.
The Gripp API is JSON-RPC-like: requests are POSTed as a batch array, and the API token is sent as Authorization: Bearer <token>.
Setup
npm install
npm run fetch:metadata
npm run buildSet your Gripp API token before starting the server:
export GRIPP_API_TOKEN="your-token"
npm startOptional environment variables:
GRIPP_API_URL=https://api.gripp.com/public/api3.php
GRIPP_REQUEST_TIMEOUT_MS=30000GRIPP_API_URL is intentionally restricted to the https://api.gripp.com/ host.
Related MCP server: SuperOps MCP Server
MCP Client Config
Example stdio config:
{
"mcpServers": {
"gripp": {
"command": "node",
"args": ["/absolute/path/to/MCP Gripp/dist/src/cli.js"],
"env": {
"GRIPP_API_TOKEN": "your-token"
}
}
}
}After publishing or linking the package, you can also run the gripp-mcp binary.
Vercel Remote MCP
This repo also exposes a Streamable HTTP MCP endpoint for Vercel through a Next.js route:
https://your-vercel-domain.vercel.app/api/mcpFor Claude custom connectors, use the /api/mcp URL. The root URL only returns a health response.
Set this environment variable in Vercel before using Gripp tools:
GRIPP_API_TOKEN=your-token
MCP_ACCESS_KEY=long-random-secretUse the access key in Claude's custom connector URL:
https://your-vercel-domain.vercel.app/api/mcp?access_key=long-random-secretThe /api/mcp endpoint fails closed in production if MCP_ACCESS_KEY is not set. If the URL leaks, rotate MCP_ACCESS_KEY in Vercel and redeploy.
The remote endpoint can also read a Gripp token from Authorization: Bearer <token> or x-gripp-api-token, but Claude's custom connector UI does not currently provide a simple custom-header field. For Claude, the practical setup is to store GRIPP_API_TOKEN in the Vercel project environment.
GoHighLevel Remote MCP
The same Vercel project can also host a GoHighLevel MCP endpoint with OAuth token storage:
https://your-vercel-domain.vercel.app/api/connect/mcpSet these environment variables in Vercel:
GHL_CLIENT_ID=your-highlevel-client-id
GHL_CLIENT_SECRET=your-highlevel-client-secret
GHL_APP_ID=your-highlevel-app-or-version-id
GHL_INSTALL_URL=your-highlevel-installation-url
GHL_REDIRECT_URI=https://your-vercel-domain.vercel.app/api/connect/callback
GHL_OAUTH_USER_TYPE=Company
GHL_MCP_ACCESS_KEY=long-random-secret
GHL_TOKEN_ENCRYPTION_KEY=$(openssl rand -hex 32)
KV_REST_API_URL=your-upstash-or-vercel-kv-rest-url
KV_REST_API_TOKEN=your-upstash-or-vercel-kv-rest-tokenUPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN also work instead of the KV_* names.
In the HighLevel Marketplace app settings, add this redirect URL:
https://your-vercel-domain.vercel.app/api/connect/callbackThen open the OAuth start URL in your browser:
https://your-vercel-domain.vercel.app/api/connect/startAfter HighLevel redirects back, the callback page stores that subaccount installation. Use one shared URL in Claude's custom connector screen:
https://your-vercel-domain.vercel.app/api/connect/mcp?access_key=long-random-secretInstall the app once per subaccount by reopening /api/connect/start and choosing the next location. The MCP keeps an index of all connected installations. In Claude, call ghl_list_installations first, then pass the chosen installId to the contact, opportunity, or generic API tools.
If your Marketplace app can only be installed by an agency admin, set GHL_OAUTH_USER_TYPE=Company. After installing once at agency level, use ghl_list_installed_locations to see where the app is actually installed, then ghl_connect_location to create a stored Location installation for the subaccount you want to query. ghl_list_locations only lists visible subaccounts and does not prove the app is installed on them.
The GoHighLevel MCP fails closed in production if GHL_MCP_ACCESS_KEY, encrypted token storage, or OAuth credentials are missing.
GoHighLevel Tools
ghl_installation_status: show the OAuth installation metadata without exposing tokens.ghl_list_installations: list all connected subaccounts/installations.ghl_list_locations: list/search subaccounts from a connected agency/company install.ghl_list_installed_locations: list locations where this app is installed/authorized.ghl_connect_location: create and store a Location token from an agency/company install.ghl_get_contact: retrieve one contact by contact ID.ghl_search_contacts: search contacts with/contacts/search.ghl_create_contact: create a contact; requiresconfirm: true.ghl_update_contact: update a contact; requiresconfirm: true.ghl_search_opportunities: search opportunities with/opportunities/search.ghl_api_call: call any relative HighLevel API path; non-GET calls requireconfirm: true.
Shared Google Ads MCP for Claude
For a shared Google Ads MCP that multiple people can use in Claude, run the official googleads/google-ads-mcp server as a separate remote service instead of using a local stdio MCP process.
See docs/google-ads-mcp-claude.md for the Cloud Run deployment and Claude custom connector setup.
Tools
gripp_list_entities: list available Gripp entities and method names.gripp_describe_entity: inspect fields, enum values, references, methods, and examples for one entity.gripp_get: call<entity>.getwith filters and options.gripp_getone: call<entity>.getonewith filters.gripp_create: call<entity>.create; requiresconfirm: true.gripp_update: call<entity>.update; requiresconfirm: true.gripp_delete: call<entity>.delete; requiresconfirm: true.gripp_call: call any documented Gripp method by full name.gripp_batch: execute multiple documented Gripp calls in one transaction.
Non-read methods are blocked unless confirm: true is provided. This also applies to gripp_call and each item in gripp_batch.
Examples
Find companies by name:
{
"entity": "company",
"filters": [
{
"field": "company.companyname",
"operator": "like",
"value": "%Acme%"
}
],
"options": {
"paging": {
"firstresult": 0,
"maxresults": 10
},
"orderings": [
{
"field": "company.companyname",
"direction": "asc"
}
]
}
}Call a nonstandard read method:
{
"method": "company.getCompanyByCOC",
"params": ["12345678"]
}Create a tag:
{
"entity": "tag",
"fields": {
"name": "Imported"
},
"confirm": true
}Metadata
The committed metadata snapshot is generated from the public API docs page:
npm run fetch:metadataRefresh it when Gripp updates the API docs.
Available Tools
9 toolsgripp_batchB
Execute multiple Gripp API calls in one Gripp transaction. Non-read calls require confirm=true per item.
Inputs: calls (required).
gripp_callB
Call any Gripp API method by full method name. Non-read methods require confirm=true.
Inputs: method (required), params, confirm.
gripp_createB
Create a Gripp entity. Requires confirm=true because this writes to Gripp.
Inputs: entity (required), fields (required), confirm (required).
gripp_deleteA
Delete a Gripp entity by ID. Requires confirm=true because this permanently changes Gripp data.
Inputs: id (required), entity (required), confirm (required).
gripp_describe_entityA
Describe one Gripp API entity, including fields, references, enum values, methods, and examples.
Inputs: entity (required).
gripp_getB
Retrieve Gripp entities with filters, paging, and ordering. Uses the entity.get API method.
Inputs: entity (required), filters, options.
gripp_getoneA
Retrieve a single Gripp entity. Uses the entity.getone API method and returns the first matching item.
Inputs: entity (required), filters.
gripp_list_entitiesA
List available Gripp API entities, fields counts, and supported method names.
Inputs: no named parameters.
gripp_updateA
Update a Gripp entity by ID. Requires confirm=true because this writes to Gripp.
Inputs: id (required), entity (required), fields (required), confirm (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Most tools have clearly distinct purposes. However, 'gripp_call' is a catch-all that can replicate other tools, and 'gripp_get' vs 'gripp_getone' may cause minor confusion, but descriptions help differentiate.
All tools follow a 'gripp_verb' or 'gripp_verb_entity' pattern. Minor deviations: 'describe_entity' and 'list_entities' are slightly more descriptive than imperative, and 'getone' breaks the verb-noun pattern.
With 9 tools, the set covers essential operations (CRUD, batch, metadata) without being overwhelming. The count is well-scoped for a generic API wrapper.
The tool surface covers most needed operations: listing, describing, CRUD, batch, and raw calls. Missing advanced search or count, but the general call and batch can fill minor gaps.
Maintenance
Related MCP Connectors
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
The official MCP Server for the Mux API
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for the GitHub REST API that enables interaction with repositories, pull requests, issues, branches, commits, reviews, and code search, with configurable write and destructive operations.-
- AlicenseAqualityCmaintenanceMCP server for interacting with the SuperOps.ai PSA/RMM platform, providing tools for managing clients, tickets, assets, and technicians via GraphQL API.21Apache 2.0
- AlicenseBqualityDmaintenanceLocal MCP server for inspecting and managing an allowlisted Discord server via Discord's REST API, with safety modes, idempotent JSON blueprints, and destructive-operation safeguards.271MIT
- AlicenseBqualityDmaintenanceMCP server for interacting with a self-hosted Appsmith instance via its REST API, enabling read/update/create of pages, queries, JS objects, widgets, datasources, and applications with lazy session management and destructive-operation gating.30MIT