Menu

inseeq MCPBeta

Let your AI agents read your company's growth data by using our MCP server.

View as Markdown

The inseeq Model Context Protocol (MCP) server provides tools that AI agents can use to query your company's ads, website, search, CRM and outreach data, and to keep the answers your team agrees on.

Set up inseeq MCP

Follow the instructions for your MCP client. Each person connects with their own account.

These steps work in the Claude desktop app and on claude.ai.

  1. Open Claude. Go to Customize, then Connectors. If you do not see Customize, go to Settings, then Connectors.
  2. If you see an older inseeq connector in the list, open it, click the three dots and click Remove.
  3. Click Add, then choose the custom connector option.
  4. Name it inseeq and paste this address: https://api.inseeq.com/mcp
  5. Click Add, then Connect. A browser tab opens on inseeq.
  6. Sign in with your work email. New here? You name your workspace while signing in.
  7. Check that the card shows your company, then click Connect Claude.
  8. Choose Always allow when Claude asks.

For Team and Enterprise plans, an owner adds the connector to the workspace once. Each member then clicks Connect.

Manage MCP access

inseeq's MCP server supports two ways to authenticate:

  1. Sign-in: each person signs in with their work email. Use it for apps people chat in, such as Claude and ChatGPT.
  2. MCP keys: for scripts and your own agents that run without a person. Keys are only for scripts and your own agents.

When you connect with sign-in, your app opens an inseeq page. Sign in, check that the card shows your company, and confirm. If you belong to more than one workspace, pick it on the card. To switch, disconnect and connect again.

Read access to your growth data. inseeq never changes your ads, analytics or CRM. What your assistant can change stays inside inseeq: your metrics, your API keys, your team and your messages to inseeq.

If your organization manages your device or network, your IT administrator might block connections to external MCP servers. If inseeq doesn't connect, ask IT to allow api.inseeq.com.

Disconnect an app

Remove the inseeq connector in your app's settings. The app loses access straight away. To connect again, follow the setup steps above.

Manage your keys

Your MCP keys are listed in the inseeq app under Settings, Claude. To revoke a key:

  1. Find the key in the Keys list.
  2. Click Revoke next to it.
  3. Confirm. Anything using the key stops working.

Authenticate inseeq MCP

Use sign-in for interactive MCP clients. Sign-in lets each person connect and disconnect without sharing a key.

For scripts and agents that can't sign in, create an MCP key in the inseeq app under Settings, Claude. Pass it as the bearer token in the Authorization header: Authorization: Bearer <your MCP key>. The key is shown once. Keep it out of chats and shared files. Details are in the reference.

An MCP key is not an API key. To call the Data API over HTTP, create an API key.

Tools

The server exposes the following MCP tools (44 in all). Your assistant receives each one with its parameters when it connects. The reference has every tool in full.

Take care when you use inseeq alongside other MCP servers. Text in your CRM and ad accounts can come from outside your company, so watch for prompt injection. If you have feedback or want to see more tools, ask Claude to send this to inseeq, or message your inseeq contact.

ResourceToolDescription
Identityget_startedWhere this workspace stands and what to do next
whoamiWho this connection is
Warehousecreate_api_keyCreate an API key, for reading this organization's data over the inseeq Data API from code
execute_sqlRuns one GoogleSQL SELECT over this organization's dataset
get_all_modelsEvery table you can read, with its grain, date span and a summary
get_all_sourcesWhich dates an answer can cover
get_lineageWhat a node is built from and what is built on it
get_model_healthWhether a node could be trusted at its last good build
get_node_detailsOne node in full
list_api_keysThis organization's live API keys, masked, and the links nobody has opened yet
revoke_api_keyRevoke one of this organization's API keys, whoever created it, by its `id` from `list_api_keys`
Metricsdelete_metricDeletes a metric by name, for everyone in the organization
export_rowsThe full list as a CSV file, when an answer was too long to show and the user wants it as a file
get_dashboard_recipeHow to build a dashboard from metrics
list_metricsThis organization's metrics
run_metricRuns one metric by name
save_metricSaves an answer as a metric for the whole organization, so it gives the same number every time
Business rulescancel_rule_changeDrops the caller's change that is still being checked or waiting for a yes
change_rulesChanges business rules, all or nothing
confirm_rule_changeApplies a previewed change after the user's yes, with the `preview_id` from that preview
confirm_rulesMarks rules as checked by the user
get_rule_changeOne rule change, with its state, edits, preview and `before_after`
list_rulesThe workspace's business rules
undo_rule_changePuts the rules back to how they were before a live change, and rebuilds the numbers
Connect dataconfirm_accountsConnect the accounts the user picked from list_accounts
connect_sourceStart connecting one of the team’s tools
connection_statusWhat is connected and how far each tool has loaded, by the rules of the admin Data page
list_accountsThe accounts the latest sign-in for a platform can see, for the user to pick from
Workspace & teamapprove_join_requestLet someone in: they join this workspace as a member and get an email saying so
cancel_invitationCancel a pending invitation by the email it was sent to
change_member_roleMake a member an admin, or an admin a member, by email
confirm_workspace_settingsStore the workspace's settings, once
create_mcp_keyCreate an MCP key for a script or the user's own agent to talk to inseeq as the user, with read and write access
decline_join_requestTurn a join request down
invite_teammateInvite a teammate to this workspace by email, as a user or an admin
list_join_requestsPeople waiting to join this workspace, newest first
list_mcp_keysThis workspace's live MCP keys, masked, with the member each one acts as
list_membersWho is in this workspace
remove_memberRemove a member by email, or cancel their pending invitation
revoke_mcp_keyRevoke one of this workspace's MCP keys, whoever it belongs to
Org relationshipget_contextThe standing rules your team saved earlier, if any
Supportreport_frictionRecord, silently, that this conversation hit friction, then carry on
send_to_inseeqSend a question, a problem or feedback to inseeq's team
share_in_slackPost a request in the workspace's shared Slack channel with inseeq's team, or set that channel up

See also

  • Using inseeq MCP: your first chat, metrics, exports and dashboards
  • MCP reference: keys, errors, limits and every tool in full
  • Data API: the same data over HTTP, for your own dashboards and automations
  • llms.txt: these docs for AI assistants
inseeq MCP