MCP Connector for Builders
The evyAI MCP server exposes the same account tools as the evyAI API to any MCP client, plus prospect search and a few more. The user-facing walkthrough is Connect evyAI to Claude. This page is for people wiring it up or writing agents against it.
Endpoint and sign-in
Section titled “Endpoint and sign-in”https://services.api.evyai.com/mcp- Add it as a custom connector in Claude (Customize > add custom connector), named evyAI.
- Authentication is a sign-in flow, not a token paste. The client opens evyAI’s login, the user signs in, and the connector acts as that user from then on. Disconnect from Settings > API and MCP in evyAI or from the client’s connector settings.
- Claude needs a paid plan (Pro, Max, Team or Enterprise) for custom connectors. MCP is an open standard, so other clients that support remote MCP servers with sign-in may work; Claude is what evyAI documents and tests.
- The endpoint answers MCP requests only. A plain browser GET returns 405, which is expected.
43 tools. 37 match the
REST capabilities one for one (same names with an underscore instead of a dot,
so connections.find is connections_find). Six exist only on MCP:
| Tool | What it does | Cost |
|---|---|---|
people_search | Searches the prospect database (people across LinkedIn, not only the user’s connections), the way Find Prospects does in the app. Filters: job titles, seniority, department, company, company domain, headline, first and last name, cities, states, countries, industries. Returns total and a page of up to 25 people with a prospectId, name, headline, title, company, location, summary, skills, work history and education. No email, phone or LinkedIn link. savedConnection is set when the user already has the person. | free |
people_preview | Looks up one person by LinkedIn URL and returns what the database has: name, headline, title, company, location, summary, skills, work history, education. No email or phone. Saves nothing. | free |
people_unlock | Unlocks people from people_search by prospectId, up to 25 at a time, and saves them to the user’s connections with the email, phone and LinkedIn link the database has. Already-saved people come back under alreadySaved and are not charged. | evyCoins per person unlocked, same as Find Prospects |
featureRequests_find | Searches the public feature request board. | free |
featureRequests_vote | Adds the user’s vote to a request. One vote per user. | free |
featureRequests_create | Posts a new request on the board under the user’s name, starting with their vote. Cannot be edited afterward, only deleted by the author on the board. | free |
socialCard_get is on both surfaces; through MCP it returns the card’s public
link, whether sharing is on, what the card shows, how often it was opened and
scanned, how many visitors left their details, and the edit URL.
Behaviors worth knowing
Section titled “Behaviors worth knowing”countries,statesandindustriesmust use the database’s own names. An unknown name is refused with the names to use instead. Retry with one of them.statesis looked up in the United States unlesscountriesis given.- Search is free, unlock costs. A good agent prompt searches, shows the user who it found, and unlocks only the people the user picks.
people_previewis the research step. Pair it withcontent_generatefor a connection request or opener that mentions something real, thenconnections_createwith the preview details to save the person.linkedin_publishis irreversible. Agents should show the draft and get a yes before calling it. Always pass a time zone.- Draft campaigns are reviewed in the app.
campaigns_createDraftmakes a draft; the user opens evyAI to launch it. - Memory is shared with the in-app Agent.
memory_addchanges how evyAI writes for that user everywhere. - Everything the API gotchas list also applies here: list limits, no pagination, no delete for most records, one-hour image URLs.
MCP or REST?
Section titled “MCP or REST?”| MCP connector | REST API | |
|---|---|---|
| For | people talking to Claude; agents inside an MCP client | scripts, automations, servers, agents you host |
| Auth | sign in with the evyAI account | personal access token with chosen permissions |
| Tools | 43, including prospect search, preview, unlock and feature requests | 37 capabilities |
| Setup | paste one URL, sign in | create a token, send a Bearer header |
| Rate limit | per user | 300 calls per minute per user |
Both act as one user, inside that user’s plan.
Prompt patterns that work
Section titled “Prompt patterns that work”- Chain in one message. “Search evyAI for VPs of Sales at SaaS companies in New Jersey, show me the top 10, and when I pick some, unlock them and add them to my list called Q4 Outreach.”
- Research then write. “Preview this LinkedIn profile in evyAI and write a connection request that mentions something real about them.”
- Read before you write. “Read my evyAI profile and my personas first, then write the post.”
- Gate the irreversible. “Draft it and wait for my yes before scheduling.”