Mesh MCP
Search your Mesh contacts, interactions and meetings, and add contacts, notes and groups from chat. Formerly Clay (clay.earth), not Clay.com.Read full description
meshLABSCO SUMMARY
Scoping by URL is the crudest form of least privilege and the hardest to get wrong.
There is no scope to misconfigure and no token that quietly covers more than intended: the connection reaches the ecosystem named in its address, full stop. The cost is that you cannot see the tools before you have an ecosystem, because the endpoint only exists once you do. That trade is a reasonable one for multi-tenant products.
What it is
HiveSight's endpoint, addressed per ecosystem: the URL carries the ecosystem id, so each connection is scoped to one by construction.
What you get
Your HiveSight network, queried in plain English: warm-path lookup, account research, intro suggestions, contact lookup, ICP fit checks and more, the same tools the in-app HiveSight agent uses. HiveSight picks the tool from your question, so there are no tool names to learn.
Requirements
OAuth 2.1 authorization code with PKCE and dynamic client registration.
Setup effort
Get your endpoint, then paste it — add your endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Working within one ecosystem
The id in the URL means the connection cannot reach another.
02
Connecting without provisioning credentials
Dynamic client registration with PKCE, so nothing is pasted by hand.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.1, authorization-code + PKCE (S256), dynamic client registration supported
INSTALLATION
Connect your client
Add your endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://dashboard.hivesight.so/api/mcp/<YOUR_ECOSYSTEM_ID>Requirements
- OAuth 2.1, authorization-code + PKCE (S256), dynamic client registration supported
