Skip to main content
Connect an AI client to Influship to find Instagram creators, review campaign evidence, and research live Instagram, TikTok, and YouTube content. Every client uses the same server URL:
Add it as a remote MCP server or custom connector, then sign in when your client asks. You choose which Influship account the client uses during sign-in, so you never copy an API key into a config file.

Choose an account at sign-in

When your client opens the Influship sign-in page, pick the account its research should be billed to: New to Influship? Either option lets you create an account during sign-in. New accounts go through the usual setup first (billing details for an API account, workspace setup for the app) and then return to finish connecting. If you are already signed in to the wrong account in this browser, select Use a different account on the connection screen. To disconnect a client, open Connected apps in the developer dashboard for API accounts, or Settings → Connected apps in the Influship app.

Choose a task

Stored creator and profile lookups return indexed data. They do not trigger a live profile scrape. Collection and analysis timestamps describe the evidence’s age; see Understanding Creator Data. get_instagram_profile retrieves a live profile by exact username. Set include_posts: true and post_limit: 5 to include up to five recent posts. The result includes public post links and collection time; stored profile lookups remain separate. Each post includes view_count: a measured video view count, or null when unavailable or hidden. Recent reel views are collected when publicly available, even when the individual post does not expose them. A missing count is not zero views. Engagement rate describes the returned post sample with visible counts, with its sample size. It is null when no measurable posts or followers are available; hidden counts are also null. The prompt gallery provides task examples you can copy into your client.

Quickstart

Claude

In Claude, Claude Desktop, or Cowork, open Customize → Connectors:
  1. Select Add custom connector.
  2. Enter Influship as the name and https://mcp.influship.com as the server URL.
  3. Select Connect, sign in to Influship, and choose the account to bill.
  4. Ask for a creator shortlist, inspect a profile, or compare creators against a campaign brief.
Claude shows interactive shortlists, profiles, and comparisons. The anonymous sample profile works before you connect. For example: “Find five Instagram creators whose recent posts discuss sunscreen and sensitive skin. Show the supporting evidence and compare the strongest three for a premium SPF launch.”

Claude Code

Then run /mcp in Claude Code, select influship, and sign in. Add --scope user to install across every project, not just the current directory.

Cursor

Add this to .cursor/mcp.json, or to ~/.cursor/mcp.json for every project:
Open the MCP section of Cursor’s settings and select Connect next to Influship to sign in.

VS Code

Run MCP: Add Server, choose HTTP, and enter https://mcp.influship.com. Or add it to .vscode/mcp.json:
VS Code asks you to sign in to Influship the first time a tool runs.

ChatGPT

In an eligible workspace, enable developer mode, create a custom app from Settings → Apps, and use https://mcp.influship.com/chatgpt/mcp as the MCP server URL. Sign in to Influship when prompted.
ChatGPT uses its own address because its interactive views need ChatGPT-specific settings. Every other client uses https://mcp.influship.com.

Other clients

Any client that supports remote MCP servers with OAuth can use https://mcp.influship.com. Stdio-only clients can connect through mcp-remote, which opens the Influship sign-in page in your browser:

Headless and CI setups

Where no one can complete a browser sign-in, send an API key from the dashboard instead, using the same URL:
Keep the key in an environment variable or secret store. Every tool works with an API key; calls are billed to that API account.

Set up with AI

Copy this prompt into your coding agent.

Connect this development environment to the Influship MCP server.

Open in Cursor

How it works

  1. Your client connects to https://mcp.influship.com and lists the available tools, each with a description and parameter schema
  2. The first time a tool needs your account, the client opens the Influship sign-in page, where you choose the account to bill
  3. The client picks the right tool, such as semantic_search_creators, and calls it with its arguments
  4. The result includes structured creator or source-platform evidence; some tools also return suggested_followups
Clients can list tools without signing in. get_sample_creator provides an unauthenticated preview.

Tools

Use your client’s tool list for the exact schemas.

Creator workspace

The signed-in workspace in Claude and ChatGPT lets you describe a campaign brief, inspect Instagram creator evidence, select up to eight creators, and compare two to four against the brief. Save a named shortlist with notes to your 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 account’s credits. 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 account. In desktop hosts that support composer mentions, search your saved shortlist names to reference them in a conversation.

Authentication and billing

  • Signed-in clients send an OAuth bearer token; calls use the account you chose at sign-in, with its billing and rate limits
  • Headless clients can send X-API-Key; calls use that API account’s metering and rate limits
  • get_sample_creator is an unauthenticated preview and does not expose arbitrary creator data
If you don’t have an Influship account yet, choose Influship API at sign-in to create one.

Pricing

MCP tool calls billed to an API account use the same credit prices as the underlying REST endpoints, with no MCP surcharge. Calls billed to an Influship app plan use that plan’s credits. The creator workspace can combine several underlying calls. 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 600 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 account)

For one-off agents without an Influship 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

Prompt Gallery

Copy a discovery brief or research task into your AI client

Open the dashboard

Manage connected apps, usage, and API keys

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