ContactOut MCP server
ContactOut finds and verifies professional contact details, letting a recruiter or sales team turn a LinkedIn profile into a working email address. Connect through Arc0 to use the actions your identity is allowed to call.
Agent workflows for ContactOut.
Get contact
Use when a LinkedIn profile needs contact details; check free availability first. Not for Sales Navigator/Recruiter URLs. Costs email/optional phone credits. Work-email verification can be slow and may be charged on timeout; don't blindly retry.
Check personal email
Use when deciding whether to spend credits revealing personal email for a LinkedIn profile. Requires a paid account but consumes no credits.
Check work email
Use when checking work email availability and verification before revealing contact details. Requires a paid account but consumes no credits.
9 ContactOut actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
9Look things up, subject to your permissions.
- contactout.get_contactGet contact
Use when a LinkedIn profile needs contact details; check free availability first. Not for Sales Navigator/Recruiter URLs. Costs email/optional phone credits. Work-email verification can be slow and may be charged on timeout; don't blindly retry.
- contactout.check_personal_emailCheck personal email
Use when deciding whether to spend credits revealing personal email for a LinkedIn profile. Requires a paid account but consumes no credits.
- contactout.check_work_emailCheck work email
Use when checking work email availability and verification before revealing contact details. Requires a paid account but consumes no credits.
- contactout.check_phoneCheck phone
Use when checking whether a LinkedIn profile has a phone number before spending a phone credit. Requires a paid account but consumes no credits.
- contactout.verify_emailVerify email
Use when checking email deliverability before outreach. Valid, invalid, and accept-all results consume one verifier credit. Unknown results do not establish deliverability.
- contactout.find_linkedinFind linkedin
Use when an email address is known but its LinkedIn profile is missing. A successful match consumes one email credit.
- contactout.get_usageGet usage
Use when checking monthly email, phone, and search usage or remaining allowance before planning more lookups. Prepaid quota fields are balances; postpaid quota fields are allowances.
- contactout.enrich_companiesEnrich companies
Use when enriching up to 30 company domains with organization details. Returns domain-keyed company records and consumes one search credit per company found.
- contactout.search_peopleSearch people
Use when discovering people by name, role, company, location, or skills. Page through up to 25 matches at a time. Consumes search credits. Not for contact reveal or known-profile lookup; use get_contact after free availability checks.
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Control access to ContactOut.
Connect the intended ContactOut account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How ContactOut connects.
Connect ContactOut using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use ContactOut with your AI client.
Sign in to Arc0 and connect ContactOut in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
ContactOut with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingContactOut with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingContactOut with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingContactOut with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingContactOut with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingContactOut with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
ContactOut and Arc0, answered.
Does ContactOut work with Claude Desktop and Claude Code?
Yes, after connecting the account and authorizing the client. Use Arc0’s remote MCP endpoint with OAuth. Claude Code has a documented registration command; Desktop uses the generic remote-client setup.
Can I use ContactOut with OpenAI Codex, ChatGPT and Cursor?
Yes, after connecting the account and authorizing the client. Codex and ChatGPT have setup instructions in Arc0’s MCP clients guide. Cursor uses the generic remote-MCP steps. Tool access remains scoped to the authorized identity.
Is this the official ContactOut MCP server?
This is Arc0’s integration page, not a claim of an official ContactOut server. Arc0 adds a shared connection, policy and audit experience across apps. Consult ContactOut for its own current MCP offerings.
Which ContactOut actions are supported?
9 registry-defined actions: 9 read, 0 write and 0 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.
Which permissions does ContactOut need?
Connect ContactOut using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
Can I restrict writes in ContactOut?
You can deny write and destructive actions or require approval. Provider scopes and Arc0 action policies are separate controls; a policy does not grant additional provider permissions.
What does ContactOut through Arc0 cost?
See Arc0 pricing for current connectivity plans. The provider may require its own subscription or charge per request. Arc0 plan allowances do not make third-party data or paid actions free.
Plug ContactOut into your agent.
ContactOut MCP server: 9 actions including get contact, check personal email, check work email. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
ContactOut and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by ContactOut.