MCP server overview

The app labels connection strength Relationship. API and MCP responses retain their existing warmness, warmnessBreakdown, and related field names; the terminology change does not change their values or contracts.

The Homie MCP server lets assistants like Cursor, Claude Desktop, Claude Code, and Codex search your organization's network on your behalf. They can find warm intro paths, people, and companies without copy-pasting context.

Endpoint

https://app.usehomie.com/mcp

Authentication

The MCP server uses OAuth 2.1 with PKCE. When you connect a client for the first time, it walks through:

1. Client identification — either a Client ID Metadata Document URL (recommended) or dynamic registration at /oauth/register (deprecated, still supported).
2. Redirect to /oauth/authorize for explicit user consent.
3. Code exchange at /oauth/token for an access token.

MCP clients can stay connected by refreshing tokens until you revoke the connection from Settings > Integrations > Developer > MCP server or your Homie user is removed from the organization.

MCP access requires the Platform plan or an active trial. Each credential can make 120 MCP requests per 60 seconds; a 429 response includes Retry-After. Request bodies are limited to 1 MB.

Tools

The server exposes thirteen read-only tools. A token with the mcp:write scope also gets four write tools, for seventeen total.

• get_icp: read your organization's Ideal Customer Profile. Call this first when prospecting.
• search_warm_paths: find warm intro paths to a target person OR to anyone at a company, from the whole org or from a narrower set of networks.
• list_person_network: list who a given person knows, warmest first. Answers "warm paths from X's network".
• list_first_degree_connections: list your own first-degree LinkedIn connections (user-scoped tokens only).
• list_second_degree_connections: list people your contacts know, with the connector who can introduce you.
• add_prioritized_connection: writes. Marks one of your first-degree connections as a key relationship (user-scoped tokens only).
• remove_prioritized_connection: writes. Takes that mark away again (user-scoped tokens only).
• get_person: fetch one person's profile and your org's warmness to them.
• list_ghost_opportunities: list agent-discovered prospects with ICP fit, buying intent, and a warm path.
• search_network: natural-language search across the organization's network.
• search_people: substring search across people in the network (1st + 2nd degree).
• search_companies: search companies by name, industry, or HQ.
• get_company: fetch one company from the directory by id.
• list_target_lists: list your own target lists and their company counts (user-scoped tokens only).
• get_target_list: inspect and paginate through the companies on one of your target lists.
• create_target_list: writes. Creates a new, empty target list at your request.
• modify_target_list: writes. Rename a target list or add/remove a company at your request.

Alongside the tools, the server exposes resources for fetch-by-URI (homie://icp, homie://person/{id}, homie://company/{id}, homie://ghost-opportunity/{id}) and a warm-intro-brief prompt that assembles the best path to a prospect plus how to ask for the introduction.

The connector is intentionally focused on Homie's network, prospecting, and warm-introduction capabilities. It instructs the connected assistant to briefly decline unrelated general-knowledge requests that no Homie tool, resource, or prompt can materially serve.

Two behaviours worth knowing

Warmness is not fit. Warmness ranks how reachable someone is, never whether they are worth reaching. An unqualified warm-path list surfaces colleagues and friends first. Call get_icp, then filter the results against it.

Warm paths search the whole organization by default. Use scope: "me" for your own network, fromUserIds for named colleagues, and connectionTypes to pick how the target is reached — ["second_degree"] is "through my first-degree connections". See Scoping the search.

Already-requested people are hidden by default. On candidate lists (company-mode search_warm_paths, list_person_network) anyone your organization has already asked for an intro to is dropped, and the count appears as excludedIntroRequested. Pass includeIntroRequested: true to see them. Lookup tools (person-mode search_warm_paths, search_people, get_person) never hide anyone, but do annotate results with introRequested, introStatus, and introRequestedBy.

Which build am I on?

The server reports its version in the initialize handshake as homie-mcp. Versions before 1.2.0 did not report changes reliably, so if your client shows 1.0.0, check tools/list instead: get_icp and list_person_network are present from 1.2.0, target-list tools from 1.3.0, and get_company, create_target_list, and remove_prioritized_connection from 1.5.0.

See Tools reference for the full input schemas, resources, and prompts.

Pick your client

• Cursor: one-click deeplink install.
• Claude Desktop: Custom Connector flow.
• Claude Code: claude mcp add command.
• Other MCP clients: see the OAuth flow page for raw config.