--- title: "Claude / Cursor agents: Call a contact lookup MCP endpoint – Invenitor" description: "Wire Claude or Cursor agents to a contact lookup MCP endpoint – URL in, email/phone when found. REST twin + /mcp.md." url: https://invenitor.com/blog/claude-cursor-agents-calling-a-contact-lookup-mcp-endpoint agents: https://invenitor.com/llms.txt mcp: https://api.invenitor.com/mcp --- [Blog](https://invenitor.com/blog) Oct 5, 2026 · 9 min read · MCP # Claude / Cursor agents: Calling a contact lookup MCP endpoint Claude and Cursor agents calling a contact lookup MCP endpoint: tool calls instead of scrapers – same credits as REST. On this page 1. [Claude / Cursor setup shape (high level)](#claude-cursor-setup-shape-high-level) 2. [Why MCP beats scraping for outreach agents](#why-mcp-beats-scraping-for-outreach-agents) 3. [Credits when agents call lookup](#credits-when-agents-call-lookup) 4. [Prompt patterns that stay honest](#prompt-patterns-that-stay-honest) 5. [Common failure modes](#common-failure-modes) 6. [What should you do next?](#what-should-you-do-next) 7. [REST twin and product packaging](#rest-twin-and-product-packaging) 8. [Tool-call checklist before production agents](#tool-call-checklist-before-production-agents) 9. [Why PMs should care about MCP now](#why-pms-should-care-about-mcp-now) Claude, Cursor, and similar agents should call a **contact lookup tool** – not scrape LinkedIn HTML. Invenitor exposes that tool over MCP (and the same find over REST): profile URL in, email/phone/links out **when we have them**. A people search and lookup API, not a sales cloud. ## Claude / Cursor setup shape (high level) 1. Point the agent or IDE at Invenitor’s MCP server config (see ). 2. Authenticate with the same API key pattern you use for REST (). 3. Prompt: “Look up contacts for these profile URLs. 4. Persist outcomes in your sheet or CRM with provenance. ## Why MCP beats scraping for outreach agents Scrapers break, violate product terms, and tempt agents to hallucinate when HTML is thin. Category: [What a Contact Lookup API Actually Does](https://invenitor.com/blog/what-is-a-contact-lookup-api). Hub: [LinkedIn or GitHub Profile URL → Contact Lookup API](https://invenitor.com/blog/linkedin-github-contact-lookup-api). GitHub rail: [GitHub Profile URL Contact Lookup](https://invenitor.com/blog/github-profile-url-contact-lookup-when-developer-profiles-are-the). Definition: [What Is a LinkedIn Profile URL Lookup?](https://invenitor.com/blog/what-is-a-linkedin-profile-url-lookup). ## Credits when agents call lookup Agents share the workspace credit pool. 1 credit only when we return an email, a phone, or both. Timeouts and errors do not spend. Commercial: . PAYG: [Pay-As-You-Go Contact APIs](https://invenitor.com/blog/pay-as-you-go-contact-apis-for-teams-that-hate). ## Prompt patterns that stay honest - “Fill email/phone columns only from tool results.” - “Prefer person profile URLs; reject company pages.” - “Do not construct emails from name + company domain.” ## Common failure modes - Keys pasted into chat logs. - Looking up search URLs or company pages. - Bundling outreach sequencing into the lookup tool (wrong layer). ## What should you do next? Keep REST in as the twin. Buy packs on when free credits are done. Agents welcome – scrapers are a detour. ## REST twin and product packaging Ship MCP for agents and REST for product backends with one found-only billing rule. Product teams: optional lookup module, not a CRM. See Global PAYG buyers: [US Price Arbitrage](https://invenitor.com/blog/us-price-arbitrage-why-some-teams-buy-inr-credit-apis). ## Tool-call checklist before production agents Confirm person URLs only. Confirm secrets not in chat. Confirm credit balance vs 30-day expiry on . Confirm REST twin still works for non-agent paths (). Free-plan contrast: [The Hidden Cost of "Free Plan" Enrichment Tools](https://invenitor.com/blog/the-hidden-cost-of-free-plan-enrichment-tools-for-small). GitHub: [GitHub Profile URL Contact Lookup](https://invenitor.com/blog/github-profile-url-contact-lookup-when-developer-profiles-are-the). Category: [What a Contact Lookup API Actually Does](https://invenitor.com/blog/what-is-a-contact-lookup-api). ## Why PMs should care about MCP now Agents are already filling sheets in boutique desks. MCP is how you keep reaching people without turning the agent into a liar. Pair with . PAYG: [Pay-As-You-Go Contact APIs](https://invenitor.com/blog/pay-as-you-go-contact-apis-for-teams-that-hate). ## Questions Can Claude or Cursor call Invenitor for contact lookup?+ Yes – wire the MCP endpoint per /mcp.md. Same find contract as REST. Should agents scrape LinkedIn instead?+ No. Use the lookup tool. Do agent calls use the same credits as REST?+ Yes. 1 credit only when we return an email, a phone, or both. Timeouts and errors do not spend. Where is the MCP spec?+ /mcp.md – pair with /docs for REST. Can agents look up GitHub profiles?+ Yes. Person GitHub profile URLs work on the same find path. How do I authenticate?+ Use your API key as documented in /docs and /mcp.md – store secrets safely. ## Find the person you need Describe who you need in one sentence. Your first search is free, and you pay only for contacts we find [Find people free](https://invenitor.com/login?from=https%3A%2F%2Fpeople.invenitor.com%2Fsearch&x=w7&q=c5&z=g1)[See pricing](https://invenitor.com/pricing?x=w7&q=c5&z=g2) ## Keep reading - [Oct 13, 2026 · MCPAgent-Readable docs: Why mcp.md matters for contact APIsAgent-readable docs: why MCP.md matters for contact APIs – typed tools for Claude/Cursor agents, same found-only billing as REST.](https://invenitor.com/blog/agent-readable-docs-why-mcp-md-matters-for-contact-apis) - [Nov 4, 2026 · PricingEvaluating contact APIs without "best of" roundupsEvaluating contact APIs without "best of" roundups – a buyer rubric for honesty, billing, docs, and workflow fit. Rubric beats rankings.](https://invenitor.com/blog/evaluating-contact-apis-without-best-of-roundups) - [Nov 4, 2026 · ProductNever make one up: Editorial standards for enrichment content teamsNever make one up: editorial standards for enrichment content teams – ban invented demo contacts, hit-rate claims, and marketing that contradicts the API.](https://invenitor.com/blog/never-make-one-up-editorial-standards-for-enrichment-content-teams)