{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/a60238d571624aada23cc29838f3fdfc\" frameborder=\"0\" width=\"3340\" height=\"2505\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":2505,"width":3340,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":2505,"thumbnail_width":3340,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/a60238d571624aada23cc29838f3fdfc-9566d2d17d04cbd0.gif","duration":255.075,"title":"C101 Bonus - MCP","description":"This Loom explains what MCP means and how it enables limited, just-in-time access to Clay logic without giving full workflow editing rights. The speaker contrasts MCP with API or CLI access, noting that with API access users can edit workflows, change audiences, and look up data, which may be too broad for restricted access. They demonstrate an example of using Clay enrichment and MCP in Claude to find a mobile phone number from a LinkedIn profile and show a contact card with additional data requests. They also outline common use cases such as giving reps access to specific derived data points and finding people in companies, for example adjacent contacts at Figma in the data science division and potentially based in New York."}