PredictLeads MCP server
PredictLeads provides company intelligence on hiring, technology use, financing, and news to spot growth signals. Sales and research teams use it to time outreach around real company changes. Connect through Arc0 to use the actions your identity is allowed to call.
Agent workflows for PredictLeads.
Look up a company
Use when resolving an exact domain or UUID, including acquisition or rename redirects. Not for broad name searches. 1 credit per response; a timed-out call may still be charged.
List company job openings
Use when assessing hiring for a known company; narrow with date and not_closed filters. Not for company discovery. 1 credit/page (up to 1,000 vendor records; Arc0 caps 50). A timed-out call may still be charged.
List company technologies
Use when checking a known company’s technologies; narrow with date filters. Not for discovering companies by technology. 1 credit/page (up to 1,000 vendor records; Arc0 caps 50). A timed-out call may still be charged.
7 PredictLeads actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
7Look things up, subject to your permissions.
- predictleads.get_companyLook up a company
Use when resolving an exact domain or UUID, including acquisition or rename redirects. Not for broad name searches. 1 credit per response; a timed-out call may still be charged.
- predictleads.list_job_openingsList company job openings
Use when assessing hiring for a known company; narrow with date and not_closed filters. Not for company discovery. 1 credit/page (up to 1,000 vendor records; Arc0 caps 50). A timed-out call may still be charged.
- predictleads.list_technologiesList company technologies
Use when checking a known company’s technologies; narrow with date filters. Not for discovering companies by technology. 1 credit/page (up to 1,000 vendor records; Arc0 caps 50). A timed-out call may still be charged.
- predictleads.list_news_eventsList company news signals
Use when tracking a known company’s news signals; narrow with date filters. Not for article text or company discovery. 1 credit/page (up to 1,000 vendor records; Arc0 caps 50). A timed-out call may still be charged.
- predictleads.list_financing_eventsList company financing
Use when reviewing funding rounds and investor IDs; narrow with date filters. Not for investor discovery. 1 credit/page (up to 1,000 vendor records; Arc0 caps 50). A timed-out call may still be charged.
- predictleads.list_connectionsList company relationships
Use when mapping a known company’s relationships; narrow with date filters. Not for broad prospect discovery. 1 credit/page (up to 1,000 vendor records; Arc0 caps 50). A timed-out call may still be charged.
- predictleads.get_subscriptionGet subscription usage
Use when checking subscription status and monthly usage. Not for account identity or frequent polling. May cost 1 credit; confirm in live window. A timed-out call may still be charged.
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 PredictLeads.
Connect the intended PredictLeads 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 PredictLeads connects.
Connect PredictLeads using API key and API token. 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 and API token
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use PredictLeads with your AI client.
Sign in to Arc0 and connect PredictLeads in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
PredictLeads 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 troubleshootingPredictLeads 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 troubleshootingPredictLeads 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 troubleshootingPredictLeads 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 troubleshootingPredictLeads 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 troubleshootingPredictLeads 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.
PredictLeads and Arc0, answered.
Does PredictLeads 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 PredictLeads 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 PredictLeads MCP server?
This is Arc0’s integration page, not a claim of an official PredictLeads server. Arc0 adds a shared connection, policy and audit experience across apps. Consult PredictLeads for its own current MCP offerings.
Which PredictLeads actions are supported?
7 registry-defined actions: 7 read, 0 write and 0 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.
Which permissions does PredictLeads need?
Connect PredictLeads using API key and API token. 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 PredictLeads?
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 PredictLeads 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 PredictLeads into your agent.
PredictLeads MCP server: 7 actions including look up a company, list company job openings, list company technologies. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
PredictLeads and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by PredictLeads.