Skip to main content
The Hog MCP server lets AI tools call The Hog API tools directly from natural language. Use it when you want an agent to search companies, find people, enrich prospects, research accounts, monitor topics, or scrape and extract web data without hand-writing each HTTP request.
This is different from Mintlify’s docs MCP endpoint. Mintlify exposes documentation context. The Hog MCP exposes The Hog API as executable tools.

​
Choose a setup

Use the hosted MCP endpoint when your client supports remote MCP with OAuth. Use the local npm package when your client only supports local stdio servers or when you want credentials to stay entirely in your local client config.
SetupBest forAuthentication
Hosted remote MCPClaude and other hosted MCP clientsSign in with The Hog and select an organization
Local stdio MCPClaude Desktop, Claude Code, Cursor, Codex, VS Code, Windsurf, and local coding agentsAPI key and API secret from the Credentials page

​
Hosted remote MCP

Hosted MCP does not require a manually created API key. Your MCP client connects to The Hog, opens a sign-in flow, and asks you to choose the organization that should be billed for tool calls. Use this endpoint: 
https://mcp.thehog.ai/mcp
When your MCP client asks for a remote server URL, paste the endpoint above. The client should open a browser-based OAuth flow. After you sign in and choose an organization, The Hog creates a connector-specific MCP URL for that client and organization.
If you belong to multiple organizations, connect each organization separately. Each connection is scoped to the organization you selected during authorization.

​
Claude

Claude supports remote MCP through custom connectors. In Claude, open Settings, go to Connectors, choose Add custom connector, and enter: 
Name: The Hog
URL: https://mcp.thehog.ai/mcp
After saving, click Connect. Claude opens the OAuth flow in your browser so you can sign in to The Hog and choose the organization for that connector. For Team or Enterprise workspaces, an owner may need to add the custom connector at the organization level before members can connect it.

​
Revoke access

You can view and revoke hosted MCP connections from the Remote MCP page in the dashboard: 
https://platform.thehog.ai/settings/integrations/mcp
Revoking a connection blocks that MCP client from making further requests. It does not revoke your API keys.

​
Hosted MCP security

  • Hosted MCP uses OAuth instead of API keys.
  • Tool calls are billed to the organization selected during authorization.
  • The MCP client cannot switch organizations by sending headers or IDs.
  • Revoked connections fail on the next MCP request.
  • You should still review tool calls before approving actions that spend credits, create monitors, or fetch large datasets.

​
Local stdio MCP

Use local stdio MCP when your client runs MCP servers on your machine with a command like npx. Package and source:

​
Available tools

See MCP tools for the workflow tools, direct API tools, example prompts, and async behavior.