Skip to main content
The Influship MCP server exposes the API to AI agents through typed tools. It works with Claude Desktop, Cursor, ChatGPT Connectors, VS Code Copilot, and any Model Context Protocol-compatible client. The server is hosted at https://mcp.influship.com/mcp and uses the Streamable HTTP transport (spec 2025-06-18). Stdio-only clients connect via the mcp-remote bridge.

How it works

Generic MCP clients authenticate with an Influship API key. Clients that support account linking can use OAuth instead. Calls use the billing route and rate limits associated with the credential.
  1. The agent connects to https://mcp.influship.com/mcp with an X-API-Key or linked Influship account
  2. The agent discovers the available typed tools, each with a full description and parameter schema
  3. The agent picks the right tool, such as semantic_search_creators, and calls it with its arguments
  4. The result includes the REST response fields plus MCP-specific suggested_followups
Clients can list available tools without authentication. get_sample_creator provides an unauthenticated preview. The remaining tools require an API key or OAuth account link.

Set up with AI

Copy this prompt into your coding agent.

Connect this project or development environment to the Influship MCP server.

Open in Cursor

Tools

The table below describes the general /mcp endpoint. The account-linked /plugin/mcp endpoint exposes a focused creator workspace and saved-shortlist tools; see ChatGPT setup. Use your client’s tool list for the inventory available on its configured endpoint. Each tool description tells the agent when to use it. Use semantic_search_creators for topical or campaign discovery, search_creators for a name or partial handle, and find_lookalike_creators when you already have seed creators.

Quickstart

Choose the setup for your client below. Config-based clients need an API key from the dashboard; account-linking clients use OAuth.

Claude Code (CLI)

One command:
Add --scope user to install across every project, not just the current directory.

Claude Desktop

Open Customize → Connectors → Add custom connector, enter https://mcp.influship.com/mcp, then complete Influship account linking when prompted. Claude’s remote custom-connector flow uses OAuth rather than an arbitrary API-key header. If you prefer an API-key-backed local bridge, add this to ~/Library/Application Support/Claude/claude_desktop_config.json:

Cursor and Windsurf

Both clients use the same remote-server configuration. Set INFLUSHIP_API_KEY in the environment that launches the app, then add this JSON to .cursor/mcp.json for Cursor or ~/.codeium/windsurf/mcp_config.json for Windsurf:

VS Code

Run MCP: Add Server, or add the server to .vscode/mcp.json. VS Code uses a top-level servers object rather than Cursor’s mcpServers key:

ChatGPT

In an eligible workspace, enable developer mode, create a custom app from Settings → Apps, and use https://mcp.influship.com/plugin/mcp as the remote MCP endpoint. Complete Influship account linking when prompted. The ChatGPT workspace lets you describe a campaign brief, inspect creator evidence, select up to eight creators, and compare two to four against the brief. Save a named shortlist with notes to your linked account, then resume it from the saved library. Selected creators remain available when you refine a search. Resume a saved shortlist to retrieve the latest stored creator evidence using your linked account’s lookup allowance. Your shortlist keeps selected profiles, the brief, and notes together. Collection dates and evidence labels help you review profile data, content evidence, and AI analysis. Each account can hold 100 saved shortlists. Updating a shortlist requires its current version; if another save changes it, reopen it before updating. Saved work is private to your linked account. In desktop hosts that support composer mentions, search your saved shortlist names to reference them in a conversation.

Stdio-only clients

Some clients only support stdio transport. Bridge them with mcp-remote:

Authentication and billing

The MCP server supports two authentication paths:
  • Generic clients send X-API-Key; calls use the associated API account’s metering and rate limits
  • Account-linking clients send an OAuth bearer token; calls use the linked account’s billing route and allowance
  • get_sample_creator is an unauthenticated preview and does not expose arbitrary creator data
If you don’t have an API key, create one in the dashboard.

Pricing

MCP tool calls bill at the same per-credit price as the underlying REST endpoint. There’s no MCP surcharge. One credit is $0.01. See the REST pricing reference for the full breakdown.

Rate limits

The credential’s account limits apply, matching direct REST usage. There’s also a per-IP cap of 60 requests per minute. If you hit it, the server returns 429 with a retry-after header. If you’re connecting many agents from the same IP (a corporate proxy, for example), reach out and we’ll tune the IP cap.

Error codes

When a tool call fails, the error message is surfaced as readable text in the MCP client.

Anonymous agents (no API key)

For one-off agents without an API key or linked account, use the direct HTTP API with x402 or MPP. These payment protocols apply to supported REST endpoints rather than MCP tool calls.

Implementation tips

  • Use tool descriptions for selection. Each tool describes its purpose and parameters so your client can choose the appropriate operation.
  • Pass real IDs. Tools that take a creator_id expect a UUID from a previous tool’s response. Resolving by platform + username is supported on lookalike, match, and posts — useful when the user types a handle.
  • Bound multi-step workflows. Cursor pagination and composite render tools can make additional billed calls. Set a page or result ceiling before handing control to an autonomous agent.

Next steps

Get an API Key

Sign up and grab your key from the dashboard

API Reference

Full endpoint specs and response schemas — the tools mirror these

Pay with x402

Anonymous per-request payment for one-off agents

Pay with MPP

Stripe cards or Tempo USDC for agent-native payments