CRM contacts, companies, deals, and engagements, via HubSpot's official MCP server.
Connect it
$ lanes link connect hubspot --profile personal --workspace localHubSpot does not offer dynamic registration, so this needs an OAuth application of your own: you register it once in their console, and Lanes Link uses those values from then on. Run lanes link setup plan hubspot for the exact steps, the values it wants, and the command that finishes the job.
What your agent can do
The tool list comes from HubSpot's own MCP server and is discovered when you connect, so the capabilities are theirs rather than ours.
To see exactly what your agents are handed right now:
$ lanes link tools --profile personal --workspace localWhat is recorded
Every call is recorded, allowed or refused. Because the capabilities are HubSpot's rather than ours, redaction has no authored list to key on, and the default withholds every argument value: you get the call, not what was in it.
That is the right default when we did not write the capability and cannot know what is sensitive. It does mean this connection gives you a thinner record than a provider with a vendored specification does.
What an entry holds and how to read one is on the audit log.
Narrowing what it may do
Connecting grants the read bundle. Tightening it happens on your machine and takes effect at once:
$ lanes link policy deny 'hubspot.*' --connection hubspot.main --profile personal --workspace localA deny always beats an allow, whatever the order in the file. See Scopes and permissions for widening, and for what can and cannot be set per connection.
Untested
The manifest is right in every way the code can check: it validates, its tools generate inside the budget, its scopes are described, and its endpoint answered a probe. Nobody has yet connected it to a real account, which is the part only a real account proves.
If you connect it, say so and this note comes off.
Next: every provider, or Connections for what a connection is and the methods behind one.